ZENworks 2 January 14, 2000 This document is a record of the issues that you should be aware of in the ZENworks 2 product. The information included here is not included in product documentation elsewhere. Table of Contents 1.0 Installation 1.1 Installation Errors 1.1.1 Error When Not Installing Novell Clients 1.1.2 Errors Resulting from a Custom Installation of the Novell Client for Windows NT 1.1.3 Error When Installing on an IPX Server 1.1.4 Error When Choosing a Volume for Database Installation 1.1.5 Error When Installing on a NetWare 4.x Server 1.1.6 Error At the End of Installation 1.2 Installing ZENworks from a Server Image 1.3 Removing ZENworks from the Installing Workstation 1.4 Reinstalling ZENworks 2 1.5 NDS for NT Server System Requirements 1.5.1 Known Issues Regarding ZENworks and NDS for NT 1.6 Additional Memory Requirements for Running the Sybase Inventory Database 2.0 NetWare Administrator 2.1 Invoking NetWare Administrator on an IPX-only Workstation 2.2 Using ZENworks NetWare Administrator 32 2.2.1 Policy Objects May Appear in NetWare Administrator 32 2.2.2 Running Snap-In DLLs Using NetWare Administrator 32 2.2.3 Running Numerous Snap-Ins with NetWare Administrator 32 2.2.4 Using NetWare Administrator 32 with the NetWare 5 Client 2.2.5 Using ZENworks on a Non-English Server 2.3 Using NetWare Administrator 95 or NetWare Administrator NT 2.4 Authenticating to a New NDS Tree Using NetWare Administrator 95 or NetWare Administrator NT 2.5 Using FastCache and BorderManager Snap-Ins 2.6 User Profiles Snap-In 3.0 Application Management 3.1 General Known Problems and Limitations 3.1.1 Creating Application Objects with NetWare Administrator for Windows 95 3.1.2 Creating Application Objects with NetWare Administrator for Windows NT 3.1.3 Using the Timed Refresh Setting 3.1.4 Windows 3.1 and UNC 3.1.5 An Application Object in Tree 1 Cannot Capture a Printer Port to a Server in Tree 2 3.2 Application Launcher 3.0 3.2.1 Application Launcher Files Installed with the NT Client 3.2.2 Application Launcher 2.01 and Earlier Files That Can Be Removed after Installation 3.3 Application Launcher Snap-Ins 3.4 Application Explorer 3.4.1 Duplicate Icons in the System Tray 3.4.2 Creating Application Explorer Desktop Icon for Users Connected to Windows NT Terminal Server or Citrix 3.5 snAppShot 3.5.1 DOS Shortcuts (PIF) 3.5.2 Drive Mappings 3.5.3 Rights to Destination Directory 3.5.4 GroupWise Client (32-Bit) 3.6 SNMPLOG File Size in Alarm Manager 4.0 Workstation Management 4.1 Workstation Inventory 4.1.1 The Sybase Inventory Database 4.1.2 Filenames 4.1.3 Workstation Inventory Window 4.1.4 Inventory Query 4.1.5 Inventory Scan Program 4.1.6 Software List Editor 4.1.7 Configuring an Inventory Policy on NetWare 4.11 4.1.8 Using the Run Now Button to Manually Run the Inventory Policy 4.2 User Policy Package 4.2.1 Getting the Correct Paper Size When Distributing Printers 4.2.2 Troubleshooting the Windows 95 User Policy Package 4.3 NT User System Printer Policy 4.4 RAS Configuration Policy 5.0 Remote Management 5.1 Remote Management Agent 5.2 Improving Performance on Window NT Workstations Running 256 Colors or Less 5.3 Screen Savers 5.4 Windows NT System Requirements 5.5 Remote Control Performance over a WAN 5.6 CPU Utilization 5.7 Remote Control with a Full-Screen DOS Box 5.8 Security 5.9 Automated Time-Out 5.10 Dial-Up Connections 5.11 File Transfer 5.11.1 File Transfer Options Not Available 5.11.2 Scroll Bar Display 6.0 ZENworks Reporting and Database Backup 6.1 Reporting Screen 6.2 Generating Lengthy Inventory Reports 6.3 Database Backup 7.0 Novell Client 7.1 Using an Outdated Novell Client for Windows NT 7.2 The Primary Network Logon Must be the Novell Client 7.3 Upgrading the Novell Client without a Full Install 7.4 Running WM3X.EXE (the DOS/Windows Client) using Windows 3.x 8.0 Interoperability 8.1 Using ZENworks with Third-Party Remote Control Software 8.2 Using ZENworks with ManageWise 2.6 8.2.1 ZENworks Features Available in ManageWise 8.2.2 Implementing Remote Control from ManageWise 8.3 Using ZENworks with NDS for NT 2.0 8.4 Using ZENworks with McAfee VirusScan 8.5 Using the English Version of ZENworks on Double-Byte Machines 9.0 Y2K Readiness 10.0 Product Documentation 10.1 Installation and Upgrade Guide 10.2 Online Help 10.2.1 Error When Clicking Help Button 10.3 Documentation on the Internet 10.4 Other Product Information 10.4.1 ZENworks Cool Solutions 10.4.2 Third-Party Tools Information 11.0 Legal Information 11.1 Disclaimer, Copyright, and Patents 11.2 Trademarks README Addendum: ZENworks 2 International Release ================================================================= 1.0 Installation 1.1 Installation Errors 1.1.1 Error When Not Installing Novell Clients During the ZENworks 2 install, if you select all install options except copying the clients over to the server, you may receive the following error just before launching the install: **** Question **** **** GetServerInternetAddress (ServerName) failed. The inventory database will not be active. Do you wish to ignore this condition and continue? **** The most likely cause of this error is that IP is not bound. You can continue with the install, but the Inventory server will not be included and the Inventory component will not work. 1.1.2 Errors Resulting from a Custom Installation of the Novell Client for Windows NT Novell recommends the Typical Installation option to most customers installing the Novell Clients. If you are installing the Novell Client for Windows NT and you choose Custom Installation, do not check all of the components listed under custom installation and do not click the Select All button. If you mistakenly select all of the components and continue with the installation, you may receive errors and ZENworks Remote Management or the Novell IP Gateway components may not function properly. A Custom Installation for the NT Client will work if you do not select all of the components listed for installation. 1.1.3 Error When Installing on an IPX Server If you install ZENworks 2 on a NetWare server running IPX only, you will receive the following error: GetServerInternet Address (ServerName) failed. The inventory database will not be active. Do you wish to ignore this and continue? If you ignore the error, you can continue with the install, but the Inventory server will not be included in the installation and the following items will not work: - Workstation Inventory Query - Workstation Inventory - Deletion of a Workstation object from the inventory database 1.1.4 Error When Choosing a Volume for Database Installation If you receive an error when you are asked to choose a volume for the Inventory database, it is probably because that volume does not support long name space. Make sure that long name space has been enabled on the volume where ZENworks 2 and the Inventory database is to be installed. 1.1.5 Error When Installing on a NetWare 4.x Server The following error may occur while you are installing ZENworks on a NetWare 4.x server: "this server cannot resolve its own hostname please configure DNS hostname resolution" hit any key To resolve the error, edit the SYS:\ETC\HOSTS file to include the IP address and the name of the file server. For example: 137.65.254.254 Failure to add this information may result in a server abend displaying the following text: abend: Free called with a memory block that has a null resource tag. 1.1.6 Error At the End of Installation When the installation process is finished and the ZENworks server tries to connect to the Inventory database across the network, you may see the following error: java.net.unknownHostException: local host This error occurs when the inventory programs (e.g. STORER.NCF, GATHERER.NCF) are loading. The error will also occur when you try to reload STORER.NCF or reboot the server. To correct the problem, add the following line to the SYS:\ETC\HOSTS file: 127.0.0.1 loopback lb local host # normal loopback address 1.2 Installing ZENworks from a Server Image If you copy ZENworks from the CD onto a server, you will need to map root to the directory from where you run WINSETUP.EXE. Otherwise, the installation program might not be able to locate certain .HLP files. 1.3 Removing ZENworks from the Installing Workstation The ZENworks install program will abort if the uninstaller setup fails to initialize. If you click OK, a blue screen displays the following error: SEVERE error--IRQL_NOT_LESS_OR_EQUAL address 80128709 base at 80100000 ntoskrnl.exe To resolve the error and uninstall ZENworks, log in to the server, from the Windows Start Menu, click Settings > Control Panel > double-click Add/Remove Programs > click ZENworks > Add/Remove. 1.4 Reinstalling ZENworks 2 If you reinstall ZENworks 2 on a server, numerous Java or Sybase database errors will occur because of the components that are loaded and running on the server. You can use two different procedures to unload these components and reinstall ZENworks successfully. Procedure A: Unload NLMs, then edit AUTOEXEC.NCF. (Does not require a server restart.) 1) Determine the process ID of the Master, Storer, and Alarm Manager processes by typing the following at the server console: java -show 2) Kill the processes for Master, Storer, and Alarm Manager by typing the following at the server console for each process: java -kill 3) Type the following commands at the server console: unload snmplog unload trapmon unload zeninv 4) Press Alt-Esc to display the database screen > press Q to quit. 5) Type the following command at the server console: unload dbextf6 6) Edit the AUTOEXEC.NCF file and remove the following lines. SEARCH ADD SYS:\PUBLIC\ZENWORKS\JAVA LOAD JAVA.NLM SYS:\SYSTEM\JVORBCFG.NCF LOAD ORBCMD.NLM LOAD OSAGENT.NLM SYS:\PUBLIC\ZENWORKS\JAVA\ALARMMGR.NCF SYS:\SYSTEM\GATHERER.NCF SYS:\PUBLIC\ZENWORKS\JAVA\MASTER.NCF SYS:\PUBLIC\ZENWORKS\JAVA\STORER.NCF SEARCH ADD VOL2:\ZENWORKS\DATABASE VOL2:\ZENWORKS\DATABASE\SYBASE.NCF These lines are added to AUTOEXEC.NCF when you reinstall ZENworks 2. 7) Reinstall ZENworks 2. Procedure B: Edit AUTOEXEC.NCF, then restart server. 1) At the server console, edit the AUTOEXEC.NCF file and remove the following lines. SEARCH ADD SYS:\PUBLIC\ZENWORKS\JAVA LOAD JAVA.NLM SYS:\SYSTEM\JVORBCFG.NCF LOAD ORBCMD.NLM LOAD OSAGENT.NLM SYS:\PUBLIC\ZENWORKS\JAVA\ALARMMGR.NCF SYS:\SYSTEM\GATHERER.NCF SYS:\PUBLIC\ZENWORKS\JAVA\MASTER.NCF SYS:\PUBLIC\ZENWORKS\JAVA\STORER.NCF SEARCH ADD VOL2:\ZENWORKS\DATABASE VOL2:\ZENWORKS\DATABASE\SYBASE.NCF These lines are added to AUTOEXEC.NCF when you reinstall ZENworks 2. 2) Save the changes to the AUTOEXEC.NCF file. 3) Type "restart server" on the console command line. 4) When the server has restarted, reinstall ZENworks 2. 1.5 NDS for NT Server System Requirements If you will be installing ZENworks on an NT Server whose NT domains are managed by NDS for NT, the server should meet the following minimum requirements: - Windows NT Server 4.0 with Service Pack 1, 3, 4, or 5. The NT server must be running on an NT file system (NTFS) in order to create a replica. - 64 MB RAM. - 175 MB of available disk space. - Administrative rights to the container where you install ZENworks. - Administrative rights to the NT server and to all portions of the NDS tree that will contain User objects that are domain-enabled. - Administrative rights to the root of the NDS tree to extend the schema. 1.5.1 Known Issues Regarding ZENworks and NDS for NT 1.5.1.1 When installing ZENworks in directory trees containing NDS for NT local replicas, be sure to wait until the ZENworks schema extensions have synchronized completely before starting any NDS partition operations involving the replicas. Preferably, you should perform the partition operations prior to the installation of ZENworks. 1.5.1.2 If you see the following mapping error when installing ZENworks to the NT server, map a drive to "SYS" share on the NT server and then rerun the ZENworks installation program. "Setup was unable to allocate a drive to use for transferring files. Please verify that you are using an authenticated connection, and there is a drive available. The installation will now exit." To map a drive, use the GUI utility or the NET USE command. For example, type NET USE * \\NTSERVER-NT\SYS 1.5.1.3 During the installation of Check 2000 software on an NDS for NT server, you will see the following error if you are installing to a mapped drive: Could not set DS tree name to UnknownTree. Installation on \:\\SYS\PUBLIC\ failed. To be able to install Check 2000, use a UNC path to the "Share" folder on the NT server instead of a mapped drive. For example, \\\SYS\PUBLIC\ 1.6 Additional Memory Requirements for Running the Sybase Inventory Database If you plan to run the Sybase Inventory database, follow the minimum memory requirements listed in the Installation and Upgrade Guide. For information about calculating a general formula for specific memory requirements, see the Inventory Deployment Guide at the ZENworks documentation web site at www.novell.com/documentation/lg/zen2/docui/index.html Look for the section called "Using an Optimal Database Cache Size on the Inventory Database Server to Improve Performance." 2.0 NetWare Administrator 2.1 Invoking NetWare Administrator on an IPX-only Workstation After you install ZENworks, if you invoke NetWare Administrator from a workstation that is not configured for IP, the following ZENworks components will not work: - Ping Remote Management Agent - File Transfer - Remote Execute - Chat - Remote Diagnostics - Inventory Summary - Inventory Query - Edit Software List Editor (Software List Editor) - Software Scan Policy 2.2 Using ZENworks NetWare Administrator 32 ZENworks supports NetWare Administrator 95 and NetWare Administrator NT. However, to take full advantage of the new features included in ZENworks, you should use NetWare Administrator 32, which ships with ZENworks. ZENworks 2 does not support ConsoleOne. 2.2.1 Policy Objects May Appear in NetWare Administrator 32 If you run NetWare Administrator 95 or NetWare Administrator NT, save settings, and then run NetWare Administrator 32, you will see all the Policy objects in the browser window. To hide the Policy objects in NetWare Administrator 32, you can close all browser windows and open new browser windows, or you can remove the registry key for NetWare Administrator: HKEY_CURRENT_USER\Software\NetWare\Parameters\NetWare Administrator You can also hide Policy objects in NetWare Administrator 95, NetWare Administrator NT, and NetWare Administrator 32 if you use the View-Sort and Include dialog box to remove individual policies from the current browser window and save your settings. 2.2.2 Running Snap-In DLLs Using NetWare Administrator 32 NetWare Administrator 32 has support for old snap-in DLLs (those compiled with SNAPIN95.LIB or SNAPINNT.LIB) as well as new Snap-in DLLs (those compiled with SNAPIN32.LIB). NetWare Administrator 32 includes the following shim DLLs in the SYS:PUBLIC\WIN32 directory that support the old snap-ins: - NWCORE95.DLL - NWCOMN95.DLL - NWVCTL95.DLL - NWCORENT.DLL - NWCOMNNT.DLL - NWVCTLNT.DLL These DLLs make calls into the corresponding NetWare Administrator 32 DLLs (NWCORE32.DLL, NWCOMN32.DLL, and NWVCTL32.DLL). To run a snap-in DLL that has been installed with NetWare Administrator 95 or NetWare Administrator NT, copy the snap-in DLL to the SYS:PUBLIC\WIN32\SNAPINS directory and any supporting DLLs to the SYS:PUBLIC\WIN32 directory. The snap-in directory is different if the snap-in runs only under Windows NT (SYS:PUBLIC\WIN32\SNAPINS\NTONLY) or Windows 95 (SYS:PUBLIC\WIN32\SNAPINS\95ONLY). You can get a list of the current snap-in DLLs by viewing two registry keys under the NetWare Administrator key: HKEY_CURRENT_USER\Software\NetWare\Parameters\NetWare Administrator For NetWare Administrator 95: - Snap-in Object DLLs WIN95 - Snap-in View DLLs WIN95 For NetWare Administrator NT: - Snap-in Object DLLs WINNT - Snap-in View DLLs WINNT If the snap-in DLL loads resource DLLs or help files relative to NetWare Administrator (using NWAGetNLSFilePath), copy the resource DLLs and help files relative to the SYS:PUBLIC\WIN32 directory. If the snap-in DLL loads resource DLLs or help files relative to the snap-in DLL, copy the resource DLLs and help files relative to the SYS:PUBLIC\WIN32\SNAPINS directory. Contact your vendor for a list of files and for the latest version of the snap-in DLL. 2.2.3 Running Numerous Snap-Ins with NetWare Administrator 32 If you have configured the registry for numerous snap-ins to load for NetWare Administrator 95 or NetWare Administrator NT, adding the ZENworks snap-ins will cause the NetWare Administrator process to run out of Thread Local Storage handles. Windows 95 and Windows NT allocate 64 handles for the NetWare Administrator 95 or NetWare Administrator NT process. NetWare Administrator requires 17 handles. Each Snap-in DLL can require from zero to four or more Thread Local Storage handles. The ZENworks snap-ins require four handles in all. If other snap-ins don't load or crash after adding the ZENworks snap-ins, you have likely exceeded the 64-handle limit on your workstation. Novell snap-ins that consume multiple handles will be fixed in future releases. In the meantime, you can remove unnecessary snap-ins from the registry so that your necessary snap-ins will load. The NetWare Administrator snap-in registry keys are: For NetWare Administrator 95 HKEY_CURRENT_USER\Software\NetWare\Parameters\NetWare Administrator\Snapin Object DLLs WIN95 For NetWare Administrator NT HKEY_CURRENT_USER\Software\NetWare\Parameters\NetWare Administrator\Snapin Object DLLs WINNT 2.2.4 Using NetWare Administrator 32 with the NetWare 5 Client Creating the Workstation Manager Client Configuration (WMCC) in NetWare Administrator 32 requires that the Novell Client for Windows 95 (v2.5 or higher) or Windows NT (v4.3 or higher) be installed on the workstation being used to create the policy. The snap-in depends on accessibility to the GUI Login Active-X controls to configure the WMCC policy for login settings. 2.2.5 Using ZENworks on a Non-English Server Running ZENworks 2 on a server with a non-English OS could cause DLL version mismatch errors. These errors may occur if the version of NWADMN32.EXE you are running does not match the language-specific DLLs located on the server. To correct the problem, copy the NWADMR32.DLL and NWADLG32.DLL resource DLLs from \PRODUCTS\ZENWORKS\PUBLIC\WIN32\NLS\ on the ZENworks CD to \SYS:\PUBLIC\WIN32\ on the server. 2.3 Using NetWare Administrator 95 or NetWare Administrator NT ZENworks requires that the DMPOLICY.DLL snap-in is the first ZENworks snap-in to be loaded by NetWare Administrator 95 or NetWare Administrator NT (this does not apply if you are using NetWare Administrator 32). In some instances, NetWare Administrator 95 and NetWare Administrator NT do not read these DLLs out of the Registry in order. In these scenarios, the DMPOLICY.DLL snap-in detects the problem and displays a warning message recommending that you fix the problem. Note that NetWare Administrator 95 and NetWare Administrator NT are not available with NetWare 5. When DMPOLICY.DLL is not the first ZENworks DLL loaded, NetWare Administrator 95 and NetWare Administrator NT might have problems, such as not being able to delete, move, or rename Workstation objects. In addition, certain Policy objects might display in the Create Object dialog box, but you can't create them there. The solution to this problem is to remove all ZENworks snap-ins from the snap-in object registry for NetWare Administrator and then re-enter them so that they are loaded in the correct order. This process is simplified by a .REG file, which is installed to the SYS:\PUBLIC\WIN95 and SYS:\PUBLIC\WINNT server directories during ZENworks installation. The file lists all registry keys needed for the ZENworks snap-ins to work. Depending on your version of ZENworks, this .REG file might be named ZENSTART.REG or ZENFULL.REG. To fix the problem 1) Open the .REG file (either ZENSTART.REG or ZENFULL.REG) in Notepad or another ASCII text editor. 2) Open Regedit and manually delete the keys found in the .REG file. 3) Run Regedit ZENSTART.REG or Regedit ZENFULL.REG to reload the registry. 2.4 Authenticating to a New NDS Tree Using NetWare Administrator 95 or NetWare Administrator NT When running on the ZENworks Client, NetWare Administrator 95 and NetWare Administrator NT might be unable to launch the NetWare Login dialog box when you try to browse to a tree to which you are not currently authenticated. However, you can task-switch to Windows Explorer, browse to the Network Neighborhood, and authenticate to the new tree without shutting down NetWare Administrator NT or NetWare Administrator 95. When you return to NetWare Administrator NT or NetWare Administrator 95, you should be able to browse to the new tree. This problem does not occur with NetWare Administrator 32. 2.5 Using FastCache and BorderManager Snap-Ins FastCache and BorderManager currently require NetWare Administrator NT in order to install the NT snap-ins for these products. NetWare Administrator NT does not ship with ZENworks. If you don't have this file and you want to install one of these snap-ins, download it from the following address: www.novell.com/download 2.6 User Profiles Snap-In In the User Profiles snap-in in NetWare Administrator 32, when you choose desktop preferences/display options and browse to a filename for either the screen saver or wallpaper, the snap-in converts your local drive mappings to a UNC mapping. When you type a path, make sure the mapping corresponds to the correct UNC path on the local machine making the changes, not to the user's workstation. The program uses the current workstation mappings for the conversion. 3.0 Application Management 3.1 General Known Problems and Limitations 3.1.1 Creating Application Objects with NetWare Administrator for Windows 95 If NetWare Administrator for Windows 95 does not allow you to create Application objects, verify that ZENAPP32.DLL, APPSNP95.DLL, SNAPIN32.DLL are located in the same directory as NWADMN95.EXE and that APPRES32.DLL, APPSNAP.HLP, and APPSNAP.CNT are in the NLS\(LANGUAGE) directory. Also make sure that the dates of the files are the same as those shipped with the product. Make sure that the registry key for Application Launcher Snap-In is set to either the hex or string value of "APPSNP95.DLL," but not to both. HKEY_CURRENT_USER\Software\NetWare\Parameters\NetWare Administrator\Snapin Object DLLs WIN95 VALUE: APPSNP95.DLL = "APPSNP95.DLL" or VALUE: APPSNP95.DLL = 41 50 50 53 4E 50 39 35 2E 44 4C 4C 3.1.2 Creating Application Objects with NetWare Administrator for Windows NT If NetWare Administrator for Windows NT does not allow you to create Application objects, verify ZENAPP32.DLL and that APPSNPNT.DLL are located in the same directory as NWADMNNT.EXE. You should also veryify that APPRES32.DLL, APPSNAP.HLP, ZENWORKS.HLP, and ZENWORKS.CNT are in the NLS\ directory. Make sure that the dates of the files are the same as those shipped with the product. Make sure that the registry key for Application Launcher snap-in is set to either the hex or string value of "APPSNPNT.DLL," but not to both. HKEY_CURRENT_USER\Software\NetWare\Parameters\NetWare Administrator\Snapin Object DLLs WINNT VALUE: APPSNPNT.DLL = "APPSNPNT.DLL" or VALUE: APPSNPNT.DLL = 41 50 50 53 4E 50 4E 54 2E 44 4C 4C 3.1.3 Using the Timed Refresh Setting Use caution when specifying the timed refresh setting. Frequent refreshes of large numbers of users can adversely impact network traffic. The default setting for timed refresh is Off. 3.1.4 Windows 3.1 and UNC In Windows 3.1, Application Launcher does not support UNC paths in the distribution part of an Application object (for example, path to a file to be copied) that has a server name greater than 11 characters or a volume name greater than eight characters. Use a drive letter path in place of the UNC path or upgrade to Windows for Workgroups 3.11. 3.1.5 An Application Object in Tree 1 Cannot Capture a Printer Port to a Server in Tree 2 Defining printer port captures within an application object must be restricted to servers within the tree in which the Application object is defined. 3.2 Application Launcher 3.0 Application Launcher 3.0 is a collection of primarily 32-bit applications. It will not work on a 16-bit platform (that is, Windows 3.1). The NALW31.EXE and accompanying files shipping with Application Launcher 3.0 are the same as those shipped with version 2.7. 3.2.1 Application Launcher Files Installed with the NT Client As part of the NT Client install, you can install the Application Launcher NT Service. If this component is installed to the workstation, the following files that are copied (assume Windows NT is located in C:\WINNT): - C:\WINNT\SYSTEM32\NALNTSRV.EXE (Application Launcher NT Service) - C:\WINNT\SYSTEM32\ZENAPP32.DLL (32-bit Application Launcher library) - C:\WINNT\SYSTEM32\NALSRVLD.EXE (Load/Unload for NT Client) - C:\WINNT\SYSTEM32\NLS\ENGLISH\NALNTRES.DLL (App Launcher NT Service resource) If you plan to continue using Application Launcher 2.0 or Application Launcher 2.01, Novell recommends that you do not install Application Launcher NT Service as part of the NT Client install. 3.2.2 Application Launcher 2.01 and Earlier Files That Can Be Removed after Installation - SYS:PUBLIC\NALW95.EXE (NALWIN32.EXE is now used) - SYS:PUBLIC\NLS\ENGLISH\APPRES3X.DLL (APPRES16.DLL is now used) - SYS:PUBLIC\NLS\ENGLISH\APPSNAP.CNT (ZENWORKS.CNT is now used) - SYS:PUBLIC\SNAPSHOT\NLS\ENGLISH\DVJRES16.DLL (This file has been changed to SNPRES16.DLL) - SYS:PUBLIC\SNAPSHOT\NLS\ENGLISH\DVJRES32.DLL (This file has been changed to SNPRES32.DLL) - SYS:PUBLIC\SNAPSHOT\NLS\ENGLISH\SNAPSHOT.CNT (APPSNAP.CNT is now used) - SYS:PUBLIC\SNAPSHOT\NLS\ENGLISH\SNAPSHOT.HLP (APPSNAP.HLP is now used) The following subdirectories contained the client login files for Application Launcher to update the user's workstation. Application Launcher 3.0 no longer updates client login files. - SYS:PUBLIC\NALLIB\WIN31 - SYS:PUBLIC\NALLIB\WIN95 - SYS:PUBLIC\NALLIB\WINNT 3.3 Application Launcher Snap-Ins If the version of MSVCRT.DLL in the Windows System directory (that is, the C:\WINDOWS\SYSTEM on Windows 95/98 or C:\WINNT\SYSTEM32 for Windows NT), is not at least version 6.0, the Application Launcher snap-ins (APPSNP32.DLL and APPSNPEX.DLL) may fail to load when NetWare Administrator runs. The snap-ins are dependent on MSVCRT.DLL version 6.0 or higher. If you installed the Novell Clients that ship with ZENworks 2, the Client install program adds MSVCRT.DLL (version 6.00.8337.0; 1/5/1999) to the files copied. To check the version of MSVCRT.DLL you have installed 1) From the Windows System directory, right-click MSCVRT.DLL. 2) Click Properties > Version. If you chose not to upgrade the clients during the ZENworks 2 install, you can use any of the following options to update a MSVCRT.DLL already in use: Option 1: Install the Novell Client that ships with ZENworks. Client installs are augmented with version 6.0 of MSVCRT.DLL. Option 2: Run NAL.EXE or NALEXPLD.EXE from SYS:\PUBLIC to check and update files on the local drive as needed (including MSVCRT.DLL from SYS:\PUBLIC\WIN32). If MSVCRT.DLL is updated, you will be prompted to restart Windows. Note that you may optionally include the /i command line option when you run NAL.EXE or NALEXPLD.EXE. This does not launch the Application Launcher window, but it will update files on the local drive. Option 3: This option is less desirable because of the increased chance of making mistakes. 1) Copy MSVCRT.DLL from SYS:\PUBLIC\WIN32 to a temporary directory on the local drive. 2) Exit Windows to a DOS prompt. 3) Copy MSVCRT.DLL from the temporary location to the Windows System directory. 3.4 Application Explorer 3.4.1 Duplicate Icons in the System Tray If more than one icon for the same application displays in the system tray, two NALDESK.EXE programs may be running. Check the Startup folder, registry, login scripts, and policies for multiple loads. 3.4.2 Creating Application Explorer Desktop Icon for Users Connected to Windows NT Terminal Server or Citrix If you run ZENworks on a Windows Terminal Server or Citrix, users connected to this type of server will not have an Application Explorer icon on their desktops unless you manually create and distribute it. Use the Create Applications Wizard to create a simple Application object, pointing to the Application Explorer executable at \\\SYS\PUBLIC\NAL.EXE. Assign a name and icon to this object and associate it with the desktop of the User, Workstation, Group, Organization, Organizational Unit, or Country object that need will to use it. When the associated users reboot their workstations, the icon representing NAL.EXE is displayed on their desktops. When double-clicked, this icon launches the Application Launcher and users will have access to all of their distributed applications. 3.5 snAppShot 3.5.1 DOS Shortcuts (PIF) snAppShot does not correctly discover shortcuts to DOS executable files; they are discovered as new files. 3.5.2 Drive Mappings The location where snAppShot places the .FIL files defaults to a drive letter. After you import the Template (.AOT) file into an Application object, go to the Macros page and change the SOURCE_PATH to a UNC path. For example, G:\PUBLIC\AOT\NETSCAPE changes to \\\SYS\PUBLIC\AOT\NETSCAPE This allows users to run the program without mapping to a drive. 3.5.3 Rights to Destination Directory When you run snAppShot, make sure you have rights to the destination directory or to directories you specify for the .AOT file and .FIL files. (You enter these in the fields labeled "Application files(s) location" and "Application object template (.AOT) filename and location.") If you enter a path to which you do not have rights, snAppShot will not create valid "snapshots." 3.5.4 GroupWise Client (32-Bit) snAppShot may encounter a conflict when running at the same time as the GroupWise Client (32-bit) installation. If you encounter this problem, cancel snAppShot after the first picture of the workstation has been taken and before you install the GroupWise Client. Because the first picture is stored in files, cancelling snAppShot will work. After you install the GroupWise Client, you can restart snAppShot and it will start again where it ended. 3.6 SNMPLOG File Size in Alarm Manager You must turn off the SNMPLOG logging function to prevent the SNMPLOG file from increasing in size so much that it will fill up your server volume. To turn off the function, add the following line to the ALARMMGR.NCF file after SNMPLOG: Set SNMP Trap Logging = OFF 4.0 Workstation Management 4.1 Workstation Inventory 4.1.1 The Sybase Inventory Database 4.1.1.1 Where to Locate the Inventory Database File Use the following guidelines when determining where to install the Sybase Inventory Database: - Accessing the ZENworks Inventory Database (an ODBC-compliant Sybase database) residing on an NFS mounted file system (such as Linux) using the NFS gateway causes a server abend. - If the ZENINV.DB database file resides on a server other than the server where the database engine is running, Sybase allows the database engine to run. Sybase also allows temporary maintenance on the database in stand-alone mode without any intervention. In this situation, it is important to make sure you have a valid backup of ZENINV.DB. - Sybase Inc. does not support installing the database engine on a server other than the one where the ZENINV.DB database file resides. Database recoverability is unreliable in such a situation and cannot be guaranteed. Sybase Inc. does not support file maintenance across a network file link because it does not provide strong Input/Output ordering semantics. - If ZENINV.DB resides on a non-NetWare file system (for example, NFS), the database server cannot use direct Input/Output. Making direct Input/Output calls to a network mapped file (using NFS Gateway on a NetWare 5 server) may cause an abend. To prevent the Inventory database engine from attempting direct Input/Output to an unrecognizable file system, start the database server with the -d switch. - Do not install the Sybase database on a NetWare server with multiple processors (for example, a NetWare 4.11 server with SMP). This will cause the server to abend when the Sybase NLM loads. - Novell recommends you locate the Inventory Database on a disk that is on the same physical server as the database engine or server accessing it. 4.1.1.2 Shutting Down Sybase with Active Inventory Connections If the Inventory Summary window or the Inventory Query window is open, do not shut down the Sybase database on the Inventory Database Server until you have exited all inventory applications from the console(s). If there are still active connections to the Sybase server, the following message displays when you type Q to quit: There are still active connections. Really quit? Y/N Type N if the message is displayed. If it is not displayed, the Sybase server has shut down safely. 4.1.1.3 If Sybase Shuts Down While Users are Connected If the Sybase database shuts down while users are connected to the database, the TCP port may stop working. To correct this condition, you can restart the server or you can use the following procedure: 1) Load tcpcon. 2) Go to the Protocol Information subscreen. 3) Select TCP. 4) Select View or modify TCP connections. 5) From the list of connections > look for port 2638 on local host connections > select each local host connection with port 2638 > press DEL to reset the connection. 6) Restart Sybase. 4.1.2 Filenames The application filenames that you specify in the Software Editor and the Software Scan Policy window on Windows 95 and Windows 98 managed workstations should follow DOS filename and extension (8.3) conventions. Long filenames are not supported. 4.1.3 Workstation Inventory Window Scroll bars are not displayed on resizing the Workstation Inventory window. To display the scroll bars again in the window, do one of the following: - Click any of the components in the window - Drag the bottom edge of the window to increase the size of the window - Drag the middle vertical pane in the window toward the right or left pane 4.1.4 Inventory Query If you are querying a large database for attributes such as Driver Name, Operating System Name, or Application Name, use the "matches" operator when you form the query. If you use the "equal to" and "not equal to" operators it may take time to display the values of the selected attributes before the formed query is executed. 4.1.5 Inventory Scan Program 4.1.5.1 The scan program does not report CD-ROM manufacturer information on Windows NT managed workstations. The program will also not scan some less-critical information, such as Model Number. 4.1.5.2 The scan program does not report keyboard typematic rate and delay on Dell computers. 4.1.5.3 The scan program does not scan a disk drive on Windows NT workstations if a disk is not inserted in the drive. 4.1.5.4 If you click Maximize while running the scan program on a managed workstation, the window will be blank. 4.1.5.5 BIOS Model information is not reported on Windows NT managed workstations. 4.1.6 Software List Editor 4.1.6.1 You can open multiple Software List Editor windows, but the only changes saved are those you specify in the window you open last. 4.1.6.2 In the Software List Editor, if you specify application entries that exist in the Software Description file (LDAPPL.INI), the scan programs will scan again for the application. Avoid duplication of application entries and new applications with blank entries. 4.1.7 Configuring an Inventory Policy on NetWare 4.11 If you are running ZENworks on a NetWare 4.11 server and you configure an Inventory Policy to use the Server DN or an IP Address to access the Inventory and Database servers, NDS Support Pack 6.04 must also be installed. This version of the Support Pack corrects a DS problem that deletes the IP address from the Server object. If you set up the Inventory server and the Database server to use the IP address or DNS name in the Inventory Policy, you do not need to upgrade to version 6.04. 4.1.8 Using the Run Now Button to Manually Run the Inventory Policy Because Workstation Inventory is designed to run only once during a scheduled period (as configured in the Inventory Policy), clicking the Run Now button in the Workstation Manager Scheduler will not manually run the Inventory Policy if the following conditions exist: - The current workstation time is within the period when the Inventory Policy is scheduled to run. - Workstation Inventory has already run during the period defined. 4.2 User Policy Package 4.2.1 Getting the Correct Paper Size When Distributing Printers When distributing a printer with a User Policy Package, the printer may prompt to insert Letter paper size although all printer settings at the workstation refer to A4. This occurs when the Regional Settings of the workstation and the user are not set properly. To correct the setting if your location is Germany, Denmark, Sweden, or another European country, click the Start menu > Settings > Control Panel > double-click Regional Settings > make sure the paper size defaults are set to A4 > make sure the Regional Settings of the users match your country. When the Regional Settings is set to US, the paper size setting will default to Letter. 4.2.2 Troubleshooting the Windows 95 User Policy Package In the 95 Desktop Preferences Policy, if you configure a Serial Key Device in Accessibility Options but do not have a physical device connected to your computer, you may receive a general fault protection error in Windows 95/98 the next time you restart the workstation. 4.3 NT User System Printer Policy If you set up the NT User System printer policy and then log in to an NT workstation as a user who is set up to use that Policy Package, you may receive a Dr. Watson error message pointing to WMRUNDLL.EXE. This is a Windows NT problem that will be fixed in Support Pack 5. To work around the problem, select a default printer in the Policy. 4.4 RAS Configuration Policy A Windows 95 RAS policy can be safely edited only from a Windows 95 or Windows 98 workstation. A Windows NT RAS policy can be safely edited only from a Windows NT workstation. 5.0 Remote Management 5.1 Remote Management Agent Before you begin to install the ZENworks Remote Management Agent, ensure that you have uninstalled any other Remote Control or Remote Management product from the managed workstation. 5.2 Improving Performance on Window NT Workstations Running 256 Colors or Less You may choose to install the optional Remote Management performance enhancement driver if your Windows NT workstations run in a color mode using 256 colors or less. This performance enhancement driver can be installed by using the "RemoteNT - ZEN 2" Application Object created by the ZENworks 2 installation program. The performance enhancement driver is not installed by installing the Remote Management Agent with the NetWare Client. Note that certain video cards, such as STB PowerGraph, are incompatible with the performance enhancement driver and may cause Windows NT to crash. Using the Application object to install the driver detects the video cards with conflicts and skips the installation of the performance enhancement driver when they are detected. If, after installation, you determine that the performance enhancement driver conflicts with your video driver, you can rename the file to disable it. You will find the driver, DRISHTI.DLL, in the C:\WINNT\SYSTEM32 folder. 5.3 Screen Savers A remote management session may be terminated if the screen saver activates on the workstation being remotely accessed. Some Windows 95 configurations may cause the Console window to paint incorrectly. Also, during a Remote session, if a 3-D screen saver activates on the managed workstation, the Console window may display a blank screen. 5.4 Windows NT System Requirements You must apply the Windows NT 4.0 Service Pack 3 (or higher) to the Windows NT managed workstation on which the RemoteNT Application object is installed. 5.5 Remote Control Performance over a WAN Performance during a Remote Control session is likely to be slow over a WAN, depending on the network traffic. 5.6 CPU Utilization Utilization on Windows NT is significantly low for the 256-color setting. For higher color settings, utilization is high. During a Remote Control session, the utilization of a Remote32 Application object on Windows 95 or Windows 98 managed workstations will be high. Using the Force 16 Color control option on the Console is likely to increase utilization on the managed workstation. However, selecting this option would improve performance over a slow link (such as a WAN). 5.7 Remote Control with a Full-Screen DOS Box If the managed workstation has a full-screen DOS box window open, you will not be able to remotely control it using the Remote32 and RemoteNT Application objects. 5.8 Security Authentication and security checking is done only when a Remote Management session is initiated. If a new user logs in at the managed workstation during a remote session, the remote session is not terminated. 5.9 Automated Time-Out Unlike ZENworks 1.1, which stored time-out values as static registry key values during a Remote Control session, ZENworks 2 automatically adjusts the time-out values based on network behavior. 5.10 Dial-Up Connections Remote Management utilities are not supported over dial- up connections. 5.11 File Transfer 5.11.1 File Transfer Options Not Available The following file transfer options are not supported: - Opening a file with its associated program - Deleting a folder with a file in it - Copying a folder (only file copy is supported) - Accessing network drives, CD drives, or disk drives. 5.11.2 Scroll Bar Display Scroll bars are not displayed on resizing the File Transfer window. To display the scroll bars again in the window, do one of the following: - Click any of the components in the window - Drag the bottom edge of the window to increase the size of the window - Drag the middle vertical pane in the window toward the right or left pane 6.0 ZENworks Reporting and Database Backup 6.1 Reporting Screen The ZENworks reporting screen will not display the scroll bar or page numbering if the display is set to 640 X 480. The screen requires a screen resolution setting of at least 800 X 600. 6.2 Generating Lengthy Inventory Reports If your workstation does not have sufficient memory to generate lengthy inventory reports, you may receive Out of Memory errors. This may also be manifested as an apparent freeze of the report viewer. The size of the report you can generate depends upon the amount of memory available on your workstation. This problem is less likely to occur if you generate reports of a useable size. Reporting tests at Novell have generated a 6,000 page report using a workstation with 128 MB of RAM. Inventory reports may be limited in size by specifying the fully-distinguished name of a workstation object to be reported on. Wildcards may be used to specify multiple workstation objects. 6.3 Database Backup If, while backing up the ZENworks database, you receive messages indicating that the server volume where the backup is targeted is out of disk space, you should assume the backup was not successful, even though NetWare Administrator generated no error messages. The backup saves a partial database file at the target location that you should delete. To continue the backup in this situation, save the data to a different volume location or free up sufficient disk space on the current volume to allow the backup to complete. 7.0 Novell Client 7.1 Using an Outdated Novell Client for Windows NT In NetWare Administrator, after you create a Policy Package object and modify a policy on the Policies page, you can use the Reset button on the Policies page to reset the selected policy to the default settings. After clicking Reset, if you receive a -601 error ("Object not found"), you are probably running an old version of the Novell Client for Windows NT. To resolve this, update your client to the one that ships with ZENworks 2. Similarly, after you add a scheduled action to a Policy Package, if you receive an "Object not found" error, you are probably running an old version of the Novell Client for Windows NT. To resolve this, update your client to the one that ships with ZENworks 2. 7.2 The Primary Network Logon Must be the Novell Client Desktop preferences and user system policies are only processed when the primary network logon is the Novell Client. 7.3 Upgrading the Novell Client without a Full Install If you have previously installed the WIN95 version 3.1 or WINNT version 4.6 clients and you want to upgrade to the ZENworks 2 clients without having to run through a full client install, run SETUPSP.EXE found in the \PRODUCTS\WIN95 directory or the \PRODUCTS\WINNT directory. This program installs the Client Service Pack 1 for the WIN95 version 3.1 or WINNT version 4.6 clients. 7.4 Running WM3X.EXE (the DOS/Windows Client) using Windows 3.x The DOS/Windows Client, WM3X.EXE, is intended to run at the end of STARTNET.BAT (or before Windows 3.x loads). Running WM3X.EXE after Windows is loaded (from a DOS box) could result in a general fault protection error. 8.0 Interoperability 8.1 Using ZENworks with Third-Party Remote Control Software Do not install or use the ZENworks Remote Management components on the same computer with remote control products developed outside Novell. 8.2 Using ZENworks with ManageWise 2.6 8.2.1 ZENworks Features Available in ManageWise Only the Remote Control feature of ZENworks 2 is available from the ManageWise Console. You can use the Remote Management Agent to implement it. 8.2.2 Implementing Remote Control from ManageWise If you choose to install the Remote Management Agent on a Windows NT managed workstation while installing the Novell Client for Windows NT, the Remote Management Agent will not be interoperable with the ManageWise Console. Use the Application Launcher to install the Remote Management Agent on a Windows NT managed workstation. This will enable the Remote Control feature of ZENworks from the ManageWise Console. 8.3 Using ZENworks with NDS for NT 2.0 ZENworks is not compatible with the Novell Windows NT 4.12 Client that is installed to the Domain Controller with NDS for NT 2.0. ZENworks requires a Novell Client for NT version 4.3 or greater. The current release of NDS for NT version 2.01 includes a Novell Client for the domain controller that is compatible with ZENworks. 8.4 Using ZENworks with McAfee VirusScan McAfee VirusScan, from Network Associates, Inc. (NAI) is bundled with ZENworks 2. This application monitors workstations running Windows 3.x, Windows 95, Windows 98, or Windows NT (version 4.03 or higher only). 8.5 Using the English Version of ZENworks on Double-Byte Machines You may experience certain errors if you use the English version of ZENworks on a double-byte enabled machine using the 1.1.5 Java Virtual Machine (JVM). A newer version of the JVM, version 1.1.7, helps to eliminate the double-byte errors. A self-extracting zip file, JVM117B.EXE, located in the \PRODUCTS\JVM folder of the ZENworks product CD, launches InstallShield and installs a new version of the JVM on your ZENworks server. Note that you should run this install after you install ZENworks; otherwise, certain parts of ZENworks will not perform correctly. 9.0 Y2K Readiness Novell has made a diligent effort to assure than ZENworks technology is Y2K ready. You should be aware, however, that one of the Windows 95 common control files used by ZENworks and shipped on the ZENworks 2 CD, COMCTL32.DLL, is not Y2K ready. Although Novell does not have the rights to redistribute an updated version of COMCTL32.DLL, Microsoft has released a Common Controls update (401COMUPD.EXE) to update the COMCTL32.DLL on your workstation. The update is available on the Microsoft web site at www.microsoft.com/msdownload/ieplatform/ie/comctrlx86.asp Follow the instructions at the web site to update the file. The following text is an excerpt from the Microsoft TechNet web site dedicated to Year 2000 issues. The text explains additional steps you should take to ensure Y2K readiness with COMCTL32.DLL: "When Regional Settings from Control Panel is set to use two digits for years, the Date/Time Picker function may not return the proper date. To ensure proper handling of dates, set Regional Settings to 4-digit date handling." The Microsoft TechNet web site can be accessed at www.microsoft.com/technet/year2k/product/user_view68383EN.htm 10.0 Product Documentation 10.1 Installation and Upgrade Guide This guide provides users with a quick solution for installing ZENworks 2 with some of its basic and most popular functionality. The audience for the guide is the network administrator who is performing an installation for the first time on a test system. The guide is printed and included in the product box and is also available in .PDF file format and is viewable from an Adobe Acrobat viewer. The .PDF file can be accessed during the ZENworks installation or by browsing the product CD. The Upgrade chapter provides information that administrators may be interested in when upgrading from an older version of ZENworks. 10.2 Online Help Help is available from the workstation or from the desktop for the administrator or a user whenever a Help button is accessible from a ZENworks, Novell Client, Help Requester, or Application Launcher interface. The help may be generated from Windows Help (32- or 16-bit help files) or from JavaHelp (reporting and inventory). Some critical tasks are also documented in online help. Other, more detailed, conceptual documentation can be found on the Internet. This information is referenced with active links from help that launch a web browser to access the contents page of that information. 10.2.1 Error When Clicking Help Button After the initial installation of ZENworks, Windows Help may fail to properly open a help file when you click a Help button on a ZENworks snap-in properties page. In this situation, you may see a Windows Help error similar to the following: "Unable to open the file \public\win32\nls\english\Zenworks.cnt" To correct the problem, browse to \PUBLIC\WIN32\NLS\ENGLISH with Windows Explorer and open ZENWORKS.HLP manually. After the file is opened initially, Help buttons in the NetWare Administrator should function normally. 10.3 Documentation on the Internet The most current ZENworks documentation is found at the ZENworks 2 documentation web site at www.novell.com/documentation/lg/zen2/docui/index.html This documentation is designed to include more detail and conceptual information about the product than does online help. 10.4 Other Product Information 10.4.1 ZENworks Cool Solutions You will find feature articles, questions and answers, tips of the week, links to specific Novell Support Technical Information Documents (TIDs) and more about ZENworks on the Internet at the ZENworks Cool Solutions web site maintained by the Novell Content & Community Web Group at www.novell.com/coolsolutions/zenworks The site is periodically updated with current product issues. It also provides a searchable archive that contains information for making the most of ZENworks. 10.4.2 Third-Party Tools Information Documentation for Check 2000 from Greenwich Mean Time and McAfee VirusScan from Network Associates is included on the ZENworks 2 product CD in PDF files. The files are viewable from an Adobe Acrobat viewer and can be accessed during the ZENworks installation or by browsing the product CD. 11.0 Legal Information 11.1 Disclaimer, Copyright, and Patents Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability, title, or fitness for a particular purpose. Distribution of any Novell software is forbidden without the express written consent of Novell, Inc. Further, Novell reserves the right to discontinue distribution of any Novell software. Novell is not responsible for lost profits or revenue, loss of use of the software, loss of data, costs of re-creating lost data, the cost of any substitute equipment or program, or claims by any party other than you. Novell strongly recommends that you make a backup before you install any software. Technical support for this software may be provided at the discretion of Novell. Copyright (C)1999 Novell, Inc. All rights reserved. U.S. Patent Nos. 5,349,642; 5,594,863; 5,633, 931; 5,692,129; 5,761,499; 5,781,733; 5,859,978. U.S. and Foreign Patents Pending. 11.2 Trademarks ManageWise, Novell, and NetWare are registered trademarks of Novell, Inc. in the United States and other countries. BorderManager, BorderManager FastCache, IPX, NDS, NetWare, Novell Client, and ZENworks are trademarks of Novell, Inc. All third-party trademarks are the property of their respective owners. ============================================================ README Addendum: ZENworks 2 International Release January 14, 2000 Software changes made to the ZENworks 2 Support Pack (English) are included in the ZENworks 2 international release. This README addendum lists the changes that you need to know if you have previously installed the ZENworks 2 (English) release. It also documents information about product issues that are not documented elsewhere. Information about enhancements or bug fixes to the ZENworks 2 (English) product are not included in this document. Table of Contents 1.0 Overview 1.1 Purpose of the Support Pack 1.2 Database Migration Enhancement 1.3 Fixes In the Support Pack 2.0 Migrating the Inventory Database 2.1 Migration Prerequisites 2.1.1 Exiting the Database Server Engine Before Migrating the Inventory Database 2.1.2 Removing Old ZENworks 2 Java Components Prior to Installing New Java Virtual Machine 2.2 Troubleshooting Database Migration 3.0 Purging Information from the Inventory Database 3.1 Configuring the Purge Process 3.2 Enabling Automatic Daily Purges 3.3 Forcing an Immediate Purge 3.4 If a Purge Doesn't Work or Items Reappear 3.5 If a Purge Takes Too Long 4.0 Scanning IBM Workstations in Hardware Inventory 5.0 Patch to Handle Logical NIC Cards for Inventory 5.1 Files Included in the NIC Card Patch 5.2 How to Install the NIC Card Patch 6.0 Distributing .INI Files 7.0 Remote Control File Transfer Enhancements 8.0 Sybase Sorting Fix 9.0 Reporting Enhancement 10.0 ManageWise 2.6 and ZENworks 2 Integration 11.0 Application Launcher Flashing Icons Fix 12.0 Remote Management Agent for Windows NT 13.0 Viewing Audit Log Information for Remote Management Sessions 14.0 Detailed List of Fixes in the Support Pack 14.1 Fixes Applied to the Application Launcher 14.2 Fixes Applied to the Application Explorer 14.3 Fixes Applied to the Application Library 14.4 Fixes Applied to snAppshot 14.5 Fixes Applied to Client Configuration 14.6 Fixes Applied to Hardware and Software Inventory 14.7 Fixes Applied to Remote Management 14.8 Fixes Applied to Workstation Management 14.9 Fixes Applied to Workstation Import 15.0 Legal Information 15.1 Disclaimer and Copyright 15.2 Trademarks 1.0 Overview 1.1 Purpose of the Support Pack The ZENworks 2 Support Pack consists of updated files and limited enhancements for the ZENworks 2 (full) product. It cannot be used to update Z.E.N.works 1.0, Z.E.N.works 1.1, or the ZENworks Starter Pack. 1.2 Database Migration Enhancement The ZENworks 2 Support Pack includes an optional migration of an existing ZENworks 2 Inventory data to a newer version of the Sybase database. Two migration options are presented during the Support Pack install: Migrate Existing Data ===================== If you want to migrate data from an existing ZENworks 2 database, you can expect the following results: 1) The install program automatically transitions to a data migration program. 2) Migration proceeds, lasting approximately 2 to 12 hours depending on the size of the database) and requiring approximately twice the disk space used by the current database in order to accommodate file swapping. 3) The migration program transitions back to the install program. 4) The install program continues. 5) Existing data is merged into a database that supports double-byte characters. Delete Existing Data ==================== If you want to delete the data from the existing ZENworks 2 database, you can expect the following results: 1) The existing inventory data is deleted. 2) The install program continues. 3) New inventory data must be gathered and stored in a database that supports double-byte characters. If you decide to migrate the database, you must exit the database server and remove old ZENworks 2 Java components from the server. You can find more detail about the database migration, including the prerequisites that must be met, in Section 2 of this document. 1.3 Fixes In the Support Pack The ZENworks 2 Support Pack includes many bug fixes that address ZENworks 2 problems, including: - Absence of logical NIC cards in inventory reports - Lack of ManageWise 2.6 and ZENworks 2 interoperability - Application Launcher flashing icons - Inability to sort double-byte strings in inventory reports - Inability to scan for some IBM workstations - Inability to purge the inventory database A more detailed list of bugs fixed in the Support Pack is listed in Section 14 of this document. 2.0 Migrating the Inventory Database The inventory database that shipped with ZENworks 2 uses the 850 Language Collating Sequence mechanism for storing characters, which does not support the storage and retrieval of internationalized information. The ZENworks 2 Support Pack install program can install a new database and migrate existing data from the older ZENworks 2 inventory database. The new database uses UCS Transformation Format (UTF-8) encoding for storing characters and retrieving internationalized information from the database. The install also updates the database server with Sybase Adaptive Server Anywhere version 6.0.3.2747. You should be aware of the following facts if you choose to migrate the existing database: - If you want to migrate your database, click the Migrate Existing Data option during the installation, If the database server does not have a DNS name, the install program reads NDS for an IP address. If this fails, you will be prompted to enter the IP address for the server. - The migration takes 2 to 12 hours, depending upon the size of the database. - If you close the DBUNLOAD window during the database migration, the migration process will abort and the database will be in an inconsistent state. - When the database migration is complete, the install program renames the old database to ZENINV.DB.OLD and starts the new database (ZENINV.DB). This process may take some time if the database is large (in the MB or GB range), leading to the false assumption that the installation is frozen. - If the new database fails to load at the end of the installation program, the migration process displays an error. If this happens, you must run the install program again and click the option to Migrate the Database. - The migration status is stored in the DBMIGRATE.LOG file in the ZENWORKS\DATABASE directory. - If the source database that is selected for migration is empty, the migration still continues and a new database server is installed. 2.1 Migration Prerequisites Prerequisites for migration are as follows: - Database server should not be loaded before starting the installation. - At least 32MB RAM is required on the database server for buffering during migration. - The user must have Read/Write rights for the ZENWORKS\DATABASE directory to run the migration process. 2.1.1 Exiting the Database Server Engine Before Migrating the Inventory Database Before you can invoke inventory database migration, you must stop the database server engine. To stop the engine 1) From the Database Server Console, select the Sybase Adaptive Server Anywhere screen. 2) Press Q. If there are active connection to the database, the following message is displayed: There are still active connections. Really quit (Y/N) 3) Press Y. You may also type UNLOADINVDB at the System Console to stop the database engine. Note that if you are using NetWare 5 with Support Pack 4, the "Press Q to quit" message may not be displayed. You can still stop the database engine by pressing Q followed by Y, or you can stop the engine with the UNLOADINVDB command at the System Console. This problem will be resolved in the next NetWare 5 Support Pack release. 2.1.2 Removing Old ZENworks 2 Java Components Prior to Installing New Java Virtual Machine If you install the ZENworks 2 Support Pack on a server, where ZENworks 2 Inventory database has previously been running, numerous Java or Sybase database errors will occur because of the components that are loaded and running on the server. Use the following procedure to unload these components and install the Support Pack successfully. 1) At the server console, edit the AUTOEXEC.NCF file and comment the following lines. SEARCH ADD SYS:\PUBLIC\ZENWORKS\JAVA LOAD JAVA.NLM SYS:\SYSTEM\JVORBCFG.NCF LOAD ORBCMD.NLM LOAD OSAGENT.NLM SYS:\PUBLIC\ZENWORKS\JAVA\ALARMMGR.NCF SEARCH ADD VOL2:\ZENWORKS\DATABASE SYS:\SYSTEM\GATHERER.NCF SYS:\PUBLIC\ZENWORKS\JAVA\MASTER.NCF SYS:\PUBLIC\ZENWORKS\JAVA\STORER.NCF Do not comment the following line: VOL2:\ZENWORKS\DATABASE\SYBASE.NCF Removing or commenting this line results in an incomplete install. 2) Save the changes to the AUTOEXEC.NCF file. 3) Type "restart server" on the console command line. 4) When the server has restarted, press Alt-Esc to display the database screen. 5) Press Q to quit the database. Java may still need to be unloaded if called by a prior process. Verify that Java is not loaded. If it is loaded, unload JAVA.NLM. 6) Install the Support Pack. 7) At the server console, edit the AUTOEXEC.NCF file and uncomment the previously commented lines. Note that the VOL2:ZENWORKS\DATABASE\SYBASE.NCF line has been replaced by SYS:\SYSTEM\MGMTDBS.NCF 8) Save the changes to the AUTOEXEC.NCF file. 9) Type "restart server" on the console command line. 2.2 Troubleshooting Database Migration The DBMIGRATE.LOG file stores the status of migration. The possible cause and explanation of messages in the log file are as follows: SQL ERROR CAUSE ========= ===== Primary key for table This error indicates that a 't$Action' is not migrated database already unique. exists. Database server not n/a running. Request to start/stop This error indicates that database denied. the database server is not running for the migration process to proceed. During the migration process, the database starts and stops automatically. Database unload This error indicates that interrupted by the the user interrupted the user. migration process by pressing CTRL+C in the DBUNLOAD Console window or by closing the DBUNLOAD Console window. Connection was This error indicates that terminated. during the migration process, the database engine was downed by the user. Template Database This error indicates that not found, Database the migration program cannot Migration procedure find the database directory. aborted. This error can be triggered if the migration creates a file named ZENINVNEW.DB or a file named ZENINV.DB.OLD on the server during the installation. Unable to resolve This error indicates that the the IP address of database server does not have the server . a DNS name. Enter the IP address of the server to correct the problem. 3.0 Purging Information from the Inventory Database ZENworks 2 provides an option to purge selected information from the inventory database. You can only purge information about application distributions and launches; you cannot purge hardware or software inventory information. You can select the information to be purged based on how old it is and how important it is. The purge software runs as a background process on the NetWare server that hosts the inventory database. It remains idle until a specified time of day when it wakes up and purges the information you have selected. The purge process is disabled by default. To enable it, you must edit certain configuration files and restart the Alarm Manager component of the inventory server. The configuration files specify the time of day the purge process wakes up and the criteria used to select the information to be purged. Once the purge process is set up, you can force it to run immediately at any time (outside its normal schedule) by issuing a command at the server console. An immediate purge uses the same criteria to select the information to be purged unless you explicitly direct it to a different configuration file. For details, see "Forcing an Immediate Purge" below. 3.1 Configuring the Purge Process 1) Using a text editor, create an AMPURGE.PROPERTY file in SYS:\PUBLIC\ZENWORKS\JAVA on the NetWare server that hosts the inventory database. 2) Copy and paste the following text into the file: PurgeStartTime=2 SeverityInformationalPurgeWait=7 SeverityMinorPurgeWait=7 SeverityMajorPurgeWait=7 SeverityCriticalPurgeWait=7 SeverityUnknownPurgeWait=7 3) Edit the contents of the file as follows: Set the PurgeStartTime to the daily hour when you want the purge process to run. Valid values are 0 to 23, where 0 is midnight and 23 is 11:00 p.m. For example, the above specifies 2:00 a.m. Important: The purge process is memory intensive and can occupy the server for several minutes if there are thousands of records to be purged, although normally there should only be one day's worth of records to purge. To be safe, we recommend that you set the start time to an hour when the server isn't being used heavily. If you run into problems, see "If a Purge Takes Too Long" below. Edit each of the SeverityXXXPurgeWait lines to specify the number of days old that the corresponding information needs to be before it is purged from the database. For example, the above specifies that only information older than seven days will be purged. In ZENworks 2, the five severity levels correspond to the following types of information in the database: Informational - Corresponds to successful application distributions, launches, or filters (hiding or showing of an application based on system requirements). Minor - (Not used in ZENworks 2) Major - (Not used in ZENworks 2) Critical - Corresponds to failed application distributions or launches. Unknown - (Not used in ZENworks 2) 4) Save any changes you have made to the file. After creating the AMPURGE.PROPERTY file, you can change the configuration settings in it at any time, but the changes won't take effect until you restart the Alarm Manager component of the inventory server as explained below. 3.2 Enabling Automatic Daily Purges Note: Before you enable automatic daily purges, you must create the AMPURGE.PROPERTY file as explained above. Otherwise, the purge software won't load. 1) Using a text editor, open the ALARMMANAGER.PROPERTY file in SYS:\PUBLIC\ZENWORKS\JAVA on the NetWare server that hosts the inventory database. 2) Add the following line to the bottom of the file: AlarmPurgeService=yes 3) Save and close the file. 4) Bring down the Alarm Manager software on the server as follows: At the system console, type JAVA -SHOW to see which Java processes are running. Note the ID numbers for the Alarm Manager processes. For each Alarm Manager process, type JAVA -KILLn, where n is the ID number of the process. 5) Restart the Alarm Manager software by typing SYS:\PUBLIC\ZENWORKS\JAVA\ALARMMGR at the system console. In a moment, on the Java interpreter console screen you should see some messages about the purge service starting up. This service will wait in an idle state until the scheduled automatic purge time. 3.3 Forcing an Immediate Purge Note: Before you can force an immediate purge, you must create an AMPURGE.PROPERTY file as explained above in "Configuring the Purge Process." Otherwise, the purge software won't load. To force an immediate purge, at the system console of the NetWare Server that hosts the inventory database, type the following (one line, with a space before "-s"): java com.novell.managewise.am.db.purge.AutoPurgeManager -s -d SYS:\PUBLIC\ZENWORKS\JAVA Notes: This command is case-sensitive because it is a Java command. You might want to put the command in an .NCF file if you need to run it frequently. The -s option specifies to start the purge process immediately. As soon as the purge is done, the process will exit. The -d option specifies the path to the AMPURGE.PROPERTY file that is to be used. The property file specifies which information is to be purged, as explained above in "Configuring the Purge Process." If you have created a different AMPURGE.PROPERTY file specifically for immediate purges (as opposed to automatic daily purges), make sure you change the path accordingly on the -d option. 3.4 If a Purge Doesn't Work or Items Reappear Possible Causes and Solutions: A. The purge software couldn't find its property file and so exited without doing anything. Make sure you create the property file with the correct name and location as explained above in "Configuring the Purge Process." If you are running an automatic daily purge, make sure you have added the purge service to the Alarm Manager configuration file as explained above in "Enabling Automatic Daily Purges." If you are running an immediate purge, make sure the -d option specifies the correct location for the property file as explained above in "Forcing an Immediate Purge." B. Java is down or is not configured correctly on the server that hosts the inventory database. At the server console, type JAVA -SHOW. If you get an "unknown command" message, Java is down. Type LOAD JAVA and then restart the inventory system as explained below. If you get a list of Java processes but none of them are related to Alarm Manager or Inventory Storer, then the Java environment has not been configured for the purge software. Restart the inventory system by entering the following commands: Vol:\ZENWORKS\DATABASE\SYBASE\GATHERER (Vol = location of inventory database) SYS:\PUBLIC\ZENWORKS\JAVA\MASTER SYS:\PUBLIC\ZENWORKS\JAVA\STORER SYS:\PUBLIC\ZENWORKS\JAVA\ALARMMGR C. Items that were purged can reappear in the inventory database if you restore an older copy of the database. Make sure you coordinate any backup/restore operations with your automatic daily purges so you don't end up restoring data that you don't want. D. None of the information in the inventory database meets the purge criteria specified in the property file. Make sure you have specified the purge criteria correctly as explained above in "Configuring the Purge Process." Keep in mind that only application distribution and launch information can be purged. The purge software cannot purge hardware or software inventory information, no matter how you configure it. 3.5 If a Purge Takes Too Long Possible Causes and Solutions: A. If you started using the inventory database months before you configured and enabled the purge service, the first time the purge process runs there may be a large number of records to purge. Make sure the initial purge runs at an off time when server usage is low. Once the initial purge has been completed, all subsequent automatic purges should never need to purge more than one day's worth of records. B. The server that hosts the purge software might not have enough memory. Increase the server memory or free up some memory by unloading unneeded software modules. 4.0 Scanning IBM Workstations in Hardware Inventory The ZENworks Inventory Scan Program (WINSCAN.EXE)utilizes information in the IBMNAMES.INI file (located in the SYS:\PUBLIC\ZENWORKS directory of the Inventory server) to help it recognize the workstation type and model number of IBM desktop and laptop workstations being scanned. This identifying information is in the [Product Names] section of the file. Entries in the section are formatted as follows: <4 Byte Machine Type>-<3 Byte Model Number>=Model Description For example, if the workstation model is IBM PC 140 and the 4 byte machine type is 6260, the entry in the IBMNAMES.INI file would be listed as 6260-79T=IBM PC 140 If you want to scan your network for newer IBM workstations whose identifying information is not currently included in IBMNAMES.INI, you must edit the file to add it; otherwise, these workstations will not be scanned. Note that if you don't already know a workstation's machine type and model number, you can find them on the underside of laptop models or on the back of desktop models. For example, the IBM Thinkpad 760E has the following label on its underside: TYPE 9546-A9B If you want to scan for all IBM workstations of a particular machine type with the same model description, you can add three wildcard characters (???) to the scan parameter so that the scan identifies all 3-byte model numbers of that machine type. For example, to scan for all the IBM models of the 6282 machine type, your scan entry would be formatted like this: 6282-???=IBM PC 300GL (6282) 5.0 Patch to Handle Logical NIC Cards for Inventory With the ZENworks 2 Support Pack, the inventory scan programs now scan for NIC cards. In addition, the Workstation Inventory window displays the NIC card information of the workstations (both physical and logical). The Inventory window that displays the minimal information stored in the NDS object is limited to displaying the information for no more than two NIC (physical) cards. To see additional NIC cards, click the More Inventory button. To see all NIC cards, click Hardware > Network Adapter. You can also query the Inventory database for NIC card information. To run the query, click Hardware > NIC Card on the Inventory Query screen. For more information on Hardware and Software Inventory, go to http://www.novell.com/documentation/lg/zen2/docui/index.html click Contents > under Workstation Management, click Workstation Inventory. 5.1 How to Install the NIC Card Patch 1) Disconnect all sessions of ZENworks 2 on the clients. You may close NWADMIN screens that have been opened previously for ZENworks 2. 2) Install the ZENworks Support Pack. 3) Reload the server modules necessary for inventory. 4) Scan the workstations again to update its inventory information in NDS and the inventory database. 5) Open NWADMIN > invoke Inventory (NDS and database) and Inventory query. 6.0 Distributing .INI Files Windows purposely sets a 64K size limitation on .INI files called by the standard Windows APIs. This limitation directly affects the distribution of .INI files in a ZENworks Application object, deleting data above the 64K limit. You can work around this limitation by letting the Application Launcher distribute the large .INI file instead of trying to generate a new .INI from scratch. Add the file to the Application Files tab (like any other file that is being distributed) and make any changes as necessary (such as "Copy if Newer," "Distribute Always," etc). For more information about managing Application files, see the ZENworks 2 documentation Web site at www.novell.com/documentation/lg/zen2/docui/index.html Click Contents > Application Management > Application Distribution > Managing > Application files. 7.0 Remote Control File Transfer Enhancements Two new buttons have been added to the File Transfer Window: Upload: to copy files from the Console to the managed workstation Download: to copy files from the managed workstation to the Console For more information, go to http://www.novell.com/documentation/lg/zen2/docui/index.html click Remote Management > Managing, or click the Help button on the File Transfer window. 8.0 Sybase Sorting Fix Earlier versions of Sybase had a problem with sorting double-byte strings, resulting in an incorrect sorting of the inventory reports. The newer version of Sybase shipping with the ZENworks 2 Support Pack 1 corrects this problem. 9.0 Reporting Enhancement The enhancement contains seven files that make enhancements to comma-delimited reports. This allows all fields to be populated regardless of whether or not the fields are duplicate fields. Six files will be replaced: ...\reporting\nwadmin.jar ...\reporting\rbw.bat ...\reporting\reporting.exe ...\reporting\reportingdos.exe ...\reporting\rw.bat ...\reporting\jinfonet\jslc.dat One file is new: ...\reporting\jinfonet\JReportBeans.zip (optional) You can manually remove the following files from the ...\reporting directory. Taking no action will not cause any problems; the patch renders these files obsolete: ...\reporting\jinfonet\jrengine.zip ...\reporting\jinfonet\jrresultviewer.jar 10.0 ManageWise 2.6 and ZENworks 2 Integration You can use Remote Control and other ZENworks 2 features from the ManageWise Console. Please see TID #2953276 for details. To access this TID, go to http://support.novell.com/servlet/Knowledgebase > type "2953276" in field 3 > click Search Now. 11.0 Application Launcher Flashing Icons Fix The problem of flashing icons in ZENworks 2 Application Launcher has been fixed in Support Pack 1. Please see TID #10013457 for details. 12.0 Remote Management Agent for Windows NT ZENworks 2 Support Pack includes an updated Remote Management Agent for Windows NT. If you are already running ZENworks 2, rerun the RemoteNT NAL object to install the updated Remote Management Agent for Windows NT. 13.0 Viewing Audit Log Information for Remote Management Sessions ZENworks 2 stored the audit information for Remote Management events in the Security log file. ZENworks 2 Support Pack 1, stores audits in the Application log file. From the Event Viewer, click File > Application to view the audits for Remote Management sessions. 14.0 Detailed List of Fixes in the Support Pack 14.1 Fixes Applied to the Application Launcher Applying the ZENWorks 2 Support Pack should have the following effects on the Application Launcher: - In a container object's Applications page, you will now be able to tell which objects within the container are associated - The version field is now disabled when Win 3.1 is selected in the application object's System Requirements page - System Requirements control is grayed out when the user has only Read and Compare rights. - You can modify an application dependency requirement. - Search and Replace now works beyond the first line in a Multi-String registry value - Removing a workstation-associated application removed from a container object will no longer reappear. - Executing NALEXPLD.EXE on a Windows 2000 machine loads the splash window and installs the NALEXPLD system tray icon. It also now installs the Application Explorer icon onto the desktop and loads the other links in the task bar. 14.2 Fixes Applied to the Application Explorer Applying the ZENWorks 2 Support Pack should have the following effects on the Application Explorer: - App Explorer now remembers the Options setting. - The Application Launcher saves the "Browse Folder By Single Window" option. - The 'Name Icon on Desktop in Application Explorer now accepts macros. This is found on the Launcher Configuration Property Page > Explorer tab > Name Icon on Desktop. - Refresh option no longer displays on View pull-down menu in Windows 98 after manual refresh has been disabled - Prompted String Macro now displays four characters. - Personal Folder quick menu now contains a "New Personal Folder" menu item. - Arrange Icons: Auto Arrange displays a check mark next to the menu item indicating the item is selected. - There is now only one icon per application object. - NALEXPEX.DLL no longer treats all .NAL shortcuts as applications, thus eliminating all NAL shortcut folders returning a -601 error. - Application Launcher personal desktop items are now stored for future use. - You can now save Application Launcher shortcuts that are folders. - Application Explorer now reads Go and GoSpecial strings to configure the Novell bitmap in lower-right corner of the Launcher window. 14.3 Fixes Applied to the Application Library Applying the ZENWorks 2 Support Pack should have the following effects on the Application Library: - Roll Back now works on directories. - NAL Mapping Search Drive now working (explained in TID 2947114). - Environment Variables set in Pre-Launch script are now available to the application With the version of NAL included in ZENworks 2, the environment variables set in the Pre-Launch script are not directly available to the application. - Running NAL.EXE and/or NALEXPLD.EXE and NWAdmin32.exe on the same NT workstation no longer causes multiple errors/problems, including Dr. Watson. - Distribute INI file no longer causes GPF - NAL is able to push down applications to Win2000 14.4 Fixes Applied to snAppshot Applying the ZENWorks 2 Support Pack should have the following effects on snAppshot: - Running snAppShot on German Windows 95 machine now functions and displays correctly. 14.5 Fixes Applied to Client Configuration Applying the ZENWorks 2 Support Pack should have the following effects on the client install: - When attempting to do a custom client install with NT, the installation finishes. 14.6 Fixes Applied to Hardware and Software Inventory Applying the ZENWorks 2 Support Pack should have the following effects on hardware and software inventory: - Software inventory scan policy now works with Korean Win95/98 with the English 3.10 client installed. - In the Non-English Netware server, if it is restarted (downing it and bringing it up), the database storer no longer crashes. - Inventory works on Windows 95, 98 (now able to load Resource.DLL - WIN16RES.DLL - In Scheduler, doing a "Run Now" on the Workstation Inventory WinNT Workstation Package gathers inventory on the machine. - New field for inventory: "Machine type-model + system unit serial number" 14.7 Fixes Applied to Remote Management Applying the ZENWorks 2 Support Pack should have the following effects on remote management: - In Remote Execute, the prompt on the target machine now goes away. - When using Remote Control from A Windows 95 machine, IPX will be used to contact the remote workstation if it is selected as the protocol. - The "Remote management service hung on starting" error seen in the system log on an NT workstation running the ZEN 2.0 client (4.60.302) is fixed. - After installing NT SP4 or SP5, the Security log now contains information after a remote control session. Logging of remote control is successful. - When executing Remote Control Diagnostics, the Novell Client version information is now shown properly. 14.8 Fixes Applied to Workstation Management Applying the ZENWorks 2 Support Pack should have the following effects on workstation management: - ZENDEL.log is now getting created. - Search policy no longer ignored when set to 'selected container' (explained in TID 2942868). - Windows 95 User System Policies no longer by default have white check boxes which cancel other policies. - When deleting multiple workstation objects from DS, now all corresponding entries from the Inventory database are deleted. - If an NT user is added to the administrator group in NT, extensible policies now push to the client. - On Win95 workstations, NWadmin no longer has a problem finding DMWORK.DLL. 14.9 Fixes Applied to Workstation Import Applying the ZENWorks 2 Support Pack should have the following effects on workstation import: - Registered workstations with import rights denied can no longer be imported anyway by users with insufficient rights to the container the workstation is registered in. - Workstation Import Policy now shows up on a 95a machine. 15.0 Legal Information 15.1 Disclaimer and Copyright Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability, title, or fitness for a particular purpose. Distribution of any Novell software is forbidden without the express written consent of Novell, Inc. Further, Novell reserves the right to discontinue distribution of any Novell software. Novell is not responsible for lost profits or revenue, loss of use of the software, loss of data, costs of re-creating lost data, the cost of any substitute equipment or program, or claims by any party other than you. Novell strongly recommends that you make a backup before you install any software. Technical support for this software may be provided at the discretion of Novell. Copyright (C)1999 Novell, Inc. All rights reserved. U.S. Patent Nos. 5,349,642; 5,594,863; 5,633,931; 5,692,129; 5,761,499; 5,781,733; 5,859,978. U.S. and Foreign Patents Pending. 15.2 Trademarks ManageWise, Novell, and NetWare are registered trademarks of Novell, Inc. in the United States and other countries. BorderManager, BorderManager FastCache, IPX, NDS, NetWare, Novell Client, and ZENworks are trademarks of Novell, Inc. All third-party trademarks are the property of their respective owners.