ZENworks provides a change management capability for bundles allowing you to make changes to them with minimum disruption to IT services.
To understand bundle change management, see Section 7.0, Understanding Bundle Change Management.
Review the following sections:
Bundle Change Management allows you to create either a sandbox-only bundle or a published version of the bundle. If you edit a published version of the bundle, a sandbox is created. You can choose to publish the sandbox either as a new version of the bundle or a new bundle.
For more information on the bundle versions, see Section 8.4.2, Managing Bundle Versions.
For more information on publishing the sandbox, see Section 8.4.4, Publishing SandboxSection 8.4.4, Publishing Sandbox.
The Displayed Version option on the bundle’s page lists all the existing versions of the bundle, and the latest version of the bundle is selected by default. However, if a sandbox exists, the sandbox is selected by default.
Consider a bundle named sos1 that is created as a sandbox. The Displayed Version option on the bundle page lists Sandbox and it is selected by default.
Click Publish to publish the sandbox to a new version. The Displayed Version option on the bundle page now lists 0(Published) and it is selected by default.
Edit the bundle’s description to create a sandbox. The Displayed Version option on the bundle page now lists 0(Published) and Sandbox. Sandbox is selected by default.
Click Publish to publish the sandbox to a new version. The Displayed Version option on the bundle page now lists 0(Published), and 1(Published). The bundle’s latest version, 1(Published), is selected by default.
0 is the older version of the bundle.
Edit the bundle’s description again to create a sandbox. The Displayed Version option on the bundle page now lists 0(Published), 1(Published), and Sandbox. Sandbox is selected by default.
0 is the older version of the bundle and 1(Published) is the latest version of the bundle.
Click Publish to publish the sandbox to a new version. The Displayed Version option on the bundle page now lists 0(Published), 1(Published), 2(Published). The bundle’s latest version, 2(Published), is selected by default.
0 and 1 are the older versions of the bundle; and 2(Published) is the latest version of the bundle.
The Displayed Version option on the bundle’s page lists all existing versions of the bundle, and the latest version of the bundle is selected by default. However, if a sandbox exists, the sandbox is selected by default.
For more information on the bundle versions, see Section 8.4.1, Understanding Bundle Versions.
Select the version of the bundle whose details you want to view or edit.
|
Task |
Steps |
Additional Details |
|---|---|---|
|
Create a sandbox from the published version of the bundle |
|
A single modification made to the bundle creates a sandbox. The created sandbox is a copy of the bundle and also includes the additional edit. However, the change is not made to the published version of the bundle. The sandbox flows to the test devices and users to whom the bundle is assigned. Changes can now be made to the sandbox. You can revert a sandbox to the original version of the bundle or publish a sandbox to create a new version or a new bundle. |
|
Create a sandbox from an older version of the bundle |
|
The created sandbox is an exact copy of the bundle version. Changes can now be made to the sandbox. |
|
Publish a sandbox |
|
The sandbox must be published for the changes to be effective on the non-test devices and users to whom the bundle is assigned. |
|
Revert a sandbox |
|
All the changes made are discarded. The sandbox no longer exists. The published version of the bundle is displayed in the Displayed Version option. |
|
Delete an older version of the bundle |
|
To delete all older versions of a bundle or delete all versions older than a particular version, click Delete Older Versions under the Bundle Tasks list located in the ZENworks Control Center left navigation pane. |
Using the Bundle Version Retain settings, you can configure the number of older bundle versions that should be retained. This setting can be configured at the zone, folder and bundle levels. The order of precedence is bundle, folder and then zone.
To configure the bundle version retain settings, perform the following steps:
In ZCC, go to Configuration > Management Zone Settings > Bundle, Policy and Content > Older Bundle Version Retain Setting.
Following are the available options to retain the version:
Retain all versions: Select this option to retain all versions of the bundle. This includes the published and sandbox versions.
Retain the specified number of older versions: Select this option to specify the number of older versions of the bundle to be retained.
The number that you specify should be a positive integer and it should not include the Published and Sandbox versions as they are retained by default. For example: If a bundle has 5 versions and if you specify 2, then only the 2 versions prior to the currently published version will be retained along with Published and Sandbox versions. The remaining versions will be deleted.
Do not retain any older versions: Select this option if you do not want to retain any older versions of bundles in ZENworks. This option retains only the Published and Sandbox versions.
The sandbox must be published for the changes to be effective on the devices and users to whom the bundle is assigned. You can choose to publish the sandbox either as a new version or as a new bundle.
Review the following sections:
Publishing a sandbox as a new version lets you create a new version of the bundle that has a version number incremented by one from the latest available version of the bundle.
Perform the following steps in the ZENworks Control Center:
On the page of the bundle that you want to publish, select Sandbox in the Displayed Version option.
Click Publish to display the Publish Option page.
Click Publish as New Version.
(Conditional) If the bundle has any dependencies, the Publish Dependent Bundles Page is displayed.
This page lists all the bundles that the sandbox you want to publish depends on. These can include sandbox-only bundles (bundles that were directly created as a sandbox), or sandbox bundles (bundles that were edited to create a sandbox). To publish the sandbox, you must publish all the dependent sandbox-only bundles. However, you can choose to publish all the dependent sandbox bundles.
You must select the Publish sandbox only bundle(s) that this bundle depends on option to publish all the dependent child bundles that have a sandbox-only version.
Select the Publish sandbox for all bundle(s) that this bundle depends on option to publish all the dependent child bundles that have a sandbox.
On the Summary Page, review the information and, if necessary, use the Back button to make changes to the information
Click Finish to create a new published version.
For example, if the Displayed Version option on the bundle page lists 0(Published), 1(Published), and Sandbox, publishing the sandbox as a new version creates a version 2. The Displayed Version option on the bundle page now lists 0(Published), 1(Published), and 2(Published).
Publishing a sandbox as a new bundle creates a new bundle. Perform the following steps in the ZENworks Control Center:
On the page of the bundle that you want to publish, select Sandbox in the Displayed Version option.
Click Publish to display the Publish Option page.
Click Publish as New Bundle.
Specify a name for the bundle.
The bundle name must be different from the name of any other item (bundle, group, folder, and so forth) that resides in the same folder. The name you provide displays in ZENworks Control Center and the ZENworks Agent (on managed devices).
For more information, see Naming Conventions in ZENworks Control Center
in the ZENworks Control Center Reference.
Specify the folder name or browse to the ZENworks Control Center folder where you want the bundle to reside. The default is /bundles, but you can create additional folders to organize your bundles.
Select the Create as Sandbox option to create a sandbox-only version of the bundle and deploy the bundle as a sandbox. The sandbox version of a bundle enables you to test it on your device before actually deploying it.
Select the bundle groups that the new bundle should be a member of.
Click Next to display the Select Assignments page.
Select the device and user assignments that you want to apply to the new bundle.
Click Next.
(Conditional) If the bundle has any dependencies, the Publish Dependent Bundles Page is displayed.
This page lists all the bundles that the sandbox you want to publish depends on. These can include sandbox-only bundles (bundles that were directly created as a sandbox), or sandbox bundles (bundles that were edited to create a sandbox). To publish the sandbox, you must publish all the dependent sandbox-only bundles. However, you can choose to publish all the dependent sandbox bundles.
You must select the Publish sandbox only bundle(s) that this bundle depends on option to publish all the dependent child bundles that have a sandbox-only version.
Select the Publish sandbox for all bundle(s) that this bundle depends on option to publish all the dependent child bundles that have a sandbox.
By default, the dependent bundles are published to the next version. You can choose to select the Publish the dependent bundles as new bundles option to publish the dependent bundles as new bundles.
Specify the name or browse to the folder where you want the new bundles to reside. If a bundle that has the same name as the new bundle already exists in the specified folder, then the new bundle is saved with a random GUID appended to its name.
On the Summary Page, review the information and, if necessary, use the Back button to make changes to the information.
Click Finish to create the bundle.
Perform the following steps in the ZENworks Control Center:
Select a few bundle folders, bundle groups and bundles.
Click Action > Publish Bundle(s) to display the Publish Options page.
(Conditional) Select the Include bundles from subfolders also option to publish all the bundles within the selected folders as new versions of the bundles.This option is displayed only if you have selected a bundle folder in Step 1.
Click Next. On the Select Bundles page, select the bundles you want to publish to next version, then click Next.
(Conditional) If the bundle has any dependencies, the Publish Dependent Bundles Page is displayed.
This page lists all the bundles that the sandbox you want to publish depends on. These can include sandbox-only bundles (bundles that were directly created as a sandbox), or sandbox bundles (bundles that were edited to create a sandbox). To publish the sandbox, you must publish all the dependent sandbox-only bundles. However, you can choose to publish all the dependent sandbox bundles.
You must select the Publish sandbox only bundle(s) that this bundle depends on option to publish all the dependent child bundles that have a sandbox-only version.
Select the Publish sandbox for all bundle(s) that this bundle depends on option to publish all the dependent child bundles that have a sandbox.
On the Summary Page, review the information and, if necessary, use the Back button to make changes to the information
Click Finish to create a new published version.
For example, if the Displayed Version option on the bundle page lists 0(Published), 1(Published), and Sandbox, publishing the sandbox as a new version creates a version 2. The Displayed Version option on the bundle page now lists 0(Published), 1(Published), and 2(Published).