20.13 Deploying a Different Version of a Bundle

You can have multiple versions of the same bundle, although only one version of a bundle can be deployed at any given time. If you make any configuration changes to an existing bundle (changing the display name or description, adding a package to or removing a package from the bundle, or adding or modifying a script), the version number increments.

Only one version of a bundle can be deployed at any given time. For example, suppose a bundle has multiple versions: 1, 2, and 3. If version 1 is currently deployed, all associated devices have version 1 of the bundle deployed. If you then make version 3 the deployed version, all devices with version 1 deployed and still associated to that bundle will be automatically upgraded to version 3.

For more information about editing bundles, which might cause version numbers to increment, see Section 20.5, Editing Bundles. Note that only changes made on the Details page cause the version number to increment, as described in Step 3.

The following section contains additional information:

20.13.1 Bundle Version Deployment Behavior (ZENworks Control Center vs. the zlman Utility)

You can modify an existing bundle using either the ZENworks Control Center or the zlman utility, which causes the bundle’s version number to increment. Depending on the method you use to modify a bundle, the deployment behavior of the new version varies.

If you use the ZENworks Control Center to modify a bundle, the version number increments but the new version of the bundle is not automatically deployed; you must manually deploy the new version, as described in Step 3.a.

If you use the zlman utility to modify a bundle, the version number increments and the new version of the bundle is automatically deployed; you do not have to manually deploy the edited bundle.