L.12 April 13, 2007

Updates were made to the following sections. The changes are explained below.

L.12.1 ZENworks System Management

The following changes were made in this section:

Location

Change

Section 5.4, Freeing Disk Space on a ZENworks Server

Newly added this section.

Installing Software by Using the Software Installer

Added the following note:

NOTE:Even though the user has been assigned rights by the administrator for installing the software, the installation of bundle fails.

Section 6.4, Uninstalling the ZENworks Agent

Added the following note:

NOTE:When you uninstall ZENworks Linux Management on SLES 10 and SLED 10 managed devices, the core zmd packages such as zmd, rug, zen-updater, and zen-inventory are not removed because they are also installed as a part of the distribution. Hence, when you reinstall the ZENworks Agent on these devices, the configuration files such as zmd.conf that are associated to these packages persist.

L.12.2 Device Registration

The following changes were made in this section:

Location

Change

Section 11.3, Automatically Registering the Services at the Initial Startup of zmd

Added the following information:

If you want to use special characters such as $, !, &, ;, ‘, and “ in the key value, you must enclose the value within single quotes.

L.12.3 Policy Management

The following changes were made in this section:

Location

Change

Section 16.6, Remote Execute Policy

Added the following note in Step 10:

NOTE:If you select Day of the Week Specific as the schedule type and Start Immediately at Start Time, and then Repeat until End Time Every, and if the Start Time and End Time spans midnight, the Remote Execute policy is executed only at the Start Time, and fails to repeat execution.

L.12.4 Package and Content Management

The following changes were made in this section:

Location

Change

Section 18.0, Package and Content Management Overview

Added a sample script that can be used to upload bulk packages into the ZENworks server.

Section 21.2, Locking and Unlocking a Bundle on a Managed Device

Added the following note:

NOTE:If a locked bundle has packages, you can remove the packages from the managed device even though the bundle is locked by using rpm -e | package_name or rug rm package_name. To prevent the removal of packages, you must individually lock the packages. For more information on how to lock a package, see Section 21.1, Locking and Unlocking a Package on a Managed Device.