This product contains undocumented utilities that Novell Support might use to diagnose or correct problems.

2.0 Issues Resolved by Version 7.3

Some of the issues identified in the initial version of ZENworks Linux Management 7.2 IR2 have been resolved with this release. For a list of the resolved issues, see TID 3469853 in the Novell Support Knowledgebase.

3.0 Known Issues

This section contains information about the issues that might occur when you install and use ZENworks 7.3 Linux Management:

3.2.1 Upgrading from SLES 10 to SLES 11 or SLED 10 to SLED 11 by using ZENworks 7.3 Linux Management is not supported

An online upgrade from SLES 10 to SLES 11 or from SLED 10 to SLED 11 is currently not supported by SUSE Linux Enterprise. Therefore, upgrading SLES 10 or SLED 10 by using ZENworks Linux Management to SLES 11 or SLED 11 is also not supported. To upgrade SLES 10 or SLED 10 that has ZENworks Linux Management installed to SLES 11 or SLED 11, see the TID 7002790 at Novell Support.

3.2.2 Upgrading to ZENworks 7.3 Linux Management fails if the system language is French or German

3.3.1 Wildcard characters do not work when executing a bundle-list command from zlman

The use of wildcard characters using the bundle-list (bl) command to list bundles is not currently supported.

3.3.2 Some pattern, patch, and product rug commands are not supported

A few pattern, patch, and product rug commands are not supported on SLES 9, RHEL, and Novell Linux Desktop.

3.3.3 Package Update shows an incorrect status when a bundle is assigned to a server or workstation group

This might occur because the bundle is assigned to a device group and not directly to the device.

Workaround: None.

3.3.4 An incorrect message is displayed on the Secondary Server on bundle creation as well as content replication

The following incorrect message is displayed on the secondary server on successful creation of the bundle as well as content replication:

“Cannot deploy this version because one or more packages have been deleted”.

Workaround: Ignore the message.

3.3.5 Unable to mirror multiple packages from the YUM and RCE repositories with the same name and version but with different architectures to the same bundle

While mirroring multiple packages from the YUM repository, or the OES 1 monolithic package bundle from the RCE repository, with the same name and version but with different architectures, only one of the packages is mirrored to a package bundle, depending on the order in which the packages are hosted in the repository.

Workaround: None

3.4 Policy Management

This section contains information about the issues that might occur when you use the Policy Management features of ZENworks Linux Management:

3.4.1 SUSE Linux Enterprise Desktop policy issues

If you configure the SUSE Linux Enterprise Desktop policy for a SLED 10 managed device, you might encounter the following issues:

The Disable Launcher Creation option does not work.

If you try to remove an option that is selected in the Show drop-down list of the main menu file area, the main menu fails to appear. Also, if you try to unassign the policy from the managed device, the main menu still fails to appear.

Workaround: If the main menu fails to appear on unassigning the policy:

Ensure that the policy is removed from the device by refreshing the managed device and logging in to the device again.

On the managed device, right-click the panel, click Add to Panel, select Main Menu from the Add to Panel list, then click Add.

3.4.2 The previous background settings of the SLED 10 managed device are not restored after the SLED policy is unenforced

On a SLED 10 managed device, if you unenforce the SLED policy in which the background image filename is configured, the previous background settings of the device are not restored.

Workaround: Log in to the managed device again.

3.4.3 The system area of the SLED 10 SP1 managed device disappears when you try to remove the system menus by using the SLED policy

If you enforce the SLED policy that is configured to remove the system menus from the system area, the system area on the SLED 10 SP1 managed device disappears.

Workaround: Remove the settings from the SLED policy and reassign the policy to the SLED 10 SP1 managed device.

3.4.4 The Event based schedule is displayed in the Schedule Type drop-down list for Remote Execute Policy and Text File Policy

When you assign a Remote Execute Policy or a Text File Policy from the Action menu in the ZENworks Control Center, the Event based schedule is displayed in the Schedule Type drop-down list, even though this schedule is not supported for these policies in ZENworks 7.3 Linux Management.

Workaround: None

3.5 Imaging

This section contains information about the issues that might occur when you use the Imaging features of ZENworks Linux Management:

3.5.1 After installing ZENworks Linux Management on a server, some image safe data is missing or incorrect

If you take an image of a server just after installing ZENworks Linux Management (that is, before zislnx-start has a chance to run again at boot), the image is restored with an incorrect network configuration and hostname.

This issue does not affect installation of the ZENworks Agent on a managed device.

3.5.2 The imaging server does not support double-byte characters in the name of the image file

The Imaging engine does not support double-byte characters in image filenames. The ZENworks Control Center allows you to enter a double-byte character, but the Imaging Server does not recognize it. Therefore, do not use double-byte characters in the names of image files.

3.5.3 zislnx fails to shut down on RHEL 3 devices

On Red Hat* Enterprise Linux 3 (RHEL 3) devices, using the /etc/init.d/novell-zislnx stop command fails to shut the service down. At some later time, the device then fails to respond to a soft reboot, and must be cold-booted.

The error message displayed when running /etc/init.d/novell-zislnx stop is incorrect, because RHEL 3 does not follow LSB standards.

Workaround: Do not use the /etc/init.d/novell-zislnx stop command. Normally, you would not run this command, because when /etc/init.d/novell-zislnx is run from either a bash prompt or at boot-up, it runs once then stops itself.

If you create a CPU-based registration rule to filter Intel* Pentium* processors for registering the managed device to the server, the Inventory Scanner utility (hwinfo) captures the CPU model name as "Pentium(R) 4 processor 2800 MHz" instead of "Intel(R) Pentium(R) 4 CPU 2.80GHz" for some machines; the prefix Intel is omitted. Consequently, the registration of the device to the server might fail.

Workaround: None.

3.7 Remote Management

This section contains information about the issues that might occur when you use the Remote Management features of ZENworks Linux Management:

5.0 Legal Notices

Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.

Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to http://www.novell.com/info/exports/ for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.

Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.novell.com/company/legal/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.