NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: Updates to ZENworks 2 with Support Pack 1 TID #: 2958416 README FOR: zfd2pt3b.exe SUPERSEDES: zfd2nal1.exe NOVELL PRODUCTS and VERSIONS: ZENworks 2 and ZENworks Starter Pack (1999.12.12) ABSTRACT: This file contains updated files for the ZENworks for Desktops 2 (Full) product with Support Pack 1 (ZFD2SP1.EXE). This update may be used for ZENworks for Desktops 2 International version. Do not use this update file to update ZENworks 1.0, ZENworks 1.1, or ZENworks Starter Pack versions. ----------------------------------------------------------------- DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES ALL REASONABLE EFFORTS TO VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION. ----------------------------------------------------------------- INSTALLATION INSTRUCTIONS: On the server(s) where ZENworks 2 with Support Pack 1 is installed: 1. Make a backup copy of the following files: SYS:PUBLIC\NALDESK.EXE SYS:PUBLIC\NALWIN32.EXE SYS:PUBLIC\ZENAPP32.DLL SYS:PUBLIC\WIN32\ZENAPP32.DLL SYS:PUBLIC\WIN32\SNAPINS\APPSNP32.DLL SYS:PUBLIC\WIN32\SNAPINS\WMGR32.DLL SYS:PUBLIC\WIN95\ZENAPP32.DLL SYS:PUBLIC\WINNT\NALNTSRV.EXE SYS:PUBLIC\WINNT\ZENAPP32.DLL SYS:PUBLIC\SNAPSHOT\SNAPPE32.EXE SYS:PUBLIC\ZENWORKS\DIAGNT.DLL SYS:PUBLIC\ZENWORKS\JAVA\STORER.JAR 2. Copy the updated files included in this file to the corresponding directories: SYS:PUBLIC\NALDESK.EXE SYS:PUBLIC\NALWIN32.EXE SYS:PUBLIC\ZENAPP32.DLL SYS:PUBLIC\WIN32\ZENAPP32.DLL SYS:PUBLIC\WIN32\SNAPINS\APPSNP32.DLL SYS:PUBLIC\WIN32\SNAPINS\WMGR32.DLL SYS:PUBLIC\WIN95\ZENAPP32.DLL SYS:PUBLIC\WINNT\NALNTSRV.EXE SYS:PUBLIC\WINNT\ZENAPP32.DLL SYS:PUBLIC\SNAPSHOT\SNAPPE32.EXE SYS:PUBLIC\ZENWORKS\DIAGNT.DLL SYS:PUBLIC\ZENWORKS\JAVA\STORER.JAR 3. Run Application Launcher or Explorer (NAL.EXE or NALEXPLD.EXE). As part of running NAL or NALEXPLD, the updated files will be copied to the workstation's local drive. 4. NALNTSRV.EXE is a Windows NT Service and requires special installation. The NAL NT Service can be updated in any of the following ways: a. Installing the Novell Client for ZENworks 2.0 (4.6 SP1, 4.6 SP2, 4.7 or 4.71) with the updated NALNTSRV.EXE in the source files. The client installation can install the NALNTSRV.EXE on the workstation. b. NALNTSRV.EXE /install can be run on each individual workstation, however this requires sufficient rights to the workstation in order to make changes to the service. c. A custom action can be created in a Workstation Policy Package to run NALNTSRV /install. The policy package could be configured and associated to the workstations to provide the update. The Workstation object needs rights to the directory where the new NALNTSRV is stored. Then follow the following steps from the ZENworks 2.0 Logic Source: 1- Select Add Action on the Policies page and give the action a name like "Install/Update NALNTSRV." 2- Select the new scheduled action and click Details. 3- On the Actions page, select Add. In the Name field, enter the UNC path and filename to run NALNTSRV.EXE. In the Parameters field, specify install or install start. 4- Select OK to save the Item Properties. 5- Select the Policy Schedule page and set the Schedule to "Event." 6- Set the event to "User Login." 7- Select Advanced Settings. 8- Set Completion to "Disable the action after completion." 9- Set Impersonation to "System" and the Priority to "Normal." 10- Select OK to save the Advanced Settings. 11- On the Associations page, make sure the correct users, groups, or containers are listed. To install the STORER.JAR file, use the instructions below: On the NetWare server(s) where the ZENworks 2 Gatherer and Storer modules are installed: 1. Install the ZENworks 2 Support Pack 1 (ZFD2SP1.EXE) to the server prior to installing this STORER.JAR patch. This will upgrade your JAVA.NLM to version 1.1.7B. 2. The STORER.JAR cannot be updated until the processes using it are unloaded. To unload the Master and Storer process, follow these instructions: At the server console type: Java -show (this will show the current Java processes running by Class and ID) Java -kill#### (Enter the ID number in place of #### for the process to be killed) Storer is process: com.novell.zenworks.desktop.inventory.storer.Loader Master is process: com.novell.zenworks.desktop.inventory.storer.MasterProcess 3. Backup and Replace the existing STORER.JAR file on the server (SYS:PUBLIC\ZENWORKS\JAVA) with the updated STORER.JAR in this patch file. 4. The MASTER process which is called from the AUTOEXEC.NCF by the line that loads MASTER.NCF now automatically loads the STORER process. It does this by calling STORER.JAR from within the MASTER.NCF file. STORER.JAR then reads the STORER.NCF file. Therefore, after updating the STORER.JAR, it is necessary to comment out or remove any existing load lines in the AUTOEXEC.NCF that call STORER.NCF directly. You may notice that it takes a little longer for the STORER process to load this way. 5. After updating the STORER.JAR, it is necessary to move the STORER.NCF file from its installed location in SYS:\PUBLIC\ZENWORKS\JAVA to SYS:\PUBLIC\ZENWORKS. If this NCF file is not moved, the STORER.NCF file will never be read, and the STORER process will fail to load. 6. Edit the STORER.NCF file and add the "-nsac" switch to the Java load line for the storer class, replacing the "-ns" switch if it is found. The out of memory error may still occur with this version of STORER.JAR, but the process will restart automatically instead of halting, leaving the storer screen open and no longer injecting workstation data into the database. The "-nsac" switch will automatically clear the screen displaying the java.lang.OutOfMemoryError if it occurs. Without this switch, you will have to manually press a key to clear the error screen from the system console. The "-nsac"-switch works with Java version 1.1.7B only. See the example following step 8 for proper syntax. The reason that you still need to modify the STORER.NCF is because when the MASTER process loads the STORER process, it will now read the STORER.NCF file to get the parameters that it needs to load it. 7. Increase the maximum Java heap size (memory) by editing the STORER.NCF file and adding "-mx256M" (where 256 is the amount of memory in megabytes to dedicate to the Java process) right after the Java command. The Java default value is 64MB, so the default STORER.NCF file that gets created won't have a "-mx..." switch in it. Novell recommends 256 megabytes be a starting point if you're experiencing this error. Increasing the value from there may continue to help the storer processes. On NetWare 4.11 the heap size cannot be bigger than the amount of physical memory, as only NetWare version 5.0 and above use virtual memory. Turning off garbage collection may also help. This is done by adding the "-noclassgc" switch to the Java load line in the STORER.NCF. 8. To reload the Storer process, run MASTER.NCF (SYS:PUBLIC\ZENWORKS\JAVA) or restart the server using the RESTART SERVER command. This is an example of the STORER.NCF file that includes these changes: Envset CLASSPATH=$CLASSPATH;SYS:\PUBLIC\ZENWORKS\JAVA\STORER.JAR Envset CLASSPATH=$CLASSPATH;SYS:\PUBLIC\ZENWORKS\JAVA\JGL3.1.0.JAR Envset CLASSPATH=$CLASSPATH;SYS:\PUBLIC\ZENWORKS\JAVA\JDBCDRV.ZIP java -mx256M -nsac -noclassgc com.novell.zenworks.desktop.inventory.storer.Loader -dbloc 10.101.8.104 -temp VOL1:\zenworks\strdir -map sys:\public\zenworks\Java\txtfiles\map.ser -ass sys:\public\zenworks\Java\txtfiles\association.ser ISSUE: TID 10054046 - When viewing the Remote Diagnostics of a workstation through the imported workstation object in NWADMN32.EXE, the event times shown are exactly 1.5 hours ahead of the actual event time in the Event Viewer on the NT workstation. TID 10016189 - When a Printer Policy is pushed down the NetWare Settings are not taking effect correctly. TID 10050975 - After installing the ZENworks for Desktops v2.0 Support Pack 1, the Clean up network resources / Monitor Module name feature of an Application object no longer works. TID 10018012 - Error: "JAVA.LANG.OUTOFMEMORYERROR." Error appears on the STORER screen on the server after: Storing Workstation with DN The Scan was sent at: TID 10027178 ZENworks Application Management not handling Temp directories on a Terminal Server. Temp files go to the common Temp directory instead of the unique temp directory for that user. TID 10023564 - NAL distribution status bar not appearing if Track Distribution Per User or Distribute Always are checked. TID 10051211 - The ZENworks Snapshot program adds an extra carriage return to the end of Multi-Value String registry entries. Some application programs are sensitive to this extra carriage return and will not run until it has been removed. TID 10054061 Changes made to Application objects do not appear to be saved. The Application Management snapin, appsnp32.dll, reads a different replica than the one just written to. TID 10052161 - %USERPROFILE% is not working with NAL.EXE. TID 10052465 - Error: "Could not configure workstation for application [] (id=-15). Problem: Unable to create rollback files. (DO15)" TID 10027178 - Temp directories on a Terminal Server not working with NAL. Self-Extracting File Name: zfd2pt3b.exe Files Included Size Date Time ..\ ZFD2PT3B.TXT (This file) ..\PUBLIC\ NALDESK.EXE 749568 4-4-2000 2:16:00 pm NALWIN32.EXE 913408 4-12-2000 8:58:54 am ZENAPP32.DLL 376832 11-17-2000 10:01:30 am ..\PUBLIC\SNAPSHOT\ SNAPPE32.EXE 955904 6-5-2000 10:11:20 am ..\PUBLIC\WIN32\ ZENAPP32.DLL 376832 11-17-2000 10:01:30 am ..\PUBLIC\WIN32\SNAPINS\ APPSNP32.DLL 1613824 5-12-2000 5:04:42 pm WMGR32.DLL 737280 6-21-2000 9:29:50 am ..\PUBLIC\WIN95\ ZENAPP32.DLL 376832 11-17-2000 10:01:30 am ..\PUBLIC\WINNT\ NALNTSRV.EXE 110592 11-16-2000 1:08:28 pm ZENAPP32.DLL 376832 11-17-2000 10:01:30 am ..\PUBLIC\ZENWORKS\ DIAGNT.DLL 77312 6-14-2000 11:14:48 am ..\PUBLIC\ZENWORKS\JAVA\ STORER.JAR 37385 3-17-2000 3:04:18 pm ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. -----------------------------------------------------------------