Novell® ZENworks® 6.5 Server Management includes the following components:
Policy and Distribution Services
Server Inventory
Remote Management
Management and Monitoring Services
The issues included in this document were identified when the product was initially released. For information about issues corrected after the initial release, see Technical Information Document 10093356.
The ZENworks 6.5 Server Management Installation Guide provides detailed installation instructions. Its .pdf file is located in the \documents\en\sminstall directory on the ZENworks 6.5 Server Management Program CD, and is available as a menu option when running the installation program. An updated version of this guide is available on the Novell documentation Web site.
The ZENworks 6.5 Server Management Administration Guide is available on the Novell documentation Web site.
Please review this Readme as well as the applicable guides before installing Server Management.
(NEW) Known Issues that are new in ZENworks 6.5 are noted with this parenthetical.
(Fixed in SP1) Known Issues that are fixed in ZENworks 6.5 SP1 are noted with this parenthetical.
(NEW) As of February 2005, Server Software Package (.cpk) files have been added to the ZENworks 6.5 Companion 2 CD for upgrading the Server Inventory, Remote Management, and Management and Monitoring Services components. For more information, see 1.3 Upgrade Procedures.
For detailed instructions, see the ZENworks 6.5 Server Management Installation Guide.
Be sure to fulfill the prerequisites before upgrading to or installing ZENworks 6.5 Server Management:
Minimum Requirements: Your target servers and installation workstation must meet the minimum requirements as stated in the ZENworks 6.5 Server Management Installation Guide.
Schema Extensions: You must extend the schema on the Novell eDirectoryTM tree where you want ZENworks objects to be installed. When running the GUI installation program, select the following menu options: Server Management > Schema Extension and Product Licensing.
Novell iManager (optional): For Policy and Distribution Services, you can use Novell iManager in addition to Novell ConsoleOne® for managing the software. You must have iManager 2.0.2 installed on at least one NetWare®, Windows*, Linux*, or Solaris* server, because the version 6.5 Policy and Distribution Services plug-ins are not compatible with any previous version of iManager.
To install iManager 2.0.2 on NetWare or Windows servers, insert the ZENworks 6.5 Companion 1 CD and select the following menu options: Companion Programs and Files > Novell iManager.
To install iManager 2.0.2 on Linux or Solaris servers, see Installing iManager > Installing a New Version of iManager on the iManager documentation Web site.
Server Management > Policy-Enabled Server Management (which includes Policy and Distribution Services, Server Inventory, and Remote Management)
or
Server Management > Management and Monitoring Services
For Policy and Distribution Services, run:
Program_CD\ZfS\TedPol\Linux\zfs-pds-install
Program_CD\ZfS\TedPol\Solaris\zfs-pds-install
For Management and Monitoring Services, run:
Program_CD\ZfS\SvrMgmt\mms\Linux\MMS_Linux_Install.pl
Server Inventory and Remote Management are not supported on Linux and Solaris. See the ZENworks 6.5 Server Management Installation Guide for details.
Server Management > Web-Based Management Components
You can directly upgrade to ZENworks 6.5 Server Management in the following ways:
GUI Installation Program: You can upgrade all ZENworks for Servers 3.x components using the installation program on the ZENworks 6.5 Server Management Program CD.
Server Software Package: You can upgrade the following ZENworks components using the .cpk files contained on the ZENworks 6.5 Companion 2 CD:
For information on upgrading Server Inventory or Remote Management in an earlier version of ZENworks for Servers 3.x to version 3.0.2 or 3 SP2, see the applicable Readme on the ZENworks for Servers documentation Web site.
For more detailed upgrade information, see the ZENworks 6.5 Server Management Installation Guide.
The following sections list the software issues that are known for Policy and Distribution Services.
The following are known installation issues for Policy and Distribution Services.
The error "Object not found (32)" is returned on a Windows 2000 server using IIS 5.0 (port 80) when attempting to use iManager's package manager to install the Server Management NPM files (located in the \NPM directory on the ZENworks 6.5 Server Management Program CD).
Workaround: To install the ZENworks NPM files, insert the ZENworks 6.5 Server Management Program CD on your workstation and select the following menu options: Server Management > Web-Based Management Components. This installs the zfs_polydistplugins.npm and zfsca.npm files.
The following are known upgrade issues for Policy and Distribution Services.
When you have both ZENworks 4.x Desktop Management Workstation Inventory and ZENworks 3.x Server Management Policy and Distribution Services installed and running on the same server, upgrading one but not the other to ZENworks 6.5 can cause the other's service to not start.
The problem lies with the ZENworks Web Server, which cannot properly start unless the upgraded service is started before the non-upgraded service.
Workaround: If you only upgrade Workstation Inventory, make sure that its service is started before you start the older Policy and Distribution Services service.
or
If you only upgrade Policy and Distribution Services, make sure that its service is started before you start the older Workstation Inventory service.
When NetWare 6.5 servers are upgraded to SP3 (NetWare OES), a newer JVM* is installed that is incompatible with the zencommon.jar file in ZENworks 6.5, so the Server Policies and Server Software Package functionalities no longer work.
Workaround: Upgrade Server Management to ZENworks 6.5 SP1 to obtain the zencommon.jar file that works with the JVM that ships with NetWare 6.5 SP3/NetWare OES.
If services have not started up correctly after upgrading them, simply restart the services.
For more information, see "Starting and Stopping Server Management Services" in "Appendixes" in the ZENworks 6.5 Server Management Installation Guide.
The following are known Tiered Electronic Distribution issues.
If a Server Software Package attempts to copy a file to the root of a DOS partition on NetWare 6.5 SP1/SP2 server, such as C:\, file copying fails.
Workaround: On NetWare 6.5 SP1/SP2 servers, only use a Server Software Package to copy files to subdirectories on a DOS partition, such as c:\nwserver.
This problem will be fixed in NetWare 6.5 SP3.
When there are two or more Distributors sending Distributions to the same Subscriber, or a parent Subscriber in the routing hierarchy is also a Distributor, the end node Subscriber could reject a Distribution because the certificate was signed by a non-trusted Distributor, rather than the trusted Distributor that sent the Distribution.
Workaround: Resolve certificates for the non-trusted Distributor so that the Subscriber recognizes it as a trusted Distributor, and then accepts Distributions from it.
(Windows only) The Tiered Distribution View in iManager shows the Subscriber's status as received and shows no red exclamation mark for an error, even though the Subscriber received an error during extraction of the MSI Distribution.
Although the Subscriber had fully extracted the Distribution, it encountered an error in processing one of the Distribution's MSIs, which should have flagged the status as red in the Tiered Distribution View.
Workaround: In the Tiered Distribution View in iManager, move the cursor over the server icon and the balloon that is displayed shows the error.
If extended characters (such as ê, ë, ì, or í) exist in the path to the .fil files for an AOT Application object, the Distributor cannot access the .fil files for the Distribution. The following error is given:
Error in building the distribution for this AOT application, the source path is invalid. It must exist on the Distributors server's file system, and begin with either \\server.zenworks.provo.novell.com or \\servername.
Workaround: Use a File Distribution to distribute the .fil files. This Distribution type handles extended characters.
Desktop Application Distributions are not supported on Linux and Solaris. The Working Context fields is used for Desktop Application Distributions.
In the Subscriber properties for a Linux or Solaris server, the Working Context field on the General tab is not disabled. It should be greyed out and inaccessible.
Workaround: Ignore this field for Linux and Solaris Subscriber servers.
The following are known Server Policy issues.
When you distribute and enforce a new policy, all existing policies get enforced.
The re-enforcement of existing policies can cause errors to be logged, stating that a file is already there, or cause unexpected log file changes if a script file change was selected.
The following are known Server Software Package issues.
When creating a Server Software Package with a Text File component, if you configure the component to search for a word, but the word in the text file being searched is adjacent to a punctuation mark, the word will not be discovered by the search, because the punctuation mark is considered by the search engine to be part of the word.
For example, you configure the Text File component to search for "word" in the following text file excerpt:
... in the word.
Because "word" ends the sentence and has a period next to it, "word" is not found by the search engine, because only "word." exists in the text file.
The configured action for the Text File component will not be performed when punctuation is involved, because the word being searched for cannot be found.
Workaround: Be aware of the possibility that punctuation can affect the ability of a search to locate words in a text file. You should account for that fact in your search patterns. When possible, review the text files to be searched to verify that your search pattern can be located.
The following are known Novell iManager issues.
The following are known security certificate issues.
When you perform the following procedures, you might receive an error message stating that the primary address and the DNS are mismatched:
Workaround: The only way to solve the mismatch is to re-mint the security certificate on that server. To do this:
The ted.cfg file will be re-created with the correct information when ZENworks is started again.
If you have installed Sybase* on a NetWare server, the following error message might be displayed during the database operations:
Connection terminated abnormally.
Ignore this message.
The following are known ZENworks reporting issues.
The Tools > ZENworks Reports option does not provide Policy and Distribution Services reports.
Workaround: Access Policy and Distribution Services reports by right-clicking the Server Management Database object.
The following sections list the software issues that are known for Server Inventory.
If you change the target Inventory server of an inventoried server, the software dictionary files at the new Inventory server are not downloaded if the files are older than the ones that are available on the inventoried server.
Workaround: Update the modified time of the software dictionary files that are available on the Inventory server so that the dictionary files at the Inventory server are newer than those at the inventoried server. The inventoried servers download the dictionary during the next scan.
The inventoried servers might fail to transfer the scan files to a Windows 2003 Inventory server if the volume containing the \scandir directory is changed from FAT partition to NTFS partition after the ZENworks 6.5 Server Management installation.
Workaround: To resolve this problem:
In ConsoleOne, right-click the Inventory Service object (Inventory Service_server_name).
Click Properties, click the Inventory Service Object tab, then click the Inventory service object properties sub-option.
Place the cursor in the Scan Directory Path field, then press Enter.
Click Apply, then click Close.
During the ZENworks 6.5 Server Management installation, if you choose to install Policy and Distribution services, and the Inventory Standalone Pre-Configuration on NetWare servers, the ZENworks service starts after installation, but Policy and Distribution Services does not work.
Do not choose to install the following Server Inventory components to a NetWare 5.1 server:
The GUI installation allows you to select NetWare 5.1 servers for installing these Server Inventory components, but this is not supported.
If you install Server Inventory on a NetWare 5.1 server, the server may abend while unloading Java.
Workaround: If you have already installed these components to a NetWare 5.1 server, you must perform the following tasks to prevent the Inventory services from being loaded on the server:
If you have installed Sybase on a NetWare server, the following error message might be displayed during the database operations:
Connection terminated abnormally.
Ignore this message.
The following sections list the software issues that are known for Remote Management.
If a user uses the Remote Desktop Connection to connect to a Windows 2003 server, and then initiates a Remote Control session on that server, the Remote Control console is black and you cannot remotely control it.
Workaround: Users with a Windows 2003 server should log in locally before you attempt to remotely control their servers.
For wallpaper suppression, a Windows 2003 server behaves differently from other Windows operating systems. When you set the wallpaper, a Windows 2003 server creates a backup of it. When you disable the wallpaper, it is disabled only from the primary location. When you change the settings, the wallpaper might reappear.
During the Remote Management session with a Windows 2003 managed server, if you place the mouse cursor on a window that is continuously changing (for example, the Task Manager), the mouse cursor flickers at the managed server. This behavior of the mouse is noticed only at the managed server.
On Windows 2000/2003 servers, DirectX applications do not run in exclusive mode during a Remote Control or Remote View Session.
During a Remote Control session, you might not be able to remove the active desktop wallpaper on the managed server. This affects Remote Management performance.
Workaround: Manually suppress the wallpaper of the managed server.
The following sections list the software issues that are known for Management and Monitoring Services.
You can change this by increasing the number of buckets for the monitored parameters in the configuration file and running the advtrend read_cfg command.
When you install the Server Management for Windows, several performance monitor counter failure messages are repeatedly logged into the Windows Event log file (event IDs such as 1008, 1009, 2001, 2002). For example:
The Open Procedure for service "Remote Access" in DLL "c:\winnt\system32\rasctrs.dll" failed. The performance data for this service is not available. Status code returned is data DWORD 0.
Sometimes the SNMP service crashes when these events are posted in the Events Viewer. For example, on a Windows 2000 machine with the AppleTalk* protocol installed and the performance enabled, the following events are posted in the Events Viewer and the SNMP service crashes:
The Trending Agent (NTREND) of the Server Management Agent uses performance counters to obtain performance data. The performance monitor checks the availability of all the counters listed in the registry. Either a service is installed, but the performance counters are disabled, or vice versa. These events are logged into the Windows Event Log.
When the performance counters are queried, the extension performance counter's DLLs are loaded in the SNMP address space. If there is a problem in the extension performance counter's DLLs, the SNMP service crashes.
Workaround: To keep the SNMP service from crashing, disable the performance counters for the problem DLL by performing the following steps:
Install the latest support version for the specific Windows platform.
Note the performance counter events that are logged in the Windows Event Log.
For Windows 2000 onwards, download and install the exctrlst_setup.exe file from the Microsoft web site. For Windows NT, download and install the resource kit that contains the exctrlst_setup.exe file from the Microsoft web site.
Run exctrlst_setup.exe from the installed location.
If the event is:
The Open Procedure for service "Remote Access" in DLL "c:\winnt\system32\rasctrs.dll" failed. The performance data for this service is not available. Status code returned is data DWORD 0.
This means that the performance counters are enabled, and the RAS is installed but might be disabled. Use exctrlst_setup.exe to enable the RAS service to function correctly and disable the performance counters:
Shut down and restart the machine.
For AppleTalk, disabling the performance counters for the service solves the problem.
If you have installed Sybase on a NetWare server, the following error message might be displayed during the database operations:
Connection terminated abnormally.
Ignore this message.
If the snmplog.nlm is not loaded on the site server, you do not receive new alarms. The snmplog.nlm file does not load if the build dates of the loaded snmp.nlm and the snmplog.nlm are different. Ensure that the build dates of the snmp.nlm and the snmplog.nlm files are the same date on the site server. Restart the site server. Installing the Server Management Agent for NetWare installs the correct version of the snmp.nlm and the snmplog.nlm files.
If the Site Server is upgraded from ZENworks for Servers 3.x to ZENworks 6.5, the nxp.ini file might not be copied because of a time stamp mismatch.
Workaround: You can copy nxp.ini from the zfs\svrmgmt\mms\server\mwserver\nmdisk directory on the ZENworks 6.5 Server Management Program CD to the zenworks_installed_folder\mms\mwserver\nmdisk directory.
When you upgrade Management and Monitoring Services' agents from ZENworks for Servers 3.x to ZENworks 6.5 Server Management, the Advance Trending Agent will not be installed if ZENworks for Servers 3.x Management and Monitoring Services' agents have been installed directly under a drive. For example, C:.
Workaround: Install the Advanced Trending Agent using the ZENworks 6.5 Server Management installation program.
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 © 2004 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. Patents 5,608,903; 5,633,931; 5,671,414; 5,677,851; 5,692,129; 5,758,069; 5,758,344; 5,761,499; 5,784,560; 5,818,936; 5,828,882; 5,832,275; 5,832,483; 5,832,487; 5,859,978; 5,870,561; 5,870,739; 5,873,079; 5,878,415; 5,884,304; 5,893,118; 5,910,803; 5,913,025; 5,919,257; 5,933,503; 5,933,602; 5,933,826; 5,946,467; 5,956,718; 5,963,938; 5,964,872; 5,983,234; 5,987,471; 6,002,398; 6,016,499; 6,023,586; 6,029,247; 6,047,312; 6,052,724; 6,061,726; 6,061,740; 6,061,743; 6,065,017; 6,067,093; 6,094,672; 6,098,090; 6,105,062; 6,105,069; 6,105,132; 6,108,649; 6,115,549; 6,119,122; 6,144,959; 6,167,393; 6,173,289; 6,286,010; 6,308,181; 6,345,266; 6,424,976; 6,516,325; 6,519,610; 6,532,451; 6,578,035; 6,615,350; 6,671,688; 6,684,293; 6,697,813; RE 37,178. Patents Pending.
ConsoleOne, LANalyzer, NetWare, Novell, and ZENworks are registered trademarks of Novell, Inc. in the United States and other countries.
eDirectory, IPX, and NLM are trademarks of Novell, Inc.
All third-party trademarks are the property of their respective owners.