The information in this Readme file pertains to the Update for Novell ZENworks 10 Configuration Management SP3 (10.3.3).
The following table contains information on the documentation content changes that were made in this Readme after the initial release of Update for Novell ZENworks 10 Configuration Management SP3 (10.3.3).
Table 1 Readme Updates
|
Date |
Readme Item Added or Updated |
|---|---|
|
April 06, 2011 |
In Section 5.0, What’s New, removed the information about the beta support for Windows 7 SP1 and added information about full support for Windows 7 SP1 and Windows Server 2008 R2 SP1 as managed devices. |
This version provides fixes to some of the issues discovered in ZENworks 10 Configuration Management SP3 and ZENworks 10 Patch Management SP3.
Some version 10.3.3 changes might have been included in the English version of the ZENworks 10Configuration 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.
Review the following sections:
You must consider the following guidelines to plan for the deployment of version 10.3.3 in your Management Zone:
You can directly deploy version 10.3.3 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.3) to ZENworks 11 is not supported. If you choose to deploy version 10.3.3, 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.3 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.3 is deployed. Therefore, the device reboots twice.
If you want to deploy version 10.3.3 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.3.
You must deploy version 10.3.3 first to the Primary Servers, subsequently to Satellites, and finally to managed devices.
If you have a ZENworks Configuration Management 10.3/10.3.1/10.3.2 Satellite without the Authentication role configured, and at a later time you want to add the Authentication role to it and update it to version 10.3.3, you must first deploy version 10.3.3 and subsequently configure the Authentication role.
If your Management Zone consists of ZENworks Configuration Management 10.3, 10.3.2 or 10.3.3 Primary Servers and ZENworks Configuration Management 10.2.x/10.3/10.3.1/10.3.2 managed devices and Satellites, and if you choose to deploy version 10.3.3:
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:
For instructions on downloading and deploying version 10.3.3 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.
Support for Open Enterprise Server 2 (OES 2) SP3 as Primary Server.
Support for Windows 7 SP1 and Windows Server 2008 R2 SP1 as managed devices.
The Asynchronous I/O operation has been enabled by default for the ZENworks SQLite database to improve the performance of the cache response on the managed devices. This also improves the response time with ZENworks Adaptive Agent refresh and with the deployment of policies and bundles in the terminal server environments.
You can now perform the following tasks in the Closest Server Default rule:
Remove all the Satellites from all the server lists of the Closest Server Default rule.
Add the entries of all Satellites to the server lists of the Closest Server Default rule, depending on the individual roles defined for each Satellite device.
Verify whether all ZENworks Servers are contained in the server lists of the Closest Server Default rule.
Configure the Closest Server Default rule to automatically add new Satellites to the server lists and synchronize the settings of the existing Satellites with their corresponding entries in the Closest Server Default rule.
You can now specify the number of ZENworks servers whose data must be sent to the managed devices at a time in the Closest Server Default rule and Closest Server rule. The limit that you set in the Closest Server rule overrides the limit that you set in the Closest Server Default rule.
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 7007641 in the Novell Support Knowledgebase.
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 following Readmes:
After you apply version 10.3.3 to a ZENworks Configuration Management 10.3/10.3.1/10.3.2 Satellite with the Authentication role configured, the Satellite is updated, but the Authentication role is not updated to version 10.3.3.
Workaround: Remove the Authentication role from the Satellite device, then again add the role to the device. For more information on how to remove and add the role to a Satellite, see the Satellites
section in the ZENworks 10 Configuration Management SP3 System Administration Reference.
If you choose to add content to a bundle that is created as a copy of another bundle, the new content is not replicated during the content replication schedule of a Satellite Server that is a part of a Primary Server already hosting the same content.
For example:
Assume that you have a Windows bundle named B1 and a Primary Server named P1 that has a Satellite Server, S1, with a Content Role added to it.
First, you copy B1 to create a new bundle named B2, then you edit B2 to add some content (C1) that is already available on P1. Then you configure a schedule for S1 to replicate Windows bundles at 12 midnight every Monday.
Now, if you choose to replicate B2 on S1, C1 is not replicated as a part of the configured schedule of the Satellite Server (12 midnight every Monday). However, C1 is replicated as a part of the default schedule.
Workaround: None.
There is a security vulnerability issue on Linux devices that run on 64-bit kernel which lets the local users have root data access. There is no patch update available for the SUSE Linux Enterprise Server (SLES) 10 SP2 64-bit operating system. Therefore, use your discretion while creating local users.
If there are multiple types of operating systems in an environment, and if one Primary Sever is on Windows and another Primary Server is on Linux, KB Merge might not finish in some cases. You see the following error message in ZENworks Control Center:
An error occurred during the KB Merge. If this problem persists, please contact Technical Support.
Workaround: If the first Primary Server is on Windows and the second Primary Server is on Linux, then modify the pathnames for the second Primary Server.
On the Linux Primary Server, go to var/opt/novell/zenworks/tmp/kb/pre.
Rename the following files by removing the C:\Program Files (x86)\Novell\ZENworks\conf\pru\ path:
To trigger the KB Merge process in ZENworks Control Center, select > > .
Select the products, click , then select to apply the changes.
Workaround: If the first Primary Server is on Linux and the second Primary Server is on Windows, then modify the pathnames for the second Primary Server.
In the Windows Primary Server, go to zenworks install path\novell\zenworks\temp\kb\pre.
Rename the following files by removing the /etc/opt/novell/zenworks/pru/ path:
To trigger the KB Merge process in ZENworks Control Center, select > > .
Select the products, click , then select to apply the changes.
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.