Deploying A Different Version Of A Bundle; Bundle Version Deployment Behavior; Utility) - Novell ZENWORKS LINUX MANAGEMENT 7.2 IR2 - ADMINISTRATION GUIDE 09-25-2008 Administration Manual

IMPORTANT: Do not rename patch bundles.
Copy: Click Copy, type a new name for the copy, then click OK.
The copy option is useful to create a new bundle that is similar to an existing bundle. You
can copy a bundle and then edit the new bundle's settings.
If you create a copy of the YOU patch bundle, the copied version is converted to the RPM
package bundle type. Before deploying the RPM package bundle to the device, you must
remove the patch RPMs from the bundle. However, you cannot install the copied version
of the YOU patch bundle if it contains only scripts.
Move: Click Move, choose a destination folder for the selected objects, then click OK.
If you rename or move a bundle, its assignments are still in place and ZENworks Linux
Management does not redistribute the catalog to devices because of the name or location
change.

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," on page
cause the version number to increment, as described in
The following section contains additional information:
Section 20.13.1, "Bundle Version Deployment Behavior (ZENworks Control Center vs. the
zlman Utility)," on page 251
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
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 3a on page
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.
235. Note that only changes made on the Details page
Step 3 on page
237.
237.
utility,
zlman
Using RPM and File Bundles 251