1. In the ZENworks Control Center, click the Bundles tab.

2. Click the folder that you created while performing an in-place upgrade on the ZENworks Primary Server (Step 11) to hold the upgrade bundles.

3. Click the underlined name of the desired upgrade bundle to display its details.

4. Click the Details tab.

5. In the Scriptable Actions section at the bottom of the Details page, click New to display the New Scriptable Action dialog box.

6. In the Scriptable action drop-down list, select Pre-Installation.

7. In the Script to run drop-down list, select Define your own script.

8. Paste the contents of the pre-install.sh script file into the Script content box. You can access the script file from the /data directory located within the directory on which ZENworks 7.2 Linux Management with IR1/IR1a/IR2 is mounted. For example, if ZENworks 7.2 Linux Management with IR1/IR1a/IR2 is mounted on /zlm72/install, the pre-install.sh script file resides in the /zlm72/install/data directory.

   If the managed device has bundle locks or package locks (package-locks.xml), the Pre-Installation script takes a backup of the bundle locks or package locks and places the backup in the /tmp/zmd directory.

9. Click OK.

10. In the Scriptable Actions section at the bottom of the Details page, click New to display the New Scriptable Action dialog box.

11. In the Scriptable action drop-down list, select Post-Installation.

12. In the Script to run drop down list, select Define your own script.

13. Paste the contents of the post-install.sh script file into the Script content box. You can access the script file from the /data directory located within the directory on which ZENworks 7.2 Linux Management with IR1/IR1a/IR2 is mounted. For example, if ZENworks 7.2 Linux Management with IR1/IR1a/IR2 is mounted on /zlm72/install, the post-install.sh script file resides in the /zlm72/install/data directory.

    NOTE:In the post-install.sh script file, the messages indicating the progress of the upgrade are commented out by default. If you want the messages to be displayed on the managed device, uncomment the messages.

    The Post Installation script performs the following tasks:

    • Restores the bundle locks and package locks backup from the /tmp/zmd directory to the appropriate directories.

    • Creates the /tmp/zmd/upgrade_final.sh shell script that automatically stops the zmd service, removes the system catalogs, and restarts the service.

    • Uses the atd server to assign a scheduled task and execute the upgrade_final.sh shell script two minutes after the post-install.sh has completed execution.

14. Click OK.

15. Click Apply at the bottom of the Details page.

16. In the RPM Package Bundle Settings section of the Details page, click Deploy to deploy the new version of the bundle.

17. Continue with Creating Catalogs for Upgrade Bundles.

1. Click the Bundles tab.

2. Click New, then click Catalog to open the Create New Catalog Wizard.

3. Specify a name for the catalog, then click Next to display the Catalog Attributes page.

4. Click Next to display the Summary page.

5. On the Summary page, click Next.

6. Click Add to display the Select Bundles dialog box.

7. Navigate to and click the desired upgrade bundle to move it to the Selected list, then click OK.

8. Click Next to display the Catalog Assignments page.

9. Click Add, navigate to and click the desired devices to move them to the Selected list, then click OK to display the Bundles Options page.

10. Click Next to display the Finish page, review the information, then click Finish.

11. Depending on your needs, continue with Upgrading Managed Devices Other Than SLES 10 and SLED 10 by Using an Upgrade Bundle or Upgrading SLES 10 or SLED 10 Managed Devices by Using an Upgrade Bundle.

1. Click the Policies tab.

2. Click New, then click Policy to display the Policy Type page.

3. Select Remote Execute Policy, then click Next to display the Policy Name page.

4. Specify a name for the policy, then click Next to display the Remote Execute Policy page.

5. From the Script to run drop-down list, choose Define your own script.

6. Paste the contents of the policy.sh script file into the Script content box. You can access the script file from the mount point /data directory.

   The Policy script performs the following tasks:

   • Subscribes to the catalog containing the upgrade bundle.

   • Installs the upgrade bundle on the managed device.

7. Edit the script so that catalog_name is the catalog you created in Creating Catalogs for Upgrade Bundles and bundle is the bundle that you specified while creating the catalog (Step 7).

8. Click Next to display the Summary page, then click Next to display the Policy Assignments page.

9. Click Add to display the Select Assignments dialog box, browse to and select the devices to which you want to assign the Remote Execute policy, then click OK.

10. Click Next to display the Policy Schedule page.

11. In the Schedule Type drop-down list, select Date Specific, specify a start date and time to apply the policy, then click Next to display the Policy Groups page.

    NOTE:If you want to verify the upgrade immediately, set the start date to today and the start time to 12 a.m. The Remote Execute policy is executed at the next scheduled refresh for the devices. Alternately, you can manually refresh the devices.

12. Click Next to display the Finish page, then click Finish.

    The Remote Execute policy is enforced as scheduled, after the managed devices’ next scheduled refresh. If the time you specified in Step 11 occurs before the next scheduled refresh, the policy is enforced on the next refresh.

    IMPORTANT:It takes approximately five minutes for the upgrade bundle to be installed and for the upgrade process to be performed. Do not perform any rug commands such as rug ref during the upgrade process. Executing rug commands during the upgrade process might cause the process to fail.

    After the upgrade completes, you can verify that the upgrade was successful by executing the rug ping command or refer to upgrade.log. The upgrade was successful if the version of zmd is 7.2.0. If you perform the rug ping command prematurely, you receive an exception message. You can recover by stopping and restarting zmd. The /tmp/zmd/upgrade.log must contain the “Starting ZENworks Management Daemon...” message in the last line.

Perform the following steps on the SLES 10 or SLED 10 managed device:

1. Execute the /usr/bin/rug sub catalog_name command, where catalog_name is the catalog assigned to the managed device.

2. Execute the /usr/bin/rug bin -y upgrade_bundle_name command, where upgrade_bundle_name is the upgrade bundle in the catalog assigned to the managed device.

   IMPORTANT:It takes approximately five minutes for the upgrade bundle to be installed and for the upgrade process to be performed. Do not perform any rug commands such as rug ref during the upgrade process. Executing rug commands during the upgrade process might cause the process to fail.

   After the upgrade completes, you can verify that the upgrade was successful by executing the rug ping command or refer to upgrade.log. The upgrade was successful if the version of zmd is 7.2.0. If you perform the rug ping command prematurely, you receive an exception message. You can recover by stopping and restarting zmd. The /tmp/zmd/upgrade.log must contain the “Starting ZENworks Management Daemon...” message in the last line.

3. If the device does not have the X Window System installed:

   1. In ZENworks Control Center, click the upgrade bundle.

   2. Click the Details tab.

   3. In the Packages panel, select the following packages:

      • novell-zenworks-x11vnc-0.6.1-2
      • novell-zenworks-zmd-gconfpolicyenforcers-7.2.1-0
      • novell-zenworks-tightvnc-1.2.9-6, zen-updater-7.2.1-0.1

   4. Click Action > Set Freshen.

4. (Optional) If SLES 10 or SLED 10 are running on DELL server and the managed devices have the default zmd agent installed, do the following if you want to collect the Dell inventory of the devices:

   1. In the Packages panel, select novell-zenworks-zmd-oem.

   2. Click Action > Unset Freshen.