Update for ZENworks 10 Configuration Management SP3 (10.3.2)

This version provides fixes to some of the issues discovered in ZENworks 10 Configuration Management SP3, ZENworks 10 Asset Management SP3, and ZENworks 10 Patch Management SP3.

Some version 10.3.2 changes might have been included in the English version of the ZENworks 10 Configuration Management SP3 guides after they were translated into other languages. We recommend that you check the English documentation for a complete list of the documentation updates. All untranslated documentation updates will be incorporated into the non-English versions of the online documentation with the next media release of ZENworks.

3.0 Deploying Version 10.3.2

Review the following sections:

Section 3.1, Planning to Deploy Version 10.3.2
Section 3.2, Downloading and Deploying Version 10.3.2

3.1 Planning to Deploy Version 10.3.2

You must consider the following guidelines to plan for the deployment of version 10.3.2 in your Management Zone:

You can directly deploy version 10.3.2 to Primary Servers, Windows Satellites, Linux Satellites, and managed devices that have ZENworks 10 Configuration Management SP3 (10.3 or later) installed.
Upgrading from ZENworks 10 Configuration Management SP 3 (10.3.2) to ZENworks 11 is not supported. If you choose to deploy version 10.3.2, you can directly upgrade to ZENworks 11.1 after ZENworks 11.1 is released.
If your Management Zone consists of ZENworks Configuration Management 10.2.x Windows Satellites and managed devices, you can deploy version 10.3.2 to the devices only if the ZENworks 10 Configuration Management SP3 update has been downloaded and is available in the Management Zone. The ZENworks 10 Configuration Management SP3 update is deployed first, and subsequently version 10.3.2 is deployed. Therefore, the device reboots twice.
If you want to deploy version 10.3.2 to a Linux Satellite that has ZENworks Configuration Management 10.2.x installed, you must first upgrade it to ZENworks 10 Configuration Management SP3 (10.3 or later), and subsequently deploy version 10.3.2.
You must deploy version 10.3.2 first to the Primary Servers, subsequently to Satellites, and finally to managed devices.

If your Management Zone consists of ZENworks Configuration Management 10.3 or 10.3.1 Primary Servers and ZENworks Configuration Management 10.2.x/10.3/10.3.1 managed devices and Satellites, and if you choose to deploy version 10.3.2:

Ensure that the ZENworks Configuration Management version of a managed device is earlier than or the same as the ZENworks Configuration Management version of its Satellite and Primary Server.
Ensure that the ZENworks Configuration Management version of the Satellite is earlier than or the same as the ZENworks Configuration Management version of its Primary Server.

Refer to the following table to understand the ZENworks Configuration Management support matrix:

Managed Device	Satellite Servers	Primary Servers
v10.2	v10.2, v10.2.1, v10.2.2, v10.3, v10.3.1, v10.3.2	v10.3.2
v10.2.1	v10.2.1, v10.2.2, v10.3, v10.3.1, v10.3.2	v10.3.2
v10.2.2	v10.2.2, v10.3, v10.3.1, v10.3.2	v10.3.2
v10.3	v10.3, v10.3.1, v10.3.2	v10.3.2
v10.3.1	v10.3.1, v10.3.2	v10.3.2
v10.3.2	v10.3.2	v10.3.2

3.2 Downloading and Deploying Version 10.3.2

For instructions on downloading and deploying version 10.3.2 as an update, see “ZENworks System Updates” in the ZENworks 10 Configuration Management System Administration Reference.

For administrative tasks, see the Novell ZENworks 10 Configuration Management documentation Web site.

4.0 What’s New

The primary focus in the 10.3.2 release is to address bug fixes. There are no new or enhanced features included as a part of this release.

5.0 Issues Resolved by Version 10.3.2

Some of the issues identified in the initial version of ZENworks 10 Configuration Management SP3 have been resolved with this release. For a list of the resolved issues, see TID 7007237 in the Novell Support Knowledgebase.

6.0 Product Issues

Section 6.1, Continuing Issues in ZENworks 10 Configuration Management SP3
Section 6.2, Known Issues in Version 10.3.2

6.1 Continuing Issues in ZENworks 10 Configuration Management SP3

Some of the issues that were discovered in the original shipping version of ZENworks 10 Configuration Management SP3 have not yet been resolved. For continuing issues, review the ZENworks 10 Configuration Management SP3 Readme and the ZENworks 10 Configuration Management SP3 (10.3.1) Readme.

The Readmes have been updated to indicate which issues are fixed by version 10.3.2.

6.2 Known Issues in Version 10.3.2

The NetWare inventory-only device object is created in ZENworks Control Center only after the next device refresh schedule
RHEL 3.x servers are not supported as Inventory-only managed devices
Users can register in to an agent with different registration keys without providing administrator credentials
The system update fails if the database migration is performed after downloading and before deploying the system update

6.2.1 The NetWare inventory-only device object is created in ZENworks Control Center only after the next device refresh schedule

If you deploy an inventory-only agent on a NetWare server, the server object is created in ZENworks Control Center only on the next device refresh schedule and not immediately after the agent deployment. By default, the device refresh is scheduled for the first day of every month.

For more details, see TID 7005720 in the Novell Support Knowledgebase.

6.2.2 RHEL 3.x servers are not supported as Inventory-only managed devices

If you run an inventory scan on inventory-only managed devices, RHEL 3.x servers are not displayed in the scan reports.

Workaround: For detailed steps to address this issue, see TID 7007582 in the Novell Support Knowledgebase.

6.2.3 Users can register in to an agent with different registration keys without providing administrator credentials

A user who does not have administrator credentials can register in to both Windows and Linux managed devices by using either the Z icon icon or zac commands.

Workaround: To enable authentication to log in to the Windows or Linux devices, do one of the following:

To enable the authentication on a Windows agent, create a registry string AUTHENTICATE_ARK in the \HKEY_LOCAL_MACHINE\SOFTWARE\Novell\ZCM\ directory and then set the value to TRUE.
On Linux Satellite servers, add the configuration parameter AUTHENTICATE_ARK=TRUE in the /etc/opt/novell/zenworks/conf/xplatzmd properties file.

6.2.4 The system update fails if the database migration is performed after downloading and before deploying the system update

If you perform a database migration between downloading and deploying the system update, the zSystemUpdateDeviceInfo table creates spaces in some fields, and the update fails.

Workaround: Delete the system update from the ZENworks Control Center and download it again.

7.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 the Novell International Trade Services Web page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.

Copyright © 2011 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 on the Novell Legal Patents Web page 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.