November 11, 2002
This document was updated in the following sections on the dates indicated:
September 13, 2002 = 4.9.1, 4.9.2, 4.9.3
September 20, 2002 = 4.9.1
November 11, 2002 = 4.9.3.4
This Readme includes the installation notes and product issues that you need to know as you install and use Novell® ZENworks® for Desktops (ZfD) 4. As it becomes available, other updated information will be included at the ZENworks for Desktops 4 Documentation Web site.
The following policies will not be supported in new releases of ZENworks for Desktops:
Although they can be configured locally, certain security settings cannot be extended to a Windows XP Group Policy on the network because Microsoft doesn't publish any method to modify them. The following security settings cannot be modified and will not work in a Windows XP Group Policy pushed to the network:
Before you install the ZENworks for Desktops Server components on a NetWare® server, you need to exit ConsoleOne® sessions and stop the other Java* components running on that server. These processes will hold open a number of files that will not be updated because they are in use.
To stop Java components on the NetWare server, enter the following commands at the server console:
Java -killall
Java -exit
You will need to restart the NetWare server after you install the ZfD Server software so that all ZfD services will load properly.
The ZfD Server installation program reads its AUTOEXEC.NCF file to find and use the first listed BIND IP Address statement. If the file has two or more BIND IP Address statements and if the first address is incorrect or inactive, the installation will fail.
To correct the problem, make sure that the correct IP address is listed first in the AUTOEXEC.NCF file.
If you are trying to install ZfD Server software to a Windows 2000 server, you may not be able to add it as a targeted server in the Add Servers dialog box, particularly if Novell eDirectory™ is installed on the Windows 2000 server and you are authenticated to eDirectory. You must also be authenticated through Windows in order for the file transfer to occur during the installation.
Use the following steps to authenticate to the target server:
zenserver\administrator
\\zenserver\C$
If you install NetWare 6 SP1 on a server that already has ZfD Middle Tier Server installed, the ZfD Middle Tier Server will stop working. If this happens, you need to reinstall the ZfD Middle Tier Server software.
If you install the ZfD Middle Tier Server software on a Windows 2000 server, you must restart that server twice to load the newly-installed software.
If you want to use the Application Browser view of the Novell Application Launcher™, some additional configuration is necessary if you have installed ZfD Middle Tier Server software to a NetWare 5.1 server where APACHE\HTDOCS is the default directory of the Apache files.
You need to manually copy two files, MYAPPS.HTML and ZFDWEBSW.EXE, from the \APACHE\NWDOCS directory to a public directory (the default is \APACHE\HTDOCS) on this server.
The ZfD Management Agent installation program, InstallShield*,
checks the TEMP and TMP environment variables in System Properties of the Windows
workstation for a location it can use to install. If the workstation doesn't
have these variables defined, or if these variables point to an invalid location,
the following error will be displayed:
error:1201 setup needs 8000kb free space in C:\
After you have installed the ZfD Management Agent on Windows NT 4.0, Windows randomly generates a Dr. Watson error for IDRIVER.EXE when you reboot. To work around the problem, run the ZfD Management Agent Installation program, SETUP.EXE, on the workstation again.
The method for upgrading the ZfD Management Agent, as documented in the ZfD 4 Installation guide, has been disabled for the initial release of ZfD 4. Novell will make an enabling patch available at a later date. The patch will be available at the Novell Support Connection Web site at http://support.novell.com in TID 10073212.
If you install the ZfD Management Agent on a Windows workstation that has an older version of the Novell Client (version 4.82 or older for Windows NT/2000, or version 3.31 or older for Windows 98) already installed, uninstalling this older version of the client will delete some key files that are required by the ZfD 4 Management Agent.
If you remove the older client after the ZfD Management Agent has been installed, you must subsequently reinstall the ZfD Management Agent to restore the key files needed for ZfD functionality on the workstation.
If some ZfD components are installed on a Windows workstation using the ZfD Management Agent installation, and if the Modify option of the ZfD Management Agent installation is subsequently used to add other ZfD components to the workstation, the user will be required to authenticate through a Windows login and then through the ZfD Management Agent login. If you continue to use the product with two logins as described, you will experience limited ZfD functionality.
We recommend that you use the Remove option of the ZfD Management Agent installation program to remove all of the workstation components; then, during a single installation session, reinstall all of the components that you want.
If you run the ZfD Management Agent installation program with a response file to perform a silent installation, the installation program will not generate any error message if the hardware and software installation prerequisites are not met on the workstation you are installing to. For example, if the workstation has Internet Explorer 5.0 installed rather than the required version 5.5, the installation program proceeds to completion, but the agent is not successfully installed.
Although the ZfD Management Agent installation program lets you install to any location you choose, do not install to the same path where the Novell Client was previously installed (\WINNT\SYSTEM32 on Windows NT/2000/XP workstations, \NOVELL\CLIENT32 on Windows 98 workstations). Installing to this directory will cause the ZfD files to be deleted when the workstation is rebooted, disabling the ZfD Management Agent.
Do not install the ZfD Management Agent to a Windows 2000 server that has Active Directory installed. Doing so may cause the server to lock up without a way to recover.
ZENworks for Desktops 4 does not support DNS-rooted trees or federated trees.
If you try to authenticate through the ZfD Middle Tier Server to a ZfD Server installed on a Windows 2000 machine that already has Active Directory (installed because the ZfD Server acts as the Primary Domain Controller) and eDirectory (installed to accommodate ZfD) both installed, the authentication will fail unless the user logs on with a full context.
The reason for this failure is a contention for the default LDAP port between the Active Directory and eDirectory LDAP listeners. To work around this port conflict, during the installation of eDirectory, choose an LDAP port other than the default, then use the NSADMIN utility in the ZfD Middle Tier Server to configure the ZfD Middle Tier Server to communicate over that port.
To configure the port in NSADMIN, follow these steps:
http://IP_address/oneNet/nsadmin
If you try to manually unload the Middle Tier Server Handlers (for example, XZEN.NLM) running on NetWare 5.1 or NetWare 6, the server will abend.
On NetWare 6, you should use NVXADMDN to unload Apache and Middle Tier handlers. Use NVXADMUP to restart Apache and Middle Tier handlers.
On NetWare 5.1, enter the following command:
unload apache
Using NDSCONS.EXE on Windows 2000 to verify the connection between the ZfD Middle Tier Server and the ZfD Server will not work unless you have Administrator rights for the local Windows 2000 user.
If a user tries to log in with a User ID only, if the user tries to log in with an incorrect password, or if the user's eDirectory object is defined with the maximum number of attributes, the ZfD Middle Tier Server might not return a new login for a new attempt at authentication.
The problem occurs when the ZfD Middle Tier Server software is installed on a NetWare server. ZfD Middle Tier Server software installed on a Windows 2000 server is not affected.
To work around this problem, users should log in with a fully-distinguished name in order to authenticate.
Example: joe.users.myorg
If many (that is, hundreds of) users attempt to log in to the network at the same time through a ZfD Middle Tier Server on NetWare 6, the server may hang due to high utilization problems. To fix this problem, download and install the patch for Novell Storage Services™ (NSS) available from Novell Support at http://support.novell.com. Search for TID 10072765.
If the Novell Client and the ZfD Management Agent are both installed on a workstation and if the workstation fails to authenticate at login time (sometimes evident because workstation polices are not applied), make sure the SLP Directory Agent is configured correctly:
Alternatively, you can modify the SLP.CFG file in the \SYSTEM\ETC directory of a ZfD Server on NetWare 6 to reference a NetWare 5.1 server where the Directory Agent is loaded. This NetWare 5.1 server need not be running ZfD Server software.
For more information, search for Service Location Protocol in the NetWare documentation at http://www.novell.com/documentation.
If the Novell Client and the ZfD Management Agent are installed on a workstation (for example, a laptop workstation) and that workstation is taken outside of the corporate firewall, only the traditional Novell Client login will be displayed at login, and the user will only be able to log in locally by choosing Workstation Only.
In this scenario, ZfD Workstation Management will not work (that is, no ZfD policies will be applied and Workstation Manager will not work), but ZfD Application Management will work (that is, applications will be available from the Application Browser view of the Novell Application Launcher).
Remember that if you have only the ZfD Management Agent installed on a workstation outside the firewall, ZfD Policies and the Workstation Manager will work.
Although NAL.EXE and NALEXPLD.EXE are included the product and still launch executables, their purpose is to facilitate the continued functioning of existing login scripts.
The ZENworks for Desktops 4 release only supports flags that are supported by NALWIN32.EXE. To see a list of these flags, type the following command:
nalwin32.exe /?
Running NAL.EXE from the server returns the following error:
The ordinal 6625 could not be located in the dynamic link library MFC42.DLL
This error occurs because an older version of MFC42.DLL is already installed on the server in SYS\PUBLIC. To work around the problem, you need to copy a newer version of MFC42.DLL to this location. You can find a newer version in the \SUPPLEMENTAL folder of the ZENworks for Desktops 4 Companion CD.
The new Terminal Server system requirement on an Application object applies only to remote Terminal Server sessions. Sessions running at the Terminal Server console are considered to be remote sessions by default. This behavior can be changed by creating the following registry key on the Terminal Server itself:
HKEY_LOCAL_MACHINE\Software\Netware\Nal\ConsoleIsNotTS
Creating this registry key will cause sessions running on the Terminal Server console to be treated as non-Terminal Server sessions.
Applications running in an off-line state will be automatically uninstalled in the following scenario:
This is a known issue and currently does not have a fix or a workaround other than disabling uninstall or the Manage Applications dialog box.
Applications cannot be delivered through a network firewall if ZfD Server software and ZfD Middle Tier Server software are installed and running on a Windows 2000 server.
If the ZfD Server and the ZfD Middle Tier Server use Active Directory and Windows Domains, and if the ZfD Middle Tier Server is part of a domain, create a user and password in Active Directory to correspond exactly to the username and password in eDirectory. The Middle Tier Server and the ZfD Server must be members of the same Active Directory domain. Windows workgroups do not work.
A key component of Novell Licensing Services, NLS32.DLL, does not ship with the current Novell Client. As a result, an error will be generated when you try to use Software License Metering and Monitoring in ZfD.
You can find a newer version of NLS32.DLL in the \NAL LICENSING folder of the ZENworks for Desktops 4 Companion CD. Copy NLS32.DLL to the following location:
Windows NT/2000/XP Workstation: Copy to C:\WINNT\SYSTEM32
Windows 98 Workstation: Copy to C:\WINDOWS\SYSTEM
Upgrading a Windows 2000 workstation hard disk from a Basic Disk System to a Dynamic Disk System changes the partition table so that it does not does not allow the workstation to boot to the production partition, only to the ZfD Linux* partition. No fixes for this issue are included in ZfD 4.
If you choose to use dynamic disks on the workstation, you must create the image after the disks have been upgraded from basic to dynamic disks.
The display adapters listed below do not support the Screen Blanking feature of Remote Management. The managed workstation screen will not be blanked when these adapters are used.
IMPORTANT: Some of the following adapters may cause the managed workstation to hang or crash.
In addition, the Screen Blanking feature will not work on any display adapter that is not 100% VGA-compatible.
If the managed workstation has a full-screen DOS window open, you will not be able to remotely control it.
During a Remote Control or Remote View session, the active desktop wallpaper on the managed workstation might not be suppressed.
To improve the Remote Management performance, suppress the wallpaper before starting the Remote Control or Remote View session.
The animated and the colored cursors on the managed workstation are not supported for Remote Management.
Password-based authentication will fail if spaces are included in the password that is used to initiate a Remote Management session.
Only English characters are supported in the Remote Management password on non-English platforms. If extended characters are used while setting the password, Remote Management authentication will fail.
The ZfD 4 Inventory database cannot be mounted on a Sybase* Adaptive Server* Anywhere 8 database. Also, the Sybase engine shipping with ZfD 4 cannot coexist on a NetWare server where Sybase ASA 8 is running.
If the Novell Client is not installed on inventoried workstations, and if you use double-byte characters in the Inventory Service object's scan directory (SCANDIR ) path, the .STR files will not be transferred to the Inventory server.
By default, the SCANDIR path is the installation path where the Inventory server-side components and the database are installed (unless you manually changed it after the ZfD 4 installation by configuring the Inventory Service object).
If you previously installed ZfD 3 on a NetWare 4.x server,
then you upgrade that server to NetWare 5.x or later, the server will abend
when you restart it after the ZfD upgrade.
This situation occurs because the NetWare 5.x/6 migration tool is unaware of
an existing ZfD 3 file, IMGSERV4.NLM, which is meant for use by NetWare 4 only.
To work around this problem, you should edit the line that loads IMGSERV4.NLM
in the ZFDSTART.NCF file to load IMGSERV.NLM instead. This version of the .NLM
is used by NetWare 5 and NetWare 6.
When installed to the same network location, ZENworks for Desktops 4 and ZENworks for Servers (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.
For more detailed information on ZfD 4 and ZfS 3 SP1
Inventory interoperability, see Interoperability
with ZENworks for Servers 3 in the Workstation Inventory section
of the ZENworks for Desktops 4 Administration
guide at http://www.novell.com/documentation/lg/zdpr/index.html.
Novell iChain features such as SSO, Caching, Access Control, Secure Exchange, etc. are not currently supported with ZfD 4. ZfD 4 features will work through an iChain 2.0 tunnel.
The following sections provide the details of what will not work properly in ZfD 4 if ZfD 3.2 is also running.
4.9.3.1 Rollup Database Server Does Not Work
If you have a network environment with a ZfD 4 Workstation Inventory root server and an intermediate server or leaf server that is ZfD 3.2, the inventory service on the intermediate or leaf server will not start. In this scenario, the ZfD 3.2 inventory service displays the following error:
getID() out ->exception[Root exception is com.novell.service.jncp.NDSException: ccode = -669 (0xfffffd63)]com.novell.java.security.LoginException: Login failed.
If the ZfD 3.2 server is the root server and ZfD 4 is the intermediate server or leaf server, the inventory service on the intermediate/leaf server will not start. The following error is displayed:
Error Type 15 Error 630
The problem can be resolved by applying a software patch to the ZfD 3.2 server. For more information, see the ZENworks for Desktops 4 Upgrade guide at http://www.novell.com/documentation/lg/zdpr/index.html.
4.9.3.2 Inventory Query Does Not Work if the ZfD 3.2 C1 Snap-ins Are Loaded
If you load ConsoleOne from the ZfD 3.2 server, you cannot view the workstation inventory information if the workstation was inventoried into the ZfD 4 database. Users will get the error that the workstation inventory is not available in database.
If you load ConsoleOne from the ZfD 4 Server, you will be able to see workstation inventory information of the workstation that is inventoried in either a ZfD 3.2 database or ZfD 4 database.
4.9.3.3 ZfD 4 Remote Control Features Do Not Work on a ZfD 4 Workstation if ZfD 3.2 Snap-ins Are Loaded
ZfD 4 Remote Control features will fail if the remote workstation has the ZfD 4 agents installed and if the Remote Management Console has ConsoleOne loaded with ZfD 3.2 ConsoleOne snap-ins.
ZfD 4 Remote Control features will work if the remote workstation has the ZfD 3.2 agents installed and if the Remote Management Console has ConsoleOne loaded with ZfD 4 ConsoleOne snap-ins.
4.9.3.4 ZfD 4 Upgrade Does Not Overwrite ZfD 3.2 SP1 Files
If you upgrade from ZfD 3.2 SP1 to ZfD 4, the ZfD 4 installation program does not overwrite some ZfD 3.2 SP1 files because the ZfD 3.2 SP1 file dates are later the ZfD 4 file dates.
The following is a list of files that need to be renamed (to *.XXX_OLD for example) before upgrading a ZfD3.2SP1 system to ZfD4. Prior to renaming the following files, close all ConsoleOne sessions and shut down the wsimport java service.
ConsoleOne_path\BIN\ZEN\REMCON\NLS\ENGLISH\REMCTRL.CHM REMCTRL.CHM_OLD
ConsoleOne_path\BIN\ZEN\REMCON\LDWMNT.DLL LDWMNT.DLL_OLD
ConsoleOne_path\LIB\ZEN\DESKTOP.JAR DESKTOP.JAR_OLD
ConsoleOne_path\LIB\ZEN\REPORTINGIMAGES.JAR REPORTINGIMAGES.JAR_OLD
ConsoleOne_path\LIB\ZEN\ZENCOMMON.JAR ZENCOMMON.JAR_OLD
ConsoleOne_path\RESOURCES.JAR RESOURCES.JAR_OLD
ConsoleOne_path\SNAPINS\ZEN\DBOBJSNAPINS.JAR DBOBJSNAPINS.JAR_OLD
ConsoleOne_path\SNAPINS\ZEN\DESKTOPSNAPINS.JAR DESKTOPSNAPINS.JAR_OLD
ConsoleOne_path\SNAPINS\ZEN\DATAEXPORTSNAPINS.JAR DATAEXPORTSNAPINS.JAR_OLD
ConsoleOne_path\SNAPINS\ZEN\INVENTORYSNAPINS.JAR INVENTORYSNAPINS.JAR_OLD
SYS\java\lib\autoWSManagement.jar autoWSManagement.jar_old
SYS\PUBLIC\zenworks\lib\zencommon.jar zencommon.jar_old
ZfD 4 customers whose networks run in an Active Directory or Microsoft Domain environment can download and use the DirXML 1.1 engine, the DirXML® 1.1 Driver for Microsoft Active Directory (AD), and the DirXML 1.1 Driver for NT Domain, which are all contained in the download for DirXML 1.1 available at http://www.novell.com/download. Additionally, ZfD 4 customers can use DirXML 1.0 Password Synchronization (available as a separate download) as part of the ZfD 4 license purchase.
90-day evaluation licenses are included with the DirXML products and are initiated
upon installation of the software. In order to use the DirXML software past
this 90-day evaluation time limit, you will be required to activate the software
using a Customer Identification number. This number is received with your electronically
delivered ZfD 4 Certificate of License and Authenticity. More detailed instructions
on the activation process can be found at http://www.novell.com/activator/Help.jsp
and in the online documentation delivered with the DirXML software downloads.
These DirXML products make it easier to manage ZfD users in a Windows server environment in the following ways:
Use the following steps to download the DirXML 1.1 drivers:
When you run the DirXML 1.1 driver installation program, you will be able to select the drivers you want from the drivers list. You are granted licenses to the DirXML 1.1 Driver for Active Directory and the DirXML 1.1 Driver for NT Domain only. For more information about installing the drivers, see the DirXML 1.1 documentation Web site at http://www.novell.com/documentation/lg/dirxmldrivers/index.html.
IMPORTANT: We recommend that you install, configure, and fully test the DirXML Drivers in a ZfD lab environment prior to using them in your production environment.
Use the following steps to download PasswordSync:
For more information about installing password synchronization, see the Password Synchronization for Windows documentation Web site at http://www.novell.com/documentation/lg/pwdsync10/index.html.
IMPORTANT: We recommend that you install, configure, and fully test PasswordSync in a ZfD lab environment along with DirXML 1.1 Drivers prior to using it in your production environment.
Wise InstallTailor*, a tool that can help you customize your .MSI installations for distribution by ZfD 4, is included in the \WISE folder of the ZENworks for Desktops 4 Companion CD. For more information about installing and using Wise InstallTailor, see the Installation guide at the ZENworks for Desktops 4 documentation Web site. at http://www.novell.com/documentation/lg/zdpr/index.html.
This product and its accompanying documentation are designed to make accessibility easier for people with disabilities. If you are unfamiliar with the control or shortcut keys used in Java* software, you can find a list of these keys at the Swing Component Keystroke Assignments Web site at http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/doc-files/Key-Index.html.
To navigate in the JavaHelp* online help system, use the following keystrokes:
JavaHelp 1.1 is currently inaccessible via JAWS screen reader software. To access JavaHelp with a screen reader, use the IBM Self-Voicing Kit available from IBM.
The Crystal Report Viewer window does not support keyboard functionality. You must use the mouse to perform all operations in the viewer window.
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© 1999-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.
US Patent Nos. 5,633,931; 5,692,129; 5,758,069; 5,761,499; 5,859,978; 5,893,118; 5,905,860; 6,023,586; 6,047,312; 6,061,743; 6,105,069; 6,115,549; 6,144,959; 6,173,289. Patents Pending.
ConsoleOne, DirXML, Novell, Novell Support Connection, NetWare, and ZENworks are registered trademarks of Novell, Inc. in the United States and other countries.
eDirectory, NLM, Novell Application Launcher, Novell Cluster Services, Novell Client, and Novell Storage Services are trademarks of Novell, Inc. .
All third-party trademarks are the property of their respective owners.