Bundles: A bundle is a package of files and information, similar to an Application Object and its files but with far greater power and flexibility. A bundle wizard lets you create a bundle, configure the actions associated with a bundle, and then assign bundles to devices or users. There are four types of bundles: Windows, Directive, File, and Imaging. For more information, see the ZENworks 10 Configuration Management Software Distribution Reference.

Actions and Action Sets: A bundle contains actions to perform with its content. All actions are divided into six categories, referred to as action sets: Install, Launch, Verify, Uninstall, Terminate, and Preboot. You can identify your actions at the time you create the bundle, and you can also add or subtract the actions later in ZENworks Control Center. For more information, see Actions in the ZENworks 10 Configuration Management Software Distribution Reference.

Content: Applications and files, along with policy files, are referred to as content. Content is stored in a directory structure, called the content repository, on the Primary Server. The Primary Server and ZENworks Adaptive Agent (running on the managed device) communicate via standard Web protocols to provide access to the content. Unless you configure your system differently, content is automatically replicated among Primary Servers to ensure that it is available from all Primary Servers. For more information, see Content Delivery in the ZENworks 10 Configuration Management System Administration Reference.

Cache: Each managed device still uses a cache directory. However, the cache location has moved from drive_root\nalcache to zenworks_home\cache. All bundles are copied to the cache directory before installation. By default, this copy occurs when the bundle is first launched on the device.

Forced Caching: You can use a distribution schedule to force cache a bundle so that it is immediately available for installation when the user launches it. The schedule can initiate an immediate distribution of the bundle, or delay distribution to a future time.

Forced Running: You can use a launch schedule to force an application to run. For example, run the application immediately or when the device refreshes. For more information, see Launching a Bundle in the ZENworks 10 Configuration Management Software Distribution Reference.

Distribution Points: To improve content access for a group of devices without creating another Primary Server, you can create a Content Distribution Point on any managed device. Distribution Points are useful in slow WAN configurations. For more information, see Understanding the Satellite Roles in the ZENworks 10 Configuration Management System Administration Reference.

Dependencies: Dependencies are now created automatically whenever you select specific types of actions for a bundle. For more information, see Creating a Bundle with Content and Dependency on Another Bundle in the ZENworks 10 Configuration Management Software Distribution Reference.

Proximity and Load Balancing: Site lists (proximity) and source lists (workload) are replaced by a feature called Closest Server Rules. These are rules that you create to direct managed devices to the Primary Server from which they will receive content and configuration information. For more information, see Closest Server Rules in the ZENworks 10 Configuration Management System Administration Reference.