11.1 Upgrading the ZENworks Servers and the Managed Devices to ZENworks 7.2 Linux Management

You can upgrade the ZENworks Linux Management Server to ZENworks 7.2 Linux Management by performing an in-place upgrade over the previous version.

Before performing any type of upgrade, do the following:

Performing an in-place upgrade lets you upgrade from a previous ZENworks Linux Management release to ZENworks 7.2 Linux Management using the same ZENworks Primary Server. For example, suppose your primary server on your ZENworks 7 Linux Management IR1 system is installed on a SLES 9 32-bit device and you want to upgrade to ZENworks 7.2 Linux Management. Using an in-place upgrade results in the previously described ZENworks Linux Management system being upgraded to ZENworks 7.2 Linux Management on that same SLES 9 32-bit device.

The upgrade process upgrades the ZENworks Server and lets you create upgrade bundles for each supported platform. The individual upgrade bundles are then pushed to assigned devices to install the new ZENworks Agent on each device.

An in-place upgrade is best suited for smaller ZENworks Linux Management systems consisting of fewer than 100 devices managed by a single ZENworks Primary Server. An in-place upgrade allows for an upgrade without scheduling down-time for the system because the server and devices are upgrading relatively quickly.

Perform the following procedures in the order listed to upgrade the ZENworks servers and ZENworks Agent software components.

  1. Performing an In-Place Upgrade on the ZENworks Primary Server

  2. Performing an In-Place Upgrade on a ZENworks Secondary Server

  3. Upgrading Managed Devices Manually or Upgrading Managed Devices by Using Upgrade Bundles

11.1.1 Performing an In-Place Upgrade on the ZENworks Primary Server

  1. Make sure the server meets the requirements. See Section 2.1, ZENworks Server Requirements.

  2. At the Linux server, mount the Novell ZENworks 7.2 Linux Management Server CD by using the mount device mountpoint command.

    For example, mount /dev/cdrom /zlm72.

    If you are using an ISO image rather than a physical CD, copy the ISO to a temporary folder on the Linux server, then mount the image using the following command:

    mount -o loop /tempfolderpath/isoimagename.iso mountpoint

    Replace tempfolderpath with the path to the temporary folder and replace mountpoint with the path to the file system location where you want to mount the image. The path specified by mountpoint must already exist.

    For example:

    mount -o loop /zlm72/ZEN72_LinuxMgmt.iso /zlm72/install

  3. Log in as root, then start the upgrade program from the mount point by running the following command:

    ./zlm-upgrade

  4. When prompted to upgrade ZENworks Linux Management, enter Y to continue.

  5. Review the Software License Agreement, pressing Page Down to scroll down the page, then enter Y to accept the agreement.

  6. Enter Y when you are asked if you are upgrading a ZENworks Primary Server.

    Make sure all ZENworks services on secondary servers are stopped. You can execute /opt/novell/zenworks/bin/zlm-config --stop to shut down the services on secondary servers.

  7. Press Enter to continue.

    The upgrade program stops ZENworks services, subscribes to the upgrade channels, upgrades RPMs, upgrades zmd, runs upgrade scripts, and then upgrades the database schema.

  8. Enter the ZENworks administrator password.

    The ZENworks services are restarted.

  9. When prompted to create bundles that can be used to upgrade zlm clients (managed devices), enter Y to continue.

    If you choose to not create upgrade bundles at this time, you can execute the zlm-upgrade -b command using the ZENworks 7.2 Linux Management Agent CD at a later time to create the bundles.

  10. Specify a folder that you want to create to hold the upgrade bundles.

  11. After the upgrade completes, refer to /var/opt/novell/log/zenworks/zlm-upgrade.log to ensure that the upgrade is successful.

  12. (Conditional) If you have ZENworks Secondary Servers to upgrade, continue with Performing an In-Place Upgrade on a ZENworks Secondary Server.

  13. Continue with Upgrading Managed Devices Manually.

    or

    Continue with Upgrading Managed Devices by Using Upgrade Bundles.

11.1.2 Performing an In-Place Upgrade on a ZENworks Secondary Server

You must upgrade the ZENworks Primary Server before upgrading ZENworks Secondary Servers. For step-by-step information, see Performing an In-Place Upgrade on the ZENworks Primary Server.

  1. Make sure the server meets the requirements. See Section 2.1, ZENworks Server Requirements.

  2. At the Linux server, mount the Novell ZENworks 7.2 Linux Management Server CD by using the mount device mountpoint command.

    For example, mount /dev/cdrom /zlm72.

    If you are using an ISO image rather than a physical CD, copy the ISO to a temporary folder on the Linux server, then mount the image using the following command:

    mount -o loop /tempfolderpath/isoimagename.iso mountpoint

    Replace tempfolderpath with the path to the temporary folder and replace mountpoint with the path to the file system location where you want to mount the image. The path specified by mountpoint must already exist.

    For example:

    mount -o loop /zlm72/ZEN72_LinuxMgmt.iso /zlm72/install

  3. Log in as root, then start the upgrade program from the mount point by running the following command:

    ./zlm-upgrade

  4. When prompted to upgrade ZENworks Linux Management, enter Y to continue.

  5. Review the Software License Agreement, pressing Page Down to scroll down the page, then enter Y to accept the agreement.

    The install program stops ZENworks services, subscribes to the upgrade channels, upgrades RPMs, upgrades zmd, runs upgrade scripts, and then restarts the ZENworks services.

  6. Enter N when you are asked if you are upgrading a ZENworks Primary Server.

  7. Enter Y when you are asked if you have upgraded the ZENworks Primary Server.

    Ignore any “failed to stop” errors that you receive. For example, you receive an error indicating that eDirectory could not be stopped, but it was already stopped when you executed /opt/novell/zenworks/bin/zlm-config --stop in Step 6.

    The upgrade program stops ZENworks services, subscribes to the upgrade channels, upgrades RPMs, upgrades zmd, and runs upgrade scripts.

    After the upgrade is complete, the ZENworks services are restarted. This might take a few minutes.

  8. (Conditional) Repeat Step 1 through Step 7 f or each ZENworks Secondary Server that you want to upgrade.

  9. Continue with Upgrading Managed Devices Manually.

    or

    Continue with Upgrading Managed Devices by Using Upgrade Bundles.

11.1.3 Upgrading Managed Devices Manually

  1. Make sure the managed device meets the requirements. See Section 2.3, Managed Device Requirements.

  2. At the Linux managed device, mount the Novell ZENworks 7.2 Linux Management Agent CD by using the mount device mountpoint command.

    For example, mount /dev/cdrom /zlm72.

    If you are using an ISO image rather than a physical CD, copy the ISO to a temporary folder on the Linux managed device, then mount the image using the following command:

    mount -o loop /tempfolderpath/isoimagename.iso mountpoint

    Replace tempfolderpath with the path to the temporary folder and replace mountpoint with the path to the file system location you want to mount the image. The path specified by mountpoint must already exist.

    For example:

    mount -o loop /zlm72/ZEN72_LinuxMgmt.iso /zlm72/install

  3. Log in as root, then start the upgrade program from the mount point by running the following command:

    ./zlm-upgrade

  4. When prompted to upgrade ZENworks Linux Management, enter Y to continue.

  5. Review the Software License Agreement, pressing Page Down to scroll down the page, then enter Y to accept the agreement.

    The install program stops ZENworks services, subscribes to the upgrade channels, upgrades RPMs, upgrades zmd, runs upgrade scripts, and then restarts the ZENworks services.

11.1.4 Upgrading Managed Devices by Using Upgrade Bundles

Upgrading managed devices to ZENworks 7.2 Linux Management installs the new ZENworks Agent.

Make sure the managed device meets the requirements. See Section 2.3, Managed Device Requirements.

Complete the following tasks in the order listed:

Creating a Script for Upgrade Bundles

  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 10) 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 is mounted. For example, if ZENworks 7.2 Linux Management 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 is mounted. For example, if ZENworks 7.2 Linux Management 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.

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.

Upgrading Managed Devices Other Than SLES 10 and SLED 10 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.

NOTE:Bundle and Package history is not migrated.

Upgrading SLES 10 or SLED 10 Managed Devices by Using an Upgrade Bundle

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.