Troubleshooting the Automatic Workstation Import Service (AWSI)

  • 3704265
  • 18-Oct-2007
  • 30-Apr-2012


Novell ZENworks for Desktops 3.0
Novell ZENworks for Desktops 4.0.1 - ZfD4.0.1
Novell ZENworks 6.5 Desktop Management Support Pack 2 - ZDM6.5 SP2
Novell ZENworks 7 Desktop Management Support Pack 1 - ZDM7 SP1
Novell ZENworks Automatic Workstation Import


ZfD Import service is not importing after being installed.
No error messages in the SYS:ZENWORKS\ZENWSIMP.LOG (debug level set to 3).
No error messages in the C:\PROGRAM FILES\NOVELL\ZENWORKS\ZENWSREG.LOG (debug level set to 2).
Troubleshooting the Automatic Workstation Import Service (AWSI).
ERROR: -601 No Import policy found


What to check if the Workstation Object did not get created:

Most all of these troubleshooting steps are valid for ZfD 4, 6.5, & 7. The main difference is that instead of WSREG.EXE, ZfD 4, 6.5, & 7 use ZWSREG.EXE.

See KB 3494801 'Using ZWSREG' for information on using ZWSREG.EXE.

1.  During the installation of ZfD / ZDM, was the Automatic Import Service installed on the server?

2.  For ZfD, have the clients upgraded to the latest version? 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 the server's Import Service be Pinged? 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 KB 10013747 ( setting up DNS) to give out the servers 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 is an A Record (see TID 7002053
). This can be done from the DNS/DHCP Management Console.

If using the HOSTS file on the workstation (Win 95/98 C:\WINDOWS\, Win NT/2000/XP C:\WINNT\SYSTEM32\DRIVERS\ETC\), make sure it doesn't have a .SAM extension, if it does, remove the extension. 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).

Note: If the registry is used to define the import server (TID10058431),PING ZENWSIMPORT is not a valid test since PING does not read the registry to resolve ZENWSIMPORT.

4.  Is the Import Service loaded on the server?  Verify the Import Service is running by typing at the server console:JAVA -SHOW

Is this service 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 ZfD 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. For example, under the Platforms, if a specific container to hold all of the Workstation objects has been selected , this will be the only container that needs to be added to the Container tab. If the "Users Container" has selected as the target for Workstation object creation, 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 the workstation object is 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 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 for determining if the antivirus software is part or all of the import problem. If it is a factor, then Novell recommends contacting the vendor of the software and troubleshoot why it is holding files open or if there is any way (like excluding files or folders) to change the behavior of the software.

14.  Workstation objects will not be automatically deleted unless the Workstation Removal Policy has enabled and removal policy settings have been met. This may be a good time 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 objects in the tree that were 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 reinstall of ZFD must be done (after checking the health of the OS and DS, see KB 3197766 'Checking the OS and DS Health for Inconsistent ZENworks behavior.')

Use DSBROWSE.NLM on the server and look for duplicate zen objects that may not be seen with NetWare Administrator / Consoleone . Understand that each policy under the policy package is an individual object in NDS, but NetWare Administrator / Consoleone hides the objects below the policy package. Running DSBROWSE.NLM -A on a server with a replica of the partition where the policy package is located, browse down and view all of the zen policy objects and look for any duplicates that might exist. If duplicate objects are found with DSBROWSE, it has an option to delete the objects. DS administrators should be involved in this process. The option to delete the object is available loading DSBROWSE with the -A switch. If finding duplicates in the environment, another reason to use KB 3197766, referenced earlier.

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

18.  A list of errors and possible fixes can be found in TID 10056909
( Also review the Automatic Workstation Import subsection of the Error Messages section of the ZfD, ZDM documentation (

19.  Make sure that there are not any versions of ZENPOL32.DLL older than 08/08/2000 on the workstation, for more information see KB 10060488 (

20.  Delete the HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Workstation Manager\Identification key from the registry to trigger a new import. In affect, this triggers a new registration (see KB 10095169, -Dalwaysreuse). The workstation \...\Identification string in this registry should be a match for the workstation name in eDirectory.

21.  KB 10058431 recommends ' WSREG32.EXE with a -S=. (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 ZW 2 to ZfD 3.2, running WSREG32.EXE with the -s switch will create the ZW 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 'zenwsimport' entry. There were no ZW 2 snapins to see if the ZW 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=' 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 theWSREG32.LOG and ZENWSIMP.LOG files.

23.  Installed the latest ZfD / ZDM (NOVELL updates and patches) on the Import server.

24. If the Import server has been moved, see TID 10092184

25.Verify that the servers name is correct for the server hosting the java import service in the ZENWSIMP.NCF file

Additional Information

Formerly known as TID# 10056752