December 14, 2007
This document was updated in the following sections on the dates indicated.
The section entitled The ZENworks 7.2 Linux Management with IR1 installation fails on RHEL4 64-bit (x86_64) managed devices was added to Section 3.1, Installation.
The section entitled ZENworks Linux Management Imaging fails on a VMware server was added to Section 3.6, Imaging.
The issues included in this document were identified in Novell® ZENworks® 7.2 Linux Management with Interim Release 1 (IR1).
For installation instructions, see the Novell ZENworks 7.2 Linux Management Installation Guide.
For administration concepts and tasks, see the Novell ZENworks 7.2 Linux Management Administration Guide.
This section contains information about the issues that might occur when you install and use ZENworks 7.2 Linux Management with IR1.
This section contains information about the issues that might occur when you install ZENworks Linux Management.
The installation fails on Red Hat* Enterprise Linux 4 (RHEL4) 64-bit and the zlm-config file indicates that the server requires a static IP or permanent DHCP address for the ZENworks Server.
Workaround: Launch system-config-network, delete the inactive NIC (eth1), then restart zlm-config. ZENworks Linux Management should install successfully.
RHEL5 64-bit (x86_64) is not supported as a managed device. Hence, the installation of the ZENworks Linux Management Agent on RHEL5 64-bit fails even though the status of the device is displayed asin ZENworks Control Center ( > ).
If you are installing to a device that is configured with DHCP, you might encounter the following eDirectory error in zlm-config:
eDir failed to start properly. Please ensure that this machine is configured with a static IP or permanently-leased DHCP Address.
Workaround: Install ZENworks 7.2 Linux Management with IR1a on RHEL4 64-bit (x86_64) managed devices. For more information on how to install ZENworks 7.2 Linux Management with IR1a, see Novell ZENworks 7.2 Linux Management Installation Guide.
This section contains information about the issues that might occur when you upgrade ZENworks 7.2 Linux Management from a previous release.
If you try to upgrade the Novell Linux Desktop 9 (NLD 9) managed device from ZENworks 7 Linux Management with IR1 to ZENworks 7.2 Linux Management with IR1 by using upgrade bundles, the upgrade might hang.
Workaround: Manually upgrade the NLD 9 managed device from ZENworks 7 Linux Management with IR1 to ZENworks 7.2 Linux Management with IR1 by using the Novell ZENworks 7.2 Linux Management with Interim Release 1 Agent CD. For detailed information on how to manually upgrade the managed device, see the Novell ZENworks 7.2 Linux Management Installation Guide.
If the status of the database is Idle in Transaction, the ZENworks Linux Management server might hang when the schema is upgraded from ZENworks 7 Linux Management with IR1 to ZENworks 7.2 Linux Management with IR1.
Workaround: Restart the database before upgrading to ZENworks 7.2 Linux Management with IR1.
Workaround: After upgrading the ZENworks Secondary Server from ZENworks 7 Linux Management with IR 1 to ZENworks 7.2 Linux Management with IR1:
Delete ostargets.xml from ZENworks Secondary Server by executing rm /var/opt/novell/zenworks/lib/www/ostargets.xml at the server console prompt.
Copy var/opt/novell/zenworks/lib/www/ostargets.xml from the ZENworks Primary Server to /var/opt/novell/zenworks/lib/www on the ZENworks Secondary Server.
On the ZENworks Secondary Server, change the ownership of ostargets.xml to zenworks by executing chown zenworks:zenworks /var/opt/novell/zenworks/lib/www/ostargets.xml at the server console prompt.
This section contains information about the issues that might occur when you use the ZENworks database.
Using the zlm_dbrestore.sh script to restore the ZENworks database installed on a RHEL device might fail.
Workaround: To resolve this issue, see the Novell ZENworks 7.2 Linux Management Troubleshooting Guide.
This section contains information about the issues that might occur when you use the Package Management features of ZENworks Linux Management.
The use of wildcard characters using the bundle-list (bl) command to list bundles is not currently supported.
Currently, a bundle is successfully installed even though a post-distribution script fails.
When a new bundle is associated to a device on a particular schedule, the bundle is deployed or installed based on the schedule configured. However, when the bundle is modified and a newer version is deployed, any changes to the schedule do not take effect. The newer version of the bundle is installed on the next refresh.
A few pattern, patch, and product rug commands are not supported on SLES 9, RHEL, and Novell Linux Desktop.
The following 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.
Workaround: Do one of the following on the managed device:
Manually remove each package from the bundle using the rug rm package_namecommand.
Stop zmd, delete /var/opt/novell/zenworks/lib/zmd/system-catalog, and restart zmd.
Even though you can schedule to deploy and install bundles on the managed device at a specific time, date, or event through ZENworks Control Center, the bundles are deployed and installed immediately when the managed device is refreshed.
This section contains information about the issues that might occur when you use the Policy Management features of ZENworks Linux Management.
If you configure the SUSE Linux Enterprise Desktop policy for a SLED 10 managed device, you might encounter the following issues:
Theoption does not work.
If you try to remove an option that is selected in thedrop-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 relogging into the device.
On the managed device, right-click the panel, click, select from the list, then click .
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.
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.
This section contains information about the issues that might occur when you use the Imaging features of ZENworks Linux Management.
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.
Workaround: After completing the server installation, execute /etc/init.d/novell-zislnx start.
This issue does not affect installation of the ZENworks Agent on a managed device.
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.
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.
The use of a symbolic link is not supported in add-on images if the link’s location does not exist on the device where the add-on image is extracted.
The Dell* utility partition relies on its version of the MBR (master boot record) to function correctly. Grub also uses the MBR for its boot loader. If you install the Dell utility partition, then install the Linux* operating system, the Dell version of the MBR is overwritten by the grub version. Instructions to remedy this problem are found in Novell ZENworks 7.2 Linux Management Administration Guide.
However, the instructions do not work for Dell PE700 devices. For Dell PE700 devices, there is not workaround.
If you try boot a VMware server from the CD or DVD, or a ZENworks partition, the preboot services fail with the following message:
Can't find ZEN install channel, invoking manual install
Workaround: Use a USB device to boot a VMware server.
This section contains information about the issues that might occur when you use the Inventory features of ZENworks Linux Management.
A hardware inventory currently does not report some items, such as power supply for any type of device. For Red Hat machines, items such as floppy and monitor are not recognized.
On SLES 9, Novell Linux Desktop, and Open Enterprise Server managed devices, the hardware probe using the hwinfo utility might unload the lp module and consequently remove the printer device.
Workaround: Download and install the updates for the hwinfo utility. For detailed information on how to obtain the updates, see the Novell Support Web site.
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.
This section contains information about the issues that might occur when you use the Remote Management features of ZENworks 7.2 Linux Management.
When you start the Remote Login operation on a managed device, the launched session shows only a grey screen with an X cursor because XDMCP is not enabled on the managed device.
Workaround: On the managed device, do the following:
Manually enable XDMCP by executing the novell-rm-fixrl.sh script from a console session as mentioned below:
On SLES 10 and SLED 10: Execute /usr/bin/novell-rm-fixrl.sh -dm gdm -cf /etc/opt/gnome/gdm/gdm.conf enable.
On SLES 9 and Novell Linux Desktop: Execute /opt/novell/zenworks/bin/novell-rm-fixrl.sh -dm gdm -cf /etc/opt/gnome/gdm/gdm.conf enable.
On RHEL: Execute /opt/novell/zenworks/bin/novell-rm-fixrl.sh - dm gdm -cf /etc/X11/gdm/gdm.conf enable.
Start the Remote Login operation.
When starting a remote management session, the Remote Management -VNC applet randomly hangs.
Workaround: Stop and restart all running browser sessions, then retry the remote management session.
In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.
A trademark symbol (®, TM, etc.) denotes a Novell trademark; an asterisk (*) denotes a third-party trademark.
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.
Copyright © 2007 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
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.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.