The Novell® ZENworks® for Servers 3.0.2 update provides support for NetWare® 6.5. This update applies to both ZENworks for Servers 3.0.2 and ZENworks for Servers 3 Support Pack 2 (SP2), but not to earlier versions of ZENworks for Servers 3.x or ZENworks for Servers 2.
This Readme provides installation instructions for installing the update and provides issues related to support for NetWare 6.5. For more information, see 1.0 Understanding the Update. For information on issues related to using ZENworks for Servers with NetWare 6.5, see 3.0 Known Issues.
To download the ZENworks for Servers 3.0.2 Update for NetWare 6.5 files (contained in the ZfS302_NW65.exe file), see Technical Information Document 10083888.
For information on ZENworks for Servers 3.0.2, see the documentation Web site.
This update is designed to allow ZENworks for Servers 3.0.2 and ZENworks for Servers 3 SP2 to support NetWare 6.5 servers.
IMPORTANT: This update for NetWare 6.5 support will not work with earlier versions of ZENworks for Servers.
ConsoleOne 1.3.6 and iManager 2.0 are not supported. For more information, see 1.2 Updating ConsoleOne and 1.3 Updating Novell iManager.
To download the ZfS302_NW65.exe update file, see Technical Information Document 10083888.
Running ZfS302_NW65.exe creates the ZfS302_NW65 directory. If you downloaded the ZEN6_NW65.exe file for the ZENworks 6 suite, it also contains the ZfS302_NW65 directory.
In addition to this Readme, the ZfS302_NW65 directory contains the following two files:
novell_rconsole_atlas.jar
novell_rconsole_NDSZFS.jar
These two .jar files make Remote Management compatible with NetWare 6.5 by updating each instance of ConsoleOne® 1.3.5 that is used for remote management of a NetWare 6.5 server.
These files provide the complete update to allow ZENworks for Servers 3.0.2 and ZENworks for Servers 3 SP2 to support NetWare 6.5, except as outlined in 3.0 Known Issues.
The ZENworks for Servers 3.0.2 snap-ins do not support the ConsoleOne 1.3.6 that ships with NetWare 6.5.
ConsoleOne 1.3.5 snap-ins do not need to be updated for Management and Monitoring Services, Policy and Distribution Services, or Server Inventory. The only ConsoleOne updates are the .jar files for Remote Management, as listed in 1.1 Contents of the Update.
The ZENworks for Servers 3.0.2 plug-ins do not support the iManager 2.0 that ships with NetWare 6.5.
You can continue to use Novell iManager 1.5.1 to manage all of the different servers in your network, including NetWare 6.5, NetWare 6, NetWare 5.1, Windows*, Linux*, and Solaris* servers. In other words, to manage a NetWare 6.5 server in a system with multiple NetWare versions, you do not need to install iManager on a NetWare 6.5 server. iManager only needs to be installed on one server somewhere in your network.
However, if your network has only NetWare 6.5 servers, then you must install iManager 1.5.2 on a server where ZENworks for Servers is installed, then install the ZENworks for Servers 3.0.2 plug-ins to that instance of iManager 1.5.2. These plug-ins will work in iManager 1.5.2 without modification to support NetWare 6.5. You can obtain iManager 1.5.2 from the Novell Download site.
For information on running iManager 1.5.2 and 2.0 concurrently on NetWare 6.5, see TID 10086292 on the Novell Support Web site.
You must meet the prerequisites outlined below before installing this update.
Download and run ZfS302_NW65.exe.
This creates a ZfS302_NW65 directory. If you downloaded the ZEN6_NW65.exe file for the ZENworks 6 suite, it also contains the ZfS302_NW65 directory.
Exit the instance of ConsoleOne 1.3.5 that you will be updating.
Manually copy the following .jar files from the ZfS302_NW65 directory:
novell_rconsole_atlas.jar
novell_rconsole_ndszfs.jar
to the following location:
consoleone\1.2\snapins\zen
These files will replace existing files of the same names.
Restart the updated instance of ConsoleOne.
Repeat through for each instance of ConsoleOne 1.3.5 to be updated.
ZENworks for Servers will now support NetWare 6.5 servers, except as outlined in 3.0 Known Issues.
The following issues are known to exist for ZENworks for Servers' support of NetWare 6.5.
This section contains two known issues for ZENworks for Servers: ConsoleOne 1.3.6 and iManager 2.0 are not supported.
ZENworks for Servers 3.0.2 and ZENworks for Servers 3 SP2 do not support ConsoleOne 1.3.6, which is the version included with NetWare 6.5.
If necessary, ConsoleOne 1.3.5 and 1.3.6 can coexist on the same machine, enabling you to perform ZENworks for Servers administration in ConsoleOne 1.3.5 and NetWare 6.5 administration in ConsoleOne 1.3.6.
To provide support for NetWare 6.5 servers, you only need to update the snap-ins to ConsoleOne 1.3.5 as noted in 1.0 Understanding the Update.
ZENworks for Servers 3.0.2 and ZENworks for Servers 3 SP2 do not support iManager 2.0, which ships with NetWare 6.5.
The only iManager versions supported by ZENworks for Servers 3.0.2 or 3 SP2 are version 1.5.1 installed on a server of any NetWare, Windows, Linux, or Solaris version that is supported by ZENworks for Servers, or version 1.5.2 installed on a NetWare 6.5 server or other servers supported by iManager 1.5.2.
You can obtain iManager 1.5.2 from the Novell Download site.
If IP Address Management is used to change the IP address of your NetWare 6.5 server running the ZENworks for Servers site server, Management and Monitoring Services might not function correctly.
To correct the problem:
Change the IP address in the sys:\system\mgmtdbs.ncf file for the -n switch.
Change the IP address in the zenworks\mms\mwserver\properties\sloader.properties file.
The IP address exists as a part of the Arguments key under the following service descriptions:
Restart Management and Monitoring Services.
Modify the trap destination address of all the managed servers to reflect the new IP address of the site server.
This section contains two known issues for Policy and Distribution Services: IP Address Management and encrypted Distributions in a NetWare 6.5 environment.
The IP Address Management feature in NetWare 6.5 can cause the ZENworks for Servers 3.0.2 Distributor and Subscriber services to not recognize an IP address change.
Subscriber Service Running on a NetWare 6.5 Server
If the IP address is changed using IP Address Management for a NetWare 6.5 server running the Subscriber service, all servers involved in the distribution process for that Subscriber must have Java unloaded and reloaded before they will recognize the new DNS name/IP address of the Subscriber server. This includes the following servers:
Each of these servers must have Java unloaded and reloaded, or they will not be able to send or pass on Distributions to the NetWare 6.5 Subscriber server that had its IP address changed.
Distributor Service Running on a NetWare 6.5 Server
If the IP address is changed using IP Address Management for a NetWare 6.5 server running the Distributor service, you might see the following three issues:
Managing with ConsoleOne and iManager: These management components cannot communicate when a Distributor running on a NetWare 6.5 server has had its IP address changed until the workstation running ConsoleOne is rebooted and the server hosting iManager is rebooted.
Distributor Service: Because Java* caches DNS name/IP addresses, you must unload and reload Java before the Distributor will have the new DNS name/IP address.
Sending Distributions: When the Distributor sends Distributions from a NetWare 6.5 server where the IP address has been changed, the Subscribers cannot reply, because Java caches the DNS name/IP addresses on each of the Subscriber servers, and Java must be reloaded before the new DNS name/IP address of the Distributor is discovered on DNS lookup.
Concerning Java caching:
JVM 1.3.x: The Internet Address cache cannot be configured and will not refresh until Java is unloaded and reloaded.
JVM 1.4.x: The Internet Address cache can be configured. The default is to cache successful IP address lookups for as long as the application is running. To modify this behavior, see the InetAddress Caching section of the InetAddress class documentation on the Sun Microsystems* Web site.
If you are not using the encryption feature of Tiered Electronic Distribution, then you will not experience this problem.
If you stop the TED processes on a NetWare 6.5 server by unloading or killing Java, or by typing exitall at the ZfS console prompt, and the processes are then restarted, the "Unable to generate ephemeral keys" error will be displayed on the TED console, which means you will be unable to build, send, or extract encrypted Distributions. You will need to restart the server to get encryption to work.
However, to work around this problem and not have to restart the server, use the systemexit command at the TED console prompt to exit the TED process, then exit the ZfS and ZWS processes using the exitall command at the ZfS console prompt. Encryption will then work after you restart ZENworks for Servers using the zfs command.
If you use IP Address Management to change the IP address of the NetWare 6.5 server that has ZENworks for Servers 3.0.2 Server Inventory installed, the following will not work:
To resolve this issue:
If the Inventory database is running on Sybase:
Edit sys:\system\mgmtdbs.ncf to change the IP address of the -n parameter to the new IP address.
In ConsoleOne, right-click the database object.
Restart the Sybase Inventory database.
Change the IP address of the Inventory server and the proxy server (if configured) in the Server Inventory policy to the new IP address.
For information on how to change the IP address in the Server Inventory policy, see Configuring the Server Inventory Policy in the ZENworks for Servers 3.0.2 Administration Guide.
Restart the Inventory services.
If the scan data is rolled up to this Inventory server:
Change the IP address of the destination Inventory server and the proxy server (if configured) in the Roll-Up policy of the associated lower-level Inventory servers to the new IP address.
For information on how to change the IP address in the Roll-Up policy, see Configuring the Roll-Up Policy in the ZENworks for Servers 3.0.2 Administration Guide.
Restart the Inventory services on the associated lower-level Inventory servers.
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, and ZENworks are registered trademarks of Novell, Inc. in the United States and other countries.
All third-party trademarks are the property of their respective owners.