This Readme has been updated for ZfS 3 SP1. Including bug fixes for ZfS 3, SP1 provides interoperability with ZENworks for Desktops (ZfD) 4. For information on what changes were made by SP1, see the Readme that is provided in the ZfS 3 SP1 download.
Items marked (New) have been added to this version of the Readme after the ZENworks for Servers product CD was created. The Readme was updated in the following sections on the dates indicated:
April 15, 2002 = 5.7; 6.1.13; 7.1; 7.2; 7.3
June 7, 2002 = 3.1
July 15, 2002 = 6.1.5
August 27, 2002 = 1.0; 3.3
October 1, 2002 = Updated various known issues that were fixed with SP1 by appending (Fixed in SP1) to the applicable heading, or appending (For this paragraph only, fixed in SP1) to the applicable paragraph.
October 8, 2002 = 6.2.19; 6.2.20; 6.2.21
Novell ZENworks for Servers (ZfS) 3 includes the following components:
With the release of ZENworks for Destkops (ZfD) 4, ZfS 3 supports interoperability with ZfD 4. For information on installation issues between the products, see section 3.3 Installation Issues for ZfS 3 and ZfD 4 Interoperability. (New)
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 Wizard and as a PDF file in the DOCUMENT subdirectory of the CD, provides detailed initial ZfS installation and setup instructions.
The Administration guide, available from the Installation Wizard, provides additional instructions for expanding your ZfS installation throughout your network.
Both of these guides are also available at the Novell Documentation site. Review these guides as well as this Readme before beginning to install ZfS 3.
To install ZfS 3, follow the instructions in the Installation guide.
Do not run the Installation Wizard on a Windows 95/98 workstation. You must use a Windows NT/2000 workstation.
3.1 Deploying ZfS 3 in a Mixed eDirectory Environment (New)
ZfS 3 requires Novell eDirectory 8.x to be installed. If all servers in the eDirectory tree are running eDirectory 8.x, the product will function without any issue. However, installing ZfS 3 in a mixed eDirectory environment (any server in the directory tree containing an earlier version of eDirectory, such as NDS 6.x or 7.x), will cause schema synchronization to fail, resulting in the error code 652. This fix is available in the newer version of the ZENworks for Servers product CD (identified by the Readme file date of 5/24/2002).
3.2 Server Platforms for Installing ZfS Components
Management and Monitoring Services can be installed on the following server platforms:
- NetWare 5.1
- NetWare 6
- Windows NT
- Windows 2000
Policy and Distribution Services can be installed on the following server platforms:
- NetWare 5.1
- NetWare 6
- Windows NT
- Windows 2000
- Linux kernel version 2.4.x as tested with Red Hat 7.1/7.2
- Solaris 8
Server Inventory can be installed on the following server platforms:
- NetWare 5.1
- NetWare 6
- Windows NT
- Windows 2000
Remote Management can be installed on the following server platforms:
- NetWare 4.2
- NetWare 5.0
- NetWare 5.1
- NetWare 6
- Windows NT
- Windows 2000
3.3 Installation Issues for ZfS 3 and ZfD 4 Interoperability (New) (Fixed in SP1)
When installed to the same network location, ZfD 4 and ZfS 3 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.
Applying ZfS 3 Support Pack 1 (SP1) will correct the following interoperability issues. ZfS 3 SP1 will be available for download at a later date from the Novell Support Connection. When SP1 is available, we recommend that you install ZfS 3 first, followed by ZfS 3 SP1, and finally ZfD 4.
For more detailed information about this issue, see the Workstation Inventory section of the ZfD 4 Administration guide at http://www.novell.com/documentation/lg/zdpr/index.html.
The following ZfD/ZfS interoperability issues have been identified:
- If you want to install ZfS 3 over ZfD 4 on a Windows NT/2000 server, the Workstation Inventory component might not work properly in two scenarios:
- You have previously changed the SCANDIR path after you installed ZfD 4
- You have upgraded from ZfD 3.x to ZfD 4
To correct this problem, you need to replace one of the ZfS 3 .JAR files before you install ZfS 3. For more information and to download the new .JAR file, see TID 2963354 at the Novell Support Connection at http://support.novell.com/search/kb_index.jsp.
- You must install ZfS 3 to the same location where you have installed ZfD 4 and vice versa.
- If ZfD 4 is installed first, followed by ZfS 3, ZfS Policy and Distribution Services will not work properly. ZfS 3 SP1 will correct this problem. Without SP1, to correct this problem you need to add new lines to NetWare or Windows server files. The following sections explain how to do this.
3.3.1 NetWare 5.1 or NetWare 6 Servers
On NetWare servers, lines must be added to files in the following locations:
- SYS:\SYSTEM\INVAGENTSET.NCF and SYS:\SYSTEM\INVAGENTSTOP.NCF
Add the following line to the end of the INVAGENTSET.NCF file and at the end of the ENVSET section in the INVAGENTSTOP.NCF file:
envset CLASSPATH=$CLASSPATH;ZWS_installation_directory\ZenWebServerRes.jar;ZWS_installation_directory\xmlrpcextRes.jar
- PDS_installation_directory\SMANAGER\ZFS.NCF
Add the following two lines at the end of the ENVSET section:
envset smclasses=$smclasses;ZWSinstall_directory\ZenWebServerRes.jar
envset smclasses=$smclasses;ZWSinstall_directory\xmlrpcextRes.jar
- PDS_installation_directory\PDS\TED.NCF
Add the following two lines at the end of the ENVSET section:
envset tedpath=$tedpath;ZWSinstall_directory\ZenWebServerRes.jar
envset tedpath=$tedpath;ZWSinstall_directory\xmlrpcextRes.jarNote that PDS_installation_directory is the value of the PDSPATH subkey under the SYS:SYSTEM\ZENWORKS.PROPERTIES file, and that ZWS_installation_directory is the value of the ZWSPATH subkey in the SYS:\SYSTEM\ZENWORKS.PROPERTIES file.
3.3.2 Windows NT or Windows 2000 Servers
On Windows servers, lines must be added to files in the following locations:
- PDS_installation_directory\BIN\ZFSSRV.CFG and PDS_installation_directory\BIN\TEDSRV.CFG
Add the following line to the end of the file:
CLASSPATH=;ZWSinstall_directory\xmlrpcextRes.jar;ZWSinstall_directory\ZenWebServerRes.jar;
- InventoryAgent_installation_directory\INVAGENTSTART.BAT and InventoryAgent_installation_directory\INVAGENTSTOP.BAT
Add the following line after the last SET CLASSPATH command in INVAGENTSET.BAT and INVAGENTSTOP.BAT:
set CLASSPATH=%CLASSPATH%;ZWSinstall_directory\ZenWebServerRes.jar;ZWSinstall_directory\xmlrpcextRes.jarNote that PDS_installation_directory is the value of the PDSPATH su
bkey under HKEY_LOCAL_MACHINE\SOFTWARE\NOVELL\ZENWORKS, ZWS_installation_directory is the value of the ZWSPATH subkey under HKEY_LOCAL_MACHINE\SOFTWARE\NOVELL\ZENWORKS, and InventoryAgent_installation_directory is the value of the INVAGENTPATH subkey under the HKEY_LOCAL_MACHINE\SOFTWARE\NOVELL\ZENWORKS.
If you are a current ZfS 2 customer, you can install ZfS 3 in an environment where ZfS 2 is already in use.
For Policy and Distribution Services, select the ZENworks for Servers 2 Upgrade option in the Installation Wizard.
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.
5.1 Timeouts of SNMP Requests on NetWare 6 Multiprocessor Servers
On NetWare 6 multi-processor servers, you may encounter timeouts of SNMP requests in loopback mode, when the server sends an SNMP request to the SNMP Agent running on the same server.
To correct the problem:
- Download TCP604M.EXE from Novell Technical Services (http://support.novell.com/).
- Copy the updated TCPIP.NLM file to the server's SYS:\SYSTEM directory.
- Restart the server.
5.2 Arrival Rate of SNMP Traps
If SNMP traps arrive faster than four traps per second, continuously for more than four hours, you may experience the following problems:
- Some traps may be dropped.
- Ticker tape updating may stop.
5.3 False Duplicate IP Alarms
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.
5.4 Wallpaper Printing from the Atlas View
When you print an Atlas view for which wallpaper has been imported for the map, the wallpaper does not print.
5.5 Database Object Editor Limitation
You cannot move a machine from one switch port to another.
5.6 Database Backup Limitation
While creating a backup directory, do not use extended or double-byte characters in the backup directory name. This is a limitation with Sybase.
5.7 Management and Monitoring Services on NetWare Multiprocessor Servers (New) (Fixed in SP1)
If Management and Monitoring Services (MMS) runs on a NetWare multiprocessor server where NetWare 6 Support Pack 1 or NetWare 5.1 Support Pack 4 have been installed, the server may encounter problems when the MMS servers are started or restarted.
To resolve the problem, download RBS.JAR from the Knowledgebase at Novell Technical Services (http://support.novell.com/), then install the new RBS.JAR file on any servers where the problems are occurring:
- Stop all MMS services on the NetWare server by entering stopservice at the server console prompt.
- Copy the new RBS.JAR file into the following directory:
volume:install_dir\ZENWORKS\MMS\MWSERVER\MWLIB
- Start all the MMS services on the server by entering mwserver, followed by sloader at the server console prompt.
6.1 Installation Issues
6.1.1 Beta 3 Uninstallation Required
If you are a Beta 3 user, do not install the final release of Policy and Distribution Services into the same tree where you tested Beta 3. First, uninstall the Beta 3 software by following the same procedure you used to move from Beta 2 to Beta 3, then install the final release.
6.1.2 Installation Wizard Requires More Than 16 Colors
Set the Colors display setting to something higher than 16 Colors before running the Installation Wizard.
6.1.3 Installation Wizard Browses Slowly
When you are browsing for an installation location on a NetWare 6 server, you may 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.
6.1.4 Installation Path Length Restriction
Do not install Policy and Distribution Services to a subdirectory with a path that exceeds 250 characters.
6.1.5 Special Characters in Installation Paths (New)
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.
6.1.6 Subscriber Object Rights Not Set
When installing Policy and Distribution Services in a very large Novell eDirectory tree, the rights for some Subscriber objects are not set and you 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 the Server object in ConsoleOne.
6.1.7 Installation across a Firewall
The Installation Wizard does not permit you to install from a private network onto a public network across a firewall. Run the Installation Wizard on a workstation on the public network to perform the installation.
6.1.8 Installation with Server Inventory
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.
6.1.9 Installation with ZENworks for Desktops 4 (Fixed in SP1)
If you want to install ZENworks for Servers (ZfS) 3 on the same server with ZENworks for Desktops (ZfD) 4, you must install and start the Policy and Distribution Services component of ZfS on the server first, then install ZfD. This installation order requirement will be addressed in a future Support Pack.
6.1.10 Installation in a Cluster
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.
6.1.11 Multi-Component Installation Issues
Installing to Different Servers
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 Wizard for each component, rather than selecting multiple components.
Canceling the Installation
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.
6.1.12 UNIX Installation Issues
ConsoleOne Snap-In Does Not Run on UNIX
The Policy and Distribution Services snap-in to ConsoleOne cannot be installed on Linux and Solaris. Install ConsoleOne 1.3.3 to a Windows workstation or server and use the Installation Wizard (WINSETUP.EXE) to install the Policy and Distribution Services snap-in to that location.
Red Hat Linux 7.1 without X Windows
If you are installing Policy and Distribution Services on a Red Hat Linux 7.1 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 following Sun Web site for an explanation of the problem and the solution you need to implement before installing Policy and Distribution Services:
http://java.sun.com/j2se/1.3/jre/install-linux.html
UNIX Installation Script vs. the Installation Wizard
If you use the Installation Wizard before using the UNIX installation script, you are accustomed to configuring Distributors before Subscribers. However, the UNIX installation script handles Subscribers first. Keep this in mind as you edit the TED configuration file so that your Distributor and Subscriber objects are created with the intended names.
6.1.13 Upgrade Issues from ZfS 2 to ZfS 3
ConsoleOne Snap-In Compatibility (New)
When you install the ZfS 3 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
Distributor/Subscriber Compatibility
If you upgrade a server that was only a Distributor or only a Subscriber from ZfS 2 to ZfS 3 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.
ZfS Database Compatibility
The ZfS Database (ZFSLOG.DB) cannot be upgraded from ZfS 2 to ZfS 3. Rename or delete the old database, so that a new one can be created, or install the ZfS 3 database on a different server.
Server Software Package Compatibility
If you have created server software packages using the ZfS 2 snap-in to ConsoleOne, you cannot edit those packages using the ZfS 3 snap-in to ConsoleOne, although the compiled server software packages (*.CPK files) will continue to work normally.
A conversion utility that will convert *.SPK files from ZfS 2 format into ZfS 3 format is available in TID 10069358 in the Knowledgebase at Novell Technical Services (http://support.novell.com/). Conversion is not necessary unless you need to edit a server software package. (For this paragraph only, fixed in SP1)
ZfS 2 Object Selection
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.
6.1.14 GroupWise Incompatibility Issue
If you install the GroupWise 6 snap-in to ConsoleOne after you have installed the Policy and Distribution Services snap-in to ConsoleOne, you may encounter some ConsoleOne functionality problems, including:
- The Refresh Distributor item on the ConsoleOne Tools menu returns the error "Unable to initialize security."
- You are unable to send Distributions to Subscribers because the security file is not created correctly.
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.
6.2 Tiered Electronic Distribution Issues
6.2.1 Special Characters in TED Object Names and Containers
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 use single quotes in the names of Subscriber, Channel, or Policy Package objects if you are logging data to the Policy/Distribution database. If you do, you will receive error -131. (For this paragraph only, fixed in SP1)
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.
6.2.2 Special Characters in Directories and Files Contained in Distributions
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.
Certain characters do not map correctly between the Windows Latin code page (1252) and the Netware Latin code page (850); for example, the Euro character and the Yen symbol (used to denote Japanese currency). Do not use these characters in the names of directories and files that will be gathered into Distributions. (For this paragraph only, fixed in SP1)
6.2.3 Distributor Primary Address
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 encryption. You can obtain this information from the DISTEVENT.TED log in the \ZENWORKS\PDS\TED directory. This information is not currently available in the TED.LOG or DEFAULTLOG.TXT files.
6.2.4 Certificates Not Copied to Windows NT/2000 Subscriber Servers
When you configure a Subscriber in ConsoleOne to receive the Distributions from a particular Channel, the Distributors of those Distributions must send certificates to the Subscriber. For this process to succeed, the ConsoleOne user must have sufficient rights to the Subscriber server file system.
For a NetWare Subscriber, the ConsoleOne user automatically has sufficient rights by virtue of being able to configure the Subscriber object.
For a Windows Subscriber, administrator rights for the ConsoleOne user must be set up in Windows:
- On a Windows NT Subscriber server, use User Manager for Domains.
- On a Windows 2000 Subscriber server, use Active Directory Users and computers or Local Users and Groups.
6.2.5 Undefined Subscriber Variable Not Reported in Event Log
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.
6.2.6 Encrypted Distributions
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.
6.2.7 Encrypted Distributions on Windows 2000 (Fixed in SP1)
A Windows 2000 server that functions as both a Distributor and a Subscriber cannot send an encrypted Distribution to itself.
6.2.8 Maximum Distribution Size on NetWare (Fixed in SP1)
For a NetWare Distributor, the maximum Distribution size is 4.2 GB compressed. This issue is being addressed and will be resolved in a future Novell Support Pack.
6.2.9 Distribution Size Reporting (Fixed in SP1)
If a Distribution is larger than 2.1 GB, its size is not correctly reported in the Policy/Distribution Database. You can obtain accurate size information from the following sources:
- The Active Distributions page in the Remote Web Console while the Distribution is being processed
- The Distributor or Subscriber log file to see how many bytes were sent or received
- The DISTFILE.TED file in the Distribution subdirectory to see how many bytes were processed
6.2.10 Maintain Trustees Option on the File Type of Distribution (Fixed in SP1)
If a target directory path or variable in the Files To Be Distributed list ends with a backslash (\), the Maintain Trustees option fails. The files are delivered successfully, but the trustees will not be maintained. Remove the backslash and resend the Distribution.
6.2.11 Distribution Schedule with the Run Immediately Schedule Type (Fixed in SP1)
On the Schedule property page of a Distribution object, if you select the Run Immediately schedule type and you also use the Repeat the Action Every option to configure a recurring interval, the Distribution will not be built according to the selected interval. Instead, it will be rebuilt when the Distributor Agent rereads eDirectory.
As a workaround, select a different schedule type. For example, the Interval schedule type offers the same intervals as the Run Immediately schedule type.
If you need to build the Distribution immediately, rather than after the interval has passed, use the ZfS Management role in Novell iManager to build the Distribution:
- In Novell iManager, expand the ZfS Management role > click Remote Web Console.
- Specify a server or select a TED object.
- In the Available Services field, select Tiered Electronic Distribution.
- Click the Distributions tab > click Build Distribution.
- Select the Distribution to build immediately > click OK.
6.2.12 Policy Package Distributions to External Subscribers
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 TEDNODE.PROPERTIES file in the TED subdirectory of the Policy and Distribution Services installation directory on the external Subscriber server. For instructions, see Editing the TEDNODE.PROPERTIES File in Policy and Distribution Services in the Administration guide.
6.2.13 Distribution Type List Empty in ConsoleOne (Fixed in SP1)
In ConsoleOne, in the properties of a Distribution object, the Select Type field on the Type tab should offer seven Distribution types. If the list is empty, check the properties of the ConsoleOne shortcut on the Windows desktop to make sure that the Start In field is set to the directory where ConsoleOne is installed.
6.2.14 Windows Services Functionality
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 stop the Novell ZfS Policies service, the Novell ZfS Distribution service, and the Novell Zen Web Server service individually.
6.2.15 DNS Issues
It is preferable to avoid DNS issues before they occur. For assistance with setting up DNS correctly, 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.
Network Address Problem
If you run the Distributor or Subscriber Agent on a NetWare server where DNS is not set up correctly, 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 ellipsis 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 ellipsis 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.
Certificate Problem
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 sent successfully 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.
DNS Temporarily Not Available
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.
6.2.16 Conn Timeout Errors
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.
6.2.17 Distributor Agent Does Not Start
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.
6.2.18 Certificates Not Copied to Linux Subscriber
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.
6.2.19 Sending File Distributions to the Root of a Server (New)
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 synchroniaation. 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.
6.2.20 Distributions Fail When Larger Than the Free Space on a Subscriber Server (New)
If you do not use the Disk Space Desired To Be Free option in a Subscriber's properties, the following problem can occur. This option was added in ZfS 3 to solve this problem.
On Windows, Linux, and Solaris servers, if you send a Distribution that is larger than the free space on the Subscriber server’s file system (specifically, the volume or drive where the Distribution is being sent), the following error will be displayed on the console, in the log file, and in the event logger:
Error receiving Distribution from Distribution_name, exception: Write error.
The Subscriber software shuts down the socket and stops the Distribution’s work order. However, for these platforms, the Distributor’s socket does not register the close and keeps sending the Distribution data. The Distributor then thinks the send has been successful, even though it has received an error from the Subscriber. Therefore, the Distributor’s log file displays both a successful completion for sending the Distribution and the error describing that the disk was full and the Distribution was not received in its entirety.
6.2.21 Distribution Completion Order Affects Rollback (New)
Although you can specify the order of processing Server Software Packages in a Distribution, this order is not currently enforced.
This affects rollback, because you can only roll back the last software package that was successfully processed. In other words, if you had three Server Software Packages in the Distribution, any one of them could be the one to finish processing last, not necessarily the one listed third.
6.3 Policy Package Issues
6.3.1 Latest SNMP.NLM Required
The SNMP Trap Targets and SNMP Community Strings policies do not work unless the SNMP.NLM file from NetWare 6 Support Pack 1 or NetWare 5.1 Support Pack 4 has been installed.
6.3.2 Native SNMP Stack Required
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.
6.4 Server Software Package Issues
6.4.1 Server Down by Server Software Package (Fixed in SP1)
If a server software package is installed that downs the server or stops the Policy/Package Agent, the software package is left in a "processing" state.
To correct the problem, delete the SFTPKG.MVP file from the install_dir\ZENWORKS\PDS\SMANAGER\PROP directory.
6.4.2 Daylight Saving Time Affects Time Stamp (Fixed in SP1)
The time stamps on files that are distributed as part of a server software package are affected by whether or not Daylight Saving Time is in effect when the files are distributed. For example, if a file has a time stamp during Daylight Saving Time (for example, during summer) and it is distributed when Daylight Saving Time is not in effect (for example, during winter), the time stamp of the distributed version will be off by one hour compared with the time stamp of the original version. The problem originates in the Sun JVM and should not adversely affect typical server software package Distributions.
6.4.3 Server Software Package Deletion
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.
6.4.4 Fail on Error Functionality (Fixed in SP1)
If you select Fail on Error on the Local File Copy page of a server software package component, only the file where the error occurred is not copied. The rest of the files in the component will still be processed successfully.
6.5 ZfS Management Role Issues
6.5.1 EMFRAME.WAR File Compatibility
The EMFRAME.WAR file on the ZENworks for Servers Companion CD is not compatible with the Novell product plug-ins to Novell iManager that are installed with NetWare 6. To obtain the newer EMFRAME.WAR file that is compatible, see TID 2961929 in the Knowledgebase at Novell Technical Services (http://support.novell.com).
6.5.2 Novell iManager Login Screen Timeout (Fixed in SP1)
After you start Tomcat for the first time, the Novell iManager Login page times out immediately after you try to log in. Simply log in again to access Novell iManager successfully.
6.5.3 Problems with Unicode Characters
Some Unicode characters used by certain locales may cause Novell iManager to display errors. To prevent the 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.
6.5.4 Distribution Status in the Tiered Distribution View
If a 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.
7.1 Inventory Database Compatibility between ZfS 2 and ZfS 3 (New)
The Inventory database (ZENINV.DB) cannot be upgraded from ZfS 2 to ZfS 3.
7.2 Installation of Server Inventory before Policy and Distribution Services on NetWare (New)
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.
7.3 Installation of the Inventory Server without Policy and Distribution Services on NetWare (New)
If you have installed the Inventory server on a NetWare server without installing Policy and Distribution Services, and you want to start the Inventory services without rebooting the server, do the following before starting the Inventory 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 commands:
SEARCH ADD ZWSPath_value
ZWS
STARTINV7.4 Interoperability with ZENworks for Desktops 3.x
Do not install ZfS 3 Server Inventory and ZfD 3.x Workstation Inventory on the same machine. Also, be aware of the following inventory data storage limitations:
- ZfS 3 and ZfD 3.x inventory information cannot be stored in a common Inventory database.
- ZfS 3 and ZfD 3.x Inventory servers cannot coexist in the same inventory tree hierarchy. Consequently, you cannot roll up the ZfS 3 inventory information to a ZfD 3.x Inventory server and vice-versa.
7.5 Special Characters in Directory and File Names
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.
7.6 Inventory Agent on NetWare Multiprocessor Servers (Fixed in SP1)
If the Inventory Agent has been scheduled to run on a NetWare multiprocessor server with more than two mounted volumes, the server may encounter problems. For more information, see TID 2961928 in the Knowledgebase at Novell Technical Services (http://support.novell.com/).
8.1 Screen Blanking Limitations
The following display adapters do not support the Screen Blanking feature:
- ATI Rage Pro Turbo AGP
- ATI Technologies Inc. 3D Rage Pro AGP 2X
- ATI Technologies Inc. 3D Rage Pro Turbo AGP 3X
- ATI Technologies Inc. 3D Rage Pro (ATI Graphics Accelerator)
- ATI Graphics Pro Turbo PCI (mach 64 GX)
- ATI Graphics Pro Turbo PCI (mach 64 VT)
- Matrox MGA Ultima/Impression (PCI)
- MGA Compatible Display Adapter (Qvision 2000)
- Compaq Qvision, 2000, 2000 + (MGA)
- Diamond Fire GL 1000 PRO
On a server whose display uses one of these adapters, the screen will not be blanked even if you have turned on this feature.
In addition, the Screen Blanking feature does not work on any display adapter that is not 100% VGA compatible.
8.2 Optimization Driver Limitation
If a managed server is configured with one of the following video drivers:
- S3VIRGE
- STBVIRGE
- GLINT
- NVIDIA
then the Optimization driver functionality will not be available for a Remote Management session with the managed server.
8.3 Full-Screen DOS Window Limitation
If a managed server has a full-screen DOS window open, you cannot establish a Remote Management session with it.
8.4 Manual Wallpaper Suppression Required (Fixed in SP1)
During a Remote Control or Remote View session, the active desktop wallpaper on the managed server cannot be suppressed by the Remote Management Agent.
To improve performance, suppress the wallpaper before starting the remote session.
8.5 High CPU Utilization (Fixed in SP1)
On Windows NT/2000 managed servers, CPU utilization is high if Enable Pointer Shadow is selected for the mouse cursor.
Deselect Enable Pointer Shadow before starting the Remote Control or Remote View session:
- From the Windows desktop, click Start > Settings > Control Panel > double-click Mouse.
- Click Pointers > deselect Enable Pointer Shadow.
8.6 RconsoleJ Help Window Problem (Fixed in SP1)
In the Remote Servers dialog box in RconsoleJ, the Help window does not close properly. Close the Remote Servers dialog box first, then close the Help window.
9.1 Disclaimer, Patents, Export Notice, and Copyright
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 o notify any person or entity of such changes.
U.S. Patent Nos. 5,910,803 and 6,067,093. US and Foreign Patents Pending.
Copyright (C) 2002 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.
This product may require export authorization from the US Department of Commerce prior to exporting from the US or Canada.
9.2 Trademarks
Novell, NetWare, NDS, ConsoleOne, 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 trademarks are the property of their respective owners.