Novell® ZENworks® for Servers (ZfS) 3.0.2 is a CD reissue of ZfS 3 that also contains updates to the ZfS software for integration and interoperability with the other products in the ZENworks suite, including ZENworks for Desktops (ZfD) and ZENworks for Handhelds (ZfH). ZfS 3.0.2 contains all bug fixes contained in ZfS 3 Support Pack 1 (SP1) and ZfS 3 Support Pack 2 (SP2).
The ZENworks for Servers Program, ZENworks 6 Server Management Program CD, or the ZfS 3 SP2 download each perform the same software update for both ZfS 3 and ZfS 3 SP1. However, an upgrade from ZfS 2 can only be performed using the Program CD.
For a history of bug fixes between ZfS 3 and ZfS 3.0.2, see the ZfS 3 SP2 Readme, which is available on the ZfS 3.0.2 documentation Web site, or in the SP2 download.
Readme Updates
Items are marked (New) that have been added to this version of the Readme. The Readme was updated in the following sections on the dates indicated:
April 15, 2003 = 7.6
June 27, 2003 = 4.2
August 15, 2003 = 1.0 (support for NetWare 6.5)
February 2, 2005 = 6.1.14 (OES issue)
Table of Contents
ZfS 3.0.2 includes the following components:
ZfS 3.0.2 supports interoperability with ZENworks for Destkops (ZfD) 4.0.1. For information on installation issues between the products, see 3.1 Installation Issues for ZfS 3.0.2 and ZfD 4.0.1 Interoperability .
(New) ZENworks for Servers 3.0.2 (including version 3 SP2) supports NetWare 6.5 when you apply the latest ZENworks update. See the ZENworks for Servers 3.0.2 Update for NetWare 6.5 Readme for information about obtaining the update and other information about using ZENworks for Servers with NetWare 6.5. The update files can be obtained from TID 10083888 on the Novell Support Web site.
This Readme file provides the latest information on known issues and other product information that is not in the ZfS documentation.
The Installation guide, available from the installation program (via a PDF file in the DOCUMENT subdirectory of the Program CD), provides detailed initial ZfS installation and setup instructions. This guide is also available on the ZfS 3.0.2 documentation Web site, and is periodically updated on the Web site. For important installation issues, review this guide before beginning to install ZfS 3.0.2.
The Administration guide, available from the installation program via a link to the ZfS 3.0.2 documentation Web site, provides additional instructions for expanding your ZfS installation throughout your network.
To install ZfS 3.0.2, follow the instructions in the Installation guide.
Do not run the installation program on a Windows* 95/98 workstation. You must use a Windows NT*/2000 workstation.
To install ZfS 3.0.2 and ZfD 4.0.1 to the same server, you must install ZfS 3.0.2 in the same directory location where you have installed ZfD 4.0.1. For example, the default installation directory is ZENWORKS for both products.
When installed to the same network location, ZfS 3.0.2 and ZfD 4.0.1 give you the ability to manage and distribute software, files, and applications, to monitor the network's usage and health, and to enforce network policies, all from a central location.
You can upgrade from ZfS 2, ZfS 3, or ZfS 3 SP1 to ZfS 3.0.2 using the Program CD.
However, there is one exception: you cannot upgrade ZfS 2 Management and Monitoring Services to ZfS 3.0.2. You can only upgrade ZfS 3 or ZfS 3 SP1 Managing and Monitoring Services to ZfS 3.0.2.
There is no direct upgrade available from ZfS 1.0 to ZfS 3.0.2.
If you are a current ZfS 2 Policy and Distribution Services customer, you can incrementally upgrade to ZfS 3.0.2 Policy and Distribution Services where ZfS 2 can continue to be used. For more information, see "Issues Concerning Upgrading Incrementally" under "Understanding Upgrading from ZfS 2 to ZfS 3" in "Upgrading Policy and Distribution Services" in "Upgrading from ZENworks for Servers 2" in the Installation guide.
For Policy and Distribution Services, select the Upgrade from ZfS 2 option.
For Management and Monitoring Services, select the Install Management and Monitoring Services option. You can also choose to uninstall the previous version of ZfS or install ZfS 3.0.2 over the existing version of ZfS.
For the other ZfS components, select New Installation; the upgrade will occur automatically during installation.
For additional instructions, see Upgrading from ZENworks for Servers 2 in the Installation guide.
If you are a current ZfS 3 or ZfS 3 SP1 customer, you can install ZfS 3.0.2 in an environment where ZfS 3 or ZfS 3 SP1 is already in use.
For Policy and Distribution Services, select the Upgrade from ZfS 3 option, not the Install/Upgrade option. (New:) Also, to upgrade the ConsoleOne snap-ins and iManager plug-ins, you must use the Install/Upgrade and Install Web Components options, because these components are not included in the Upgrade from ZfS 3 option.
IMPORTANT: In upgrading Distributors and Subscribers, you can upgrade only one type at a time, usually the Distributors first. For servers running both the Distributor and Subscriber software, you only need to upgrade those servers once when you upgrade the Distributors. You do not need to repeat upgrading those particular servers when you upgrade your Subscribers.
For Management and Monitoring Services, select the Upgrade Site Management Services from ZfS 3 or ZfS 3 SP1 to ZfS 3.0.2 option.
For the other ZfS components, select Install/Upgrade; the upgrade will occur automatically during installation.
For additional instructions, see Upgrading from ZENworks for Servers 3 in the Installation guide.
The following sections list the ZfS 3.0.2 software issues that are known for Management and Monitoring Services.
If SNMP traps arrive faster than four traps per second, continuously for more than four hours, you might experience the following problems:
The Traffic Analysis Agent falsely generates a Duplicate IP alarm for machines where the same IP address is bound to two Media Access Control (MAC) addresses. After the two MAC addresses have been discovered, the false Duplicate IP alarm will not be generated again.
When you print an Atlas view for which wallpaper has been imported for the map, the wallpaper does not print.
You cannot move a machine from one switch port to another.
While creating a backup directory, do not use extended or double-byte characters in the backup directory name. This is a limitation with Sybase*.
On NetWare IP and IPXTM routers that are configured with unnumbered addresses, discovery fails to create a correct topology.
To work around this problem, try using the Database Object Editor to manually create the correct topology linking the routers.
The following sections list the ZfS 3.0.2 software issues that are known for Policy and Distribution Services.
The following installation issues that are known for Policy and Distribution Services.
To upgrade ZfS 3 Policy and Distribution Services to ZfS 3.0.2 using the Program CD, you should use the upgrade option (Upgrade from ZfS 3), not the installation option (Install/Upgrade). The Upgrade from ZfS 3 option and Install/Upgrade option provide the same end result.
However, if you use the Install/Upgrade option for ZfS 3 servers, Policy and Distribution Services will not start unless you also do the following after installing. The following sections provide a workaround if you use the installation option. This workaround does not need to be applied if you upgrade ZfS 3 SP1 servers to 3.0.2 using the Install/Upgrade option.
IMPORTANT: In the following workarounds, the default installation paths are given (such as SYS:\ZENWORKS or C:\ZENWORKS). Alter these paths in the examples to match installation paths that you actually use.
On the ZfS 3 NetWare server where you installed ZFS 3.0.2, edit the ZFS.NCF file (located at SYS:\ZENWORKS\PDS\SMANAGER) by adding the following line:
envset smclasses=$smclasses;sys:\zenworks\zws\xmlrpcextres.jar
On the same server, edit the TED.NCF file (located at SYS:\ZENWORKS\PDS\TED) by adding the following line:
envset tedpath=$tedpath;sys:\zenworks\zws\xmlrpcextres.jar
On the same server, edit the ZWS.NCF file (located at SYS:\ZENWORKS\ZWS) by adding the following lines:
envset zwspath=$zwspath;sys:\zenworks\zws\zenwebserverres.jar
envset zwspath=$zwspath;sys:\zenworks\zws\xmlrpcextres.jar
Repeat these steps for every ZfS 3 NetWare server where you installed ZfS 3.0.2 from the Program CD.
On the ZfS 3 Windows server where you installed ZFS 3.0.2, edit the ZFSSRV.CFG, TEDSRV.CFG, and ZWSSRV.CFG files (located at C:\ZENWORKS\PDS\BIN) by adding the following line in each file:
CLASSPATH="c:\ZENworks\ZWS\ZenWebServerRes.jar;c:\ZENworks\ZWS\xmlrpcextRes.jar;"
Repeat these edits on every ZfS 3 Windows server where you installed ZfS 3.0.2 from the Program CD.
Set the Colors display setting to something higher than 16 Colors before running the installation program.
When you are browsing for an installation location on a NetWare 6 server, you might not initially see all the directories in the file system. Occasionally, it can take up to 10 seconds to display the entire file system contents.
Do not install Policy and Distribution Services to a subdirectory with a path that exceeds 250 characters.
Because NetWare uses a DOS code page instead of a Windows code page, double-byte or extended characters cannot be used for paths contained in .NCF files. During installation, ZfS updates .NCF files with installation path information. Therefore, do not use double-byte or extended characters in any part of an installation path, including a NetWare volume name.
When installing Policy and Distribution Services in a very large Novell eDirectoryTM tree, the rights for some Subscriber objects may not be set and you may receive the following message:
Failed to set rights for Subscriber_server.context
You do not have rights to modify the NCP Server object: server.context
To correct the problem, make the Subscriber object a trustee of its corresponding Server object in ConsoleOne®.
The installation program does not permit you to install from a private network onto a public network across a firewall. Run the installation program on a workstation on the public network to perform the installation.
If you want to install Policy and Distribution Services on the same server with Server Inventory, you must install Policy and Distribution Services first because Server Inventory has a dependency on Policy and Distribution Services.
You cannot install Policy and Distribution Services to a cluster if the common name of the Cluster object is longer than 31 characters. If you attempt to do so, you receive an error indicating that the cluster is down, even though the cluster is running. The error occurs because DNS name resolution truncates the cluster name to 31 characters and consequently cannot resolve it.
There is no workaround.
The following are known installation issues.
Select multiple components in the Components to Install dialog box only if you want to install all selected components to the same set of servers. If you want to install each component to a different set of servers, run the installation program for each component, rather than selecting multiple components.
If you select multiple components in the Components to Install dialog box and then cancel the installation during the file copy operation of the Policy and Distribution Services installation, the Server Inventory and Remote Management installation will still start. It is a separate program that must be canceled separately.
The following are known installation issues.
The Policy and Distribution Services snap-in to ConsoleOne cannot be installed on Linux* and Solaris*. Install ConsoleOne 1.3.5 to a Windows workstation or server and use the installation program (WINSETUP.EXE) to install the Policy and Distribution Services snap-in to that location.
If you are installing Policy and Distribution Services on a Red Hat* Linux 7.1 or newer server where X Windows is not installed, the default libraries do not meet the requirements of the JRE that will be installed with the Policy and Distribution Services software. Go to the Sun Web site for an explanation of the problem and the solution you need to implement before installing Policy and Distribution Services.
The following are known upgrade issues.
When you install the ZfS 3.0.2 snap-ins to ConsoleOne over the ZfS 2 snap-ins, the Type property page of the Distribution object is empty when displayed in ConsoleOne.
To correct the problem, delete the following file from the ConsoleOne installation:
ConsoleOne_path\SNAPINS\TED\TEDNALAGENT.JAR
If you upgrade a server that was only a Distributor or only a Subscriber from ZfS 2 to ZfS 3.0.2 and then later decide to increase its functionality to both Distributor and Subscriber, you must run the installation for both objects, not just for the object you want to add. If you do not, the new functionality replaces the original functionality, rather than being added to it.
The ZfS Database (ZFSLOG.DB) cannot be upgraded from ZfS 2 to ZfS 3.0.2. Rename or delete the old database, so that a new one can be created, or install the ZfS 3.0.2 database on a different server.
If you have created server software packages using the ZfS 2 snap-in to ConsoleOne, you cannot edit those packages using the ZfS 3.0.2 snap-in to ConsoleOne, although the compiled server software packages (*.CPK files) will continue to work normally.
However, you can edit ZfS 2 software packages with the ZfS 3.0.2 snap-ins after you have converted those packages to version 3. You can do this in ConsoleOne by selecting the Server Software Packages namespace, then click File > Actions > Convert Software Package to Version 3.
The upgrade process does not allow you to select specific containers to search for ZfS 2 objects. It automatically searches the entire tree and provides a list of objects to select for upgrade.
If the upgrade process does not initially locate all ZfS 2 objects in the tree, upgrade those it has located and then select the Upgrade option again to rescan the tree for additional ZfS 2 objects.
If you install the GroupWise® 6 snap-in to ConsoleOne after you have installed the Policy and Distribution Services snap-in to ConsoleOne, you might encounter some ConsoleOne functionality problems, including:
To correct the problem, re-install the Policy and Distribution Services snap-in to ConsoleOne. It uses a more recent XERCES.JAR file, which GroupWise can also use successfully.
This problem does not apply to GroupWise 6.5.
When NetWare 6.5 servers are upgraded to SP3 (NetWare OES), a newer JVM* is installed that is incompatible with the zencommon.jar file used by ZfS 3.0.2, so the Server Policies and Server Software Package functionalities no longer work.
Workaround: Replace the outdated zencommon.jar file with the updated version that works with the JVM that ships with NetWare 6.5 SP3/NetWare OES. To download the newer zencommon.jar file, see TID ######## on the Novell Support Web site.
The following are known Tiered Electronic Distribution (TED) issues.
Do not create TED objects with names that include special characters (for example, < > ` & ^ $ # * and so on). Objects with special characters in their names cannot be managed using the ZfS Management role in Novell iManager. Use only alphanumeric characters in TED object names.
Do not use extended or double-byte characters in TED object names. The Sybase database engine that writes to the Policy/Distribution Database cannot log entries that include such characters.
Do not use periods or double quotes in TED object names. For example, you cannot name an External Subscriber object after the fully qualified host name of the server it represents (such as server47.novell.com or "server47.novell.com").
Do not create TED objects in containers that have a slash (/) in the Organizational Unit name. The Distributor Agent will not start if the container where the Distributor object resides contains a slash.
Do not use the euro character in TED object names and containers.
Do not use double-byte characters that end with 5C in the names of directories and files that will be gathered into Distributions. Double-byte characters that end with 5C are currently read incorrectly by the NetWare JVM, so that the Distribution cannot be built successfully. The problem will be addressed in a future release of the JVM.
On a server with multiple NICs, you need to know the primary address (IP address or DNS host name) of the server in order to set up XMLRPC security and data encryption. You can obtain this information from the DISTEVENT.TED log in the installation_path\ZENWORKS\PDS\TED directory. This information is not currently available in the TED.LOG or DEFAULTLOG.TXT files.
If a Subscriber receives a Distribution that contains a variable for which the Subscriber does not have a value, the Distribution cannot be successfully extracted. Under such circumstances, errors are written to the Subscriber log file on disk but are not reported in the Subscriber Event Log available from the Remote Web Console in Novell iManager.
If a Subscriber receives an encrypted Distribution certificate before it receives an unencrypted Distribution, it will fail to receive the Distribution. Send encrypted Distribution certificates only after an unencrypted Distribution has been successfully received by the Subscriber.
If you send a Policy Package Distribution to an external Subscriber, the Subscriber event log indicates that the Distribution was received and extracted successfully. However, the Policy/Package Agent has not actually processed the package.
As a workaround, add the trusted tree and the distinguished name of the trusted Distributor to the AGENTINFO.PROPERTIES file in the TED subdirectory of the Policy and Distribution Services installation directory on the external Subscriber server.
You can start Policy and Distribution Services on a Windows server by starting the Novell ZfS Policies service. However, to stop Policy and Distribution Services, you must individually stop the Novell ZfS Policies service, the Novell ZfS Distribution service, and the Novell Zen Web Server service.
It is preferable to avoid DNS issues before they occur. For assistance with correctly setting up DNS, see Ensuring Successful DNS Name Resolution in Appendix A: Installing Supporting Software To Meet ZfS System Requirements in the Installation guide before you install Policy and Distribution Services.
If you run the Distributor or Subscriber Agent on a NetWare server where DNS is not correctly set up, the Network Address field on the Other tab of the Distributor or Subscriber object will have incorrect information.
To correct the network address information in ConsoleOne:
Right-click the Distributor or Subscriber object > click Properties > Other.
Expand Network Address > click the network address > click Modify.
Click the Network Address button to open the Extended Editor dialog box.
In the NetAddress Type field, select IP > select Type_13 again. (This works around a known ConsoleOne defect.)
Click the NetAddress button to open the Extended Editor.
In the ASCII box, correct the network address information > click OK.
Click OK to close the Extended Editor dialog box > click OK to close the Distributor or Subscriber object properties dialog box.
If you run the Distributor Agent on a NetWare server where DNS is not set up correctly, then resolve certificates for Subscribers that receive Distributions from the Distributor, and afterwards correct the problems with the DNS setup, the Distributor server's primary address and DNS host name do not match. As a result, Distributions cannot be successfully sent to Subscribers.
To successfully copy the certificates:
Stop the Distributor Agent.
Delete the .KEYSTORE file from install_dir\ZENWORKS\PDS\SECURITY.
Restart the Distributor Agent.
Resolve the certificates again for all Subscribers that receive Distributions from the Distributor.
If DNS is not available when a Distribution is sent to a Subscriber, an exception displays on the Distributor Agent console on a NetWare server. This is an informational message and does not present a problem.
Occasionally, a Distributor Agent running on a server where eDirectory is not installed is unable to connect to eDirectory and reports the following error:
Error -748, A Conn Timeout error occurred
Restart all the Policy and Distribution agents that are running on the server.
Occasionally, the Distributor Agent fails to start and displays the following message:
Authenticated Identity is Distributor_object.context
If you try again, the Distributor Agent should start successfully.
When you resolve certificates by copying them to a Linux Subscriber, check the following directory to make sure that the copy operation was successful:
/usr/ZENworks/PDS/ted/security/private
No error will be reported if the copy operation was not successful, but you will not be able to send Distributions successfully to the Subscriber unless the certificates have been copied.
ZfS creates diskhash files for each File type of Distribution, so that if synchronization is enabled, ZfS will have the information it needs to provide synchronization. The diskhash file is a record of the entire directory structure from the location where the File Distribution is sent.
Therefore, if you send a Distribution to the root of a volume or drive, ZfS could create a very large diskhash file there. For example, a 60 MB diskhash file could be created for a 200 KB Distribution.
You should send File type Distributions to directories where the structure beneath is applicable to the content of the File Distribution.
Although you can specify the order for processing Server Software Packages that are contained in a Distribution, this order is not guaranteed. This is because the length of time it takes for software packages to finish processing can be different for each package, and it is the finishing time for when a software package has completed processing that determines its rollback order.
In other words, you can only roll back the last software package that was successfully processed, and other software packages only in the reverse order of when they finished processing.
You can use the Package List command to view the order in which software packages finished processing. An asterisk marks the next package that is available for rollback.
The following are known Policy Package issues.
If you are using the SNMP Trap Targets policy, the native SNMP stack must be loaded on the server before the SNMP Trap Targets policy can be enforced. If it is not loaded, an error will occur when the Policy/Package Agent attempts to enforce the policy.
The following are known Server Software Package issues.
If you insert a server software package into the Server Software Package namespace in ConsoleOne and subsequently delete the server software package (.SPK) file from the file system, the reference to the deleted .SPK file still displays in ConsoleOne. Manually delete the reference from the Server Software Package namespace.
The following are known ZfS Management Role issues.
Some Unicode* characters used by certain locales might cause Novell iManager to display errors. To prevent this problem:
Edit the SERVER.XML file in the CONF subdirectory of your Tomcat installation.
Search for DecodeInterceptor.
Set the line as follows:
<DecodeInterceptor defaultEncoding="UTF8" />
Save the SERVER.XML file.
Edit the EMFRAME.CFG file in the WEBAPPS\EMFRAME\WEB-INF subdirectory of your Tomcat installation.
Search for Charset.default.
Under the Default User Charset section, uncomment the following line:
Charset.default=utf-8
Save the EMFRAME.CFG file.
Stop and then restart Tomcat.
If a Software Package Distribution is successfully received but the extraction fails, the Tiered Distribution View provided by the ZfS Management role in Novell iManager shows that the extraction was successful.
As a workaround, use the ZfS Management role in Novell iManager to check the extraction status of a Distribution:
In Novell iManager, expand the ZfS Management role > click Remote Web Console.
Specify a server or a TED object.
In the Available Services field, select Tiered Electronic Distribution.
Click the Distributions tab > click Received Distributions.
Select the Distribution to check the extraction status for > click OK.
The following sections list the ZfS 3.0.2 software issues that are known for Server Inventory.
The Inventory database (ZENINV.DB) cannot be upgraded from ZfS 2 to ZfS 3.0.2.
If you have installed Server Inventory before installing Policy and Distributions Services on the same NetWare server, do the following before starting Policy and Distribution Services:
On the NetWare Inventory server, note the value of the ZWSPath key in the SYS:\SYSTEM\ZENWORKS.PROPERTIES file.
At the NetWare Inventory server console prompt, enter the following command:
SEARCH ADD ZWSPath_value
Start the Policy and Distribution services.
Do not install ZfS 3.0.2 Server Inventory and ZfD 3.x Workstation Inventory on the same machine. Also, be aware of the following inventory data storage limitations:
ZfS 3.0.2 requires ZfD 4.0.1 to be installed to ensure interoperability. For example, if you have a server where you have installed ZfD 4 and ZfS 3 SP1, you must upgrade the server to ZfD 4.0.1 and ZfS 3.0.2.
Do not use double-byte characters that end with 5C in the names of Server Inventory directories and files. Double-byte characters that end with 5C are currently read incorrectly by the NetWare JVM. The problem will be addressed in a future release of the JVM.
Do not use the euro character in the names of Server Inventory directories and files.
When installing the Inventory Agent from a Terminal server using the Local Machine option, the installation copies the INVSETUP.INI file to the C:\DOCUMENTS AND SETTINGS\ADMINISTRATOR\WINDOWS directory.
To work around this problem, copy the INVSETUP.INI file to the C:\WINNT\ directory or the WINDIR directory to enable the Inventory Agent to work properly.
The following sections list the ZfS 3.0.2 software issues that are known for Remote Management.
The display adapters listed below do not support the Screen Blanking feature of Remote Management. The managed workstation screen will not be blanked when these adapters are used.
IMPORTANT: Some of the following adapters may cause the managed workstation to hang or crash.
In addition, the Screen Blanking feature does not work on any display adapter that is not 100% VGA compatible.
If a managed server is configured with one of the following video drivers:
then the Optimization driver functionality will not be available for a Remote Management session with the managed server.
If a managed server has a full-screen DOS window open, you cannot establish a Remote Management session with it.
During a Remote Control or Remote View session, the active desktop wallpaper on the managed server may not be suppressed by the Remote Management Agent.
To improve performance, suppress the wallpaper before starting the remote 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.
You may not export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside.
Copyright © 2003 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.
U.S. Patent Nos. 5,910,803 and 6,067,093. US and Foreign Patents Pending.
Novell, NetWare, ConsoleOne, GroupWise, and ZENworks are registered trademarks of Novell, Inc. in the United States and other countries.
eDirectory and NLM are trademarks of Novell, Inc.
Novell Technical Services is a service mark of Novell, Inc.
All third-party products are the property of their respective owners.