Novell® ZENworks® 6.5 Server Management includes the following components:
Policy and Distribution Services
Server Inventory
Remote Management
Management and Monitoring Services
This Readme file provides the latest information on known issues and other product information that is not contained in the Server Management documentation.
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. However, a more updated version exists in the Web version.
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.
Be sure to fulfill the prerequisites before installing ZENworks 6.5 Server Management.
Previous ZENworks Versions: Upgrading from ZENworks for Servers 3.x to ZENworks 6.5 Server Management is supported for Public Beta 1. However, for customers who have been using ZENworks 6.5 Beta 1 or Beta 2, you cannot use an upgrade method to move from these betas to the Public Beta 1. You must perform a new installation of 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 graphical installation program, select the Policy-Enabled Server Management > Schema Extension and Product Licensing menu options.
Novell iManager (optional): For Policy and Distribution Services, you can use Novell iManager in addition to Novell ConsoleOne® for managing the software. However, 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 on NetWare or Windows servers for Public Beta 1, insert the ZENworks 6.5 Companion 1 CD and select Companion Programs and Files > Novell iManager from the menu options.
Policy-Enabled Server Management (includes Policy and Distribution Services, Server Inventory, and Remote Management)
or
The following sections list the ZENworks 6.5 Server Management software issues that are known for Policy and Distribution Services.
See the ZENworks 6.5 Server Management Installation Guide for a more updated version than the guide that is contained on the Public Beta 1 CDs. For example, information concerning eDirectory versions and installing multiple databases is incorrect in the version of the guide on the CD.
The following upgrade issues are known for Policy and Distribution Services.
You cannot use the upgrade program to move from ZENworks 6.5 Beta 1 or Beta 2 to the Public Beta 1. You should perform a new installation of ZENworks 6.5 Server Management.
However, upgrading from ZENworks for Servers 3, 3 SP1, 3 SP2 or 3.0.2 to ZENworks 6.5 Server Management is supported in the Public Beta 1. See the Upgrade section in the ZENworks 6.5 Server Management Installation Guide for details.
Directly upgrading from ZENworks for Servers 2 is not supported in version 6.5.
After upgrading NetWare and Windows servers, you might see "Signature Error" on the Subscriber when sending Distributions through parent Subscribers. This error is intermittent and is caused by the graphical interface upgrade program setting the Distributor's Network Address attribute to the IP Address, rather than the DNS name.
Workaround: To avoid this error, immediately after you upgrade the Distributor objects using the graphical interface upgrade program, you must change the Distributor's network address from its IP address to its DNS name:
In ConsoleOne, right-click the Distributor object, then click Properties.
On the Other tab, click the plus sign for Network Address, click the attribute, then click Modify.
Click the ... button to the right of the attribute.
In the Extended Editor Dialog box, click the down arrow for the NetAddress Type field and change type_13 to AppleTalk.
Click the down arrow again and change it back to type_13.
This is necessary to get ConsoleOne to save the change you make next.
For the NetAddress field, click the ... button.
In the ASCII column, change the IP address to the server's DNS name, then click OK three times to exit the dialog boxes and the object's properties.
Repeat this process for each Distributor object that was upgraded.
We recommend doing this for all of the Distributor objects that were upgraded to ZENworks 6.5 Server Management.
After upgrading NetWare and Windows servers, you might see a -669 authentication error when extracting Desktop Application Distributions. When this error occurs, it is because the password was not correctly set for the Subscriber object during the upgrade process. The error is intermittent.
Workaround: To fix the -669 authentication error, you must reset the password in the Subscriber object:
In ConsoleOne, right-click the Subscriber object, then click Properties.
On the Other tab, click the plus sign for zentedXMLInfo, click the attribute, then click Modify.
Click the ... button to the right of the attribute.
In the Extended Editor Dialog box, if the following text exists, remove it:
<SetPassword>true<SetPassword>
Click Ok to exit the dialog box.
Click Apply to register the change.
You must click Apply before continuing.
Click the General > Working Context tab, then set or reset the context:
Click OK to close the object's properties to save the changes.
Repeat this process for each Subscriber object.
For Subscriber objects that have been upgraded to ZENworks 6.5, we recommend doing this for all Windows Subscriber objects, and for all NetWare Subscriber objects that do not have NCP Server objects in the same Tree.
Re-send the Desktop Application Distributions to the Subscribers.
The following are known Tiered Electronic Distribution issues.
For a "Signature Error" error, see 3.2.2 "Signature Error" might be displayed for Distributions that are sent through a parent Subscriber for steps to solve it.
For a -669 authentication error, see 3.2.3 A -669 authentication error might occur for Desktop Application Distributions received by Subscribers for steps to solve it.
When a single application belongs to two or more folders, a Desktop Application Distribution might create application folders where only one folder has application associations, and the others do not. This can happen the first time the Distribution is received and extracted.
Workaround: Send and extract a revision (delta) of the Distribution to add the associations to the other folders.
When a Distributor is very busy, it may drop the Extraction Replies that it receives from the Subscribers.
In iManager, if you Remote Web Console into the Subscriber, the Distribution information will be correct. However, the Tiered Distribution View will be incorrect, in that it will show the Distribution as having been received, but not extracted. Also, there have been cases where the Tiered Distribution View shows the Distribution as not having been received.
The cause is currently unknown.
Workaround: To make everything work, you must resolve the certificate of the untrusted Distributor (to the end node Subscriber) or update the Subscriber object, refresh the trusted Distributor, then send the Distribution again.
When creating an FTP Distribution in iManager, the Target entry does not retain the backslash character after you refresh the view. Because the backslash is being treated as an escape character, the first character after the backslash is also not retained if that character is recognized as a valid escape command, and instead replaces that character with a space.
For example, where the first character after the backslash is recognized as a escape character:
work:\temp
after refreshing the view, it is displayed as:
work: emp
Where none of the directory entries contain a recognized escape character:
work:\zfsdist\mcafee\client
after refreshing the view, it is displayed as:
work:zfsdistmcafeeclient
Workaround: Use ConsoleOne rather than iManager to create FTP Distributions.
If a Server Software Package attempts to copy a file to the root of a DOS partition on NetWare 6.5 SP1 server, such as C:\, file copying fails.
Workaround: On NetWare 6.5 SP1 servers, using a Server Software Package, only copy files to subdirectories on a DOS partition, such as c:\nwserver.
This problem will be fixed in NetWare 6.5 SP2.
Error "Object note found (32)" is returned when attempting to use iManager's package manager to install Server Management NPM files (located in the \NPM directory on the ZENworks 6.5 Server Management Program CD).
Workaround: Use the Web Management Components installation option to install NPMs on Windows servers. To do so, on the main installation menu, select Server Management, the select Web-Based Management Components. This installs the two NPM files: zfs_polydistplugins.npm and zfsca.npm.
The following are known Novell iManager issues.
The cause is currently unknown.
Workaround: Log in again and continue using iManager.
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 are known ConsoleOne Help issues.
When you view online help from a page in ConsoleOne, you can click the ZENworks Online Documentation link to access the ZENworks Server Management documentation. This opens another help topic that should display the link to the current online documentation. However, this link might not be displayed in the help topic.
Workaround: Exit ConsoleOne, then copy the jh.jar and njha.jar files from the \novell consoleone\helpjarupdate directory of the Novell ZENworks 6.5 Companion 1 CD to the ConsoleOne_installation_path\consoleoneext directory on your workstation, replacing the older versions of these files. Then restart ConsoleOne.
The following sections list the ZENworks 6.5 Server Management software issues that are known for Server Inventory.
The ZENworks Public Beta 1 release contains a first look at new ZENworks inventory features that will continue to be enhanced during the beta cycle. These enhancements to inventory performance and features will be included in the final ZENworks 6.5 product.
Server Inventory can be upgraded with the following conditions:
To resolve this problem:
If you create a custom view with attributes having multiple instances, the resultant view will have a Cartesian product. This might affect the Custom View performance. For example, if you create a view with computer name, hard disk size, logical disk size attributes, and if the inventoried server has two hard disks and three logical disks, the resultant view will have six entries.
Hence, do not create a custom view with attributes having software information and attributes having multiple instances. Also, do not create a custom view with software (or any of its related classes such as Patch and File), and Exclude File information.
If you have installed ZENworks 6.5 Management and Monitoring Services along with Server Inventory in your setup, you might not be able to invoke the Server Inventory snap-ins from the Atlas namespace.
Workaround: You must access the Inventory snap-ins from the NDS namespace.
Do not use the "Equal To" operator for Date fields while creating a query in any of the following utilities: Query, Data Export, and Custom Views.
If the Inventory scanner is unable to find the language information of a software or a file on the inventoried servers, then Summary displays "[1000]" for the Language attribute.
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.
Stop the ZENworks service by entering exit in the service window of the NetWare server.
Restart the ZENworks service by entering zfs.ncf at the server console prompt.
In the tables of the Software Dictionary Editor, you must press either the Enter or the Tab key after entering the information in the table cells to save the information into the table.
Connection terminated abnormally.
Ignore this message.
The Inventory scanner does not support the dictionary-based file scan on NetWare Inventoried servers for Public Beta 1.
If you have configured the Software Dictionary editor to exclude the disk usage from the Inventory scan and if you select the disk usage attributes along with other attributes while creating a custom view, then the complete information for the machine will not be displayed.
For example, there are three machines in your setup: Machine 1, Machine 2, and Machine 3 and the Inventory scanner is configured to scan for disk usage on Machine 1 and Machine 2 only. If you create a custom view with attributes System Identification.Name, Disk Usage. Total Size, and Physical Hard Disk. Size for all the three machines, the custom view will display information for only Machine 1 and Machine 2.
The Inventory data will not be exported if you configure the following settings in the Data Export wizard:
NOTE: You will not encounter this issue if you set the filters for the attributes of these classes to NULL.
During Inventory Database export, if the query contains only software information and the "Enable Filter" option is selected, the exported file contains multiple instances of software information depending upon the number of patch and file information corresponding to the software.
For example, if a software has three patch releases and four executable files installed on the inventoried server, the exported file will contain four instances of the software information for the inventoried server.
The following are the Remote Management issues.
If a user uses the Remote Desktop Connection to connect to a Windows 2003 server, and then initiate a Remote Control session on that server, the Remote Control console will be black and you will not be able to remote control it.
Users with a Windows 2003 server should log in locally before you attempt to remote control their workstations.
In case of wallpaper suppression, Windows 2003 server behaves differently from other Windows operating systems. When you set the wallpaper, Windows 2003 server creates a backup of it. When you disable the wallpaper, it gets disabled only from the primary location. When you change the settings, the wallpaper may resurface.
If you upgrade a ZENworks for Servers 3 SP2 NetWare console (NetWare 6 SP3) to ZENworks 6.5 Server Management, RConsoleJ does not work through proxy.
Workaround: To workaround this problem, after upgrading to ZENworks 6.5 Server Management, you must delete the rconsolej.jar file used to invoke the RConsoleJ from the ConsoleOne directory (<ConsoleOne_installation_directory>\1.2\lib\zen).
During the ZENworks 6.5 Server Management installation, if you choose to install Remote Management on NetWare and Windows servers, the password that you specify for the Windows servers will not be applied.
Workaround: You have to manually set password on the Windows servers.
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, Task Manager), the mouse cursor flickers at the managed server. This behavior of the mouse can be 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 the Remote Management performance.
To workaround this problem, you must manually suppress the wallpaper of the managed server.
The animated and the colored cursors on the managed servers are not supported for Remote Management.
During a remote control session on the managed server, if you change the mode of display from DOS box application mode to full-screen mode, you do not receive updates until you refresh the full-screen mode or close and open it again.
The following are the Management and Monitoring Services issues.
1. In the sys:\<mms-installed-path>\mms\mwserver\bin\sloader.ncf file, replace the following line:
com.novell.utility.servicemanager.ServiceLoader
with:
com.novell.zfs.mms.utility.servicemanager.ZfS_MMS_Services
2. At the server prompt, enter sloader to restart the sloader service.
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.
Connection terminated abnormally.
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 "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 Apple Talk protocol installed and the performance is 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 counters DLLs are loaded in the SNMP address space. If there is a problem in the extension performance counters DLLs, the SNMP service will crash.
Workaround: To avoid the SNMP service from crashing disable the performance counters for the problematic 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 install the exctrlst_setup.exe file from the Microsoft web site and 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, the RAS is installed but may be disabled. Using the exctrlst_setup.exe. enable the RAS service to function correctly and disable the performance counters:
Shutdown and restart the machine.
In the Apple Talk Protocol example, disabling the performance counters for the service will solve the problem.
If the snmplog.nlm is not loaded on the site server, you will not receive new alarms. The snmplog.nlm file will not load if the build date of the loaded snmp.nlm and the snmplog.nlm is 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 will install 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 may not get copied sometimes because of timestamp mismatch. You can copy this file from the ZfS\SvrMgmt\mms\server\MWServer\nmdisk directory on the ZENworks 6.5 Server Management CD to the ZfS_installed_folder\mms\mwserver\nmdisk folder.
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.