Novell is now a part of Micro Focus

Troubleshooting Automatic Workstation Import

Novell Cool Solutions: Feature

Digg This - Slashdot This

Posted: 22 Aug 2002

Current version: ZENworks for Desktops 3.2

If you're having trouble with Automatic Workstation Import Service, save yourself a call to Support, and read this first. This list of troubleshooting strategies came from the good folks in Support, compiled from their experiences with other customers.

If the Workstation Object did not get created, here are some things you should check:

1. During the installation of ZfD3, was the Automatic Import Service installed on the server?

2. Are the clients upgraded to 3.3 and 4.8? The workstations must be upgraded to the new "Workstation Registration" files, which are included in Novell Client 3.3 for Windows 95/98 or Novell Client 4.8 for Windows NT/2000. The clients must be connecting to the servers via IP, NOT IPX.

3. Can you Ping the Import Service on the server? For workstations to register, they must be able to ping the ZENWSIMPORT service running on the server. This can be done by using DNS (see Solution 10013747 for setting up DNS) to give out the server's IP address as being associated to ZENWSIMPORT, or editing the HOSTS file on the workstations. If DNS is already setup, all that needs to be added in an A Record. This can be done from the DNSDHCP Management Console.

If editing the HOSTS file on the workstation, make sure it doesn't have a .SAM extension; if it does, remove the extension.

Windows 95/98: C:\WINDOWS\HOSTS, or it may be called HOSTS.SAM (If it displays as hosts.sam you will have to rename it to just 'HOSTS' with no extension.)

Windows NT/2000: C:\WINNT\SYSTEM32\DRIVERS\ETC\HOSTS, or HOSTS.SAM. (Again, this will need to be renamed if it appears as HOSTS.SAM as mentioned above.)

Add the server IP address to the HOSTS file and associate it to ZENWSIMPORT. It should look like this:     ZENWSIMPORT

To test this setup, open a DOS box and try pinging the ZENWSIMPORT Service. (Ex. Open a DOS Window and type PING ZENWSIMPORT)

4. Is the Import Service loaded on the server? Verify the Import Service is running by typing JAVA -SHOW at the server console and see if COM.NOVELL..APPLICATION.ZENWORKS.AUTOWSMANAGEMENT.WSIMPORT.IMPORT is running. If not, load SYS:SYSTEM\ZENWSIMP.NCF or restart the server. Sometimes, it is necessary to restart the server running the Import Service, especially if AWSI has not worked since ZfD3 was installed.

5. Is the Server Policy Package created?

6. In the Server Policy Package, is it associated to the server object where the Import service is loaded, or to the container where the server object resides?

7. In the Server Policy Package, is the Workstation Import Policy enabled?

8. In the Workstation Import Policy, under the Container tab, are the containers where the Workstation objects will be created added to the list? If not, add the containers to setup the rights needed to create workstations. This should match the setting you have under the Platforms > Location tab. Example: Under the platform, if you have selected a specific container to hold all of the Workstation objects, this will be the only container that needs to be added to the Container tab. If you have selected the "Users Container" option to create the Workstation object, you will need to add the Users' container(s) to the Containers tab.

9. Configure the Platforms tab under the Workstation Import Policy.

10. Under the Limits tab, the default setting for "User Login Number" is 3. This means the user will log in 3 times before the workstation object will be created. If you want the workstation object to be created the first time the user logs in, set it to 1.

11. To verify that the Workstation Import policy is configured correctly, check the Trustees of the container where the workstations will be created to see if the Workstation Import policy is a trustee of the container object.

12. Sometimes, it is helpful to delete and recreate the Server Policy Package.

13. Remove any virus scanning from the workstation. This eliminates the virus scanner from holding open the WSREG.DLL. This may manifest itself by no entry being written to the C:\WSREG32.LOG on boot up, but works when it is run manually.

(NOTE: Step 13 is ONLY a troubleshooting step. This is not intended to be a solution to remove Antivirus Protection Software. This is just one thing to try to determine if the antivirus software is what is causing part of all of the problem. If you find out that it is then Novell recommends that you contact the vendor of the software and troubleshoot why it is holding files open or if there is any way to change the behavior of the software.)

14. Workstation objects will not be automatically deleted unless you have enabled the Workstation Removal Policy. You may want to set this up while you're configuring the Server policies.

15. Make sure you have the following lines in your AUTOEXEC.NCF:


16. Check the Trustees of the Server Package (or other ZfD 3 objects in the tree that are created during the install), Import Policy properties (NDS Rights tab) for trustees that have xxxxx-000x extensions. This indicates that there are duplicate policy objects in NDS. These must be addressed and then a re-install of ZfD 3 must be done.

Use DSBROWSE.NLM on the server and look for duplicate ZEN objects that you cannot see with NetWare Administrator. Note that each policy under the policy package is an individual object in NDS. NetWare Administrator just hides the objects below the policy package. If you run DSBROWSE.NLM -A on a server with a replica of the partition where the policy package is located, you can browse down and see all of the zen policy objects and and any duplicates that might exist. Once you find the duplicate objects with DSBROWSE, hitting <F3> will give you an option to delete the objects. You only get the option to delete the object if you load DSBROWSE with a -A switch.

17. After completing this checklist of items, reboot the workstation and check to see if it imported correctly. If it still is not imported, view the log files C:\WSREG32.LOG and/or SYS:\ZENWORKS\ZENWSIMP.LOG. To get more verbose information in the ZENWSIMP.LOG, edit the SYS:SYSTEM\ZENWSIMP.NCF and set -Dlogfilelevel=3 (values 0 to 3), then restart the server and reboot the workstation.

The default SYS:SYSTEM\ZENWSIMP.NCF file contains the following debug parameters:

-Dlogfile=sys:zenworks\zenwsimp.log -Dlogfilelevel=2 -Dloglevel=0

-Dlogfile= sets the path and filename of the log file
-Dlogfilelevel= sets the verbose level of logging to the log file (0 is none, 3 is most verbose)
-Dloglevel= sets the verbose level of logging to the System Console screen (0 is none, 3 is most verbose)

To see a real time trace screen of the Automatic Workstation Import Process, insert a "-ns" (ns = new screen) after -Dloglevel=0. An example ZENWSIMP.NCF file with the verbose debugging enabled and a new screen enabled would look like this:

Load Java
java -classpath $zenAWSClassPath;$CLASSPATH -jszenWSImp 
-Dlogfile=sys:zenworks\zenwsimp.log -Dlogfilelevel=3 -Dloglevel=3 -ns
ImportWorkstations "" ""

18. A list of errors and possible fixes can be found in the document Automatic Workstation Import/Removal Errors and Suggested Remedies. You can also review the Automatic Workstation Import Error Messages.

19. Make sure that you don't have ANY versions of ZENPOL32.DLL older than 08/08/2000 on your workstation. See this document for more information: ZENworks policies stop downloading after installing 3.3 Novell Client for Windows9X in ZENworks 2 environment.

20. Try deleting the HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Workstation Manager\Identification key from the registry.

21. Run WSREG32.EXE with a -S=<domain name or IP address>. (ex. wsreg32.exe This will work for this one instance of running WSREG32.EXE to bypass ZENWSIMPORT handed out by DNS.' This worked with ZENworks 2, but may not work for ZfD 3.x. If the environment is a migration from ZEN 2 to ZfD 3.2, running WSREG32.EXE with the -s switch will create the ZEN 2 registration object in a container's 'Workstation registration' property rather than importing to the ZfD 3.2 environment.

In a new ZfD 3.2 environment, the import did not happen either if the local host file did not have the '<ip_address> zenwsimport' entry. There were no ZEN 2 snapins to see if the ZEN 2 registration 'cookie' was registered and waiting to be imported.

This symptom could not be reproduced in the new ZfD 3.2 environment after applying ZD32PTK.EXE (and related beta client SP 1). If the symptom persists after applying the latest ZfD 3.2 patches, add these registry entries (if they do not already exists) and run the 'wsreg32.exe -s=<ip_address>' command again.

[HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Workstation Manager\Identification]
"Tree"="LAB134_TREE"                               [String Value]
"EXE Path"="C:\\WINNT\\System32"             [String Value]

If these do not work either, the solution is to use the other import options: local host file, registry setting, or a DNS entry for zenwsimport.

22. If the AWSI process is still not working after going through this list and the list of errors, Novell Technical Support Services will need to obtain the WSREG32.LOG and ZENWSIMP.LOG files.

Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions.

© Copyright Micro Focus or one of its affiliates