Workstations re-import unexpectedly.

  • 7005034
  • 16-Dec-2009
  • 30-Apr-2012

Environment

Novell ZENworks 7 Desktop Management Support Pack 1 - ZDM7 SP1
Novell ZENworks 7 Desktop Management on Linux Support Pack 1 - ZDML7 SP1
Novell ZENworks 6.5 Desktop Management - ZfD6.5.
Novell ZENworks for Desktops 4.0.1 - ZfD4.0.1.
Novell ZENworks Automatic Workstation Import.

Situation

Workstations re-import unexpectedly.

The new workstation object has the same name with a "1" appended to it (import string is based on the Computer Name only).

The new workstation object has the same computer name but a different MAC address (import string is based on the Computer Name and the MAC ).

The Import service screen and/or log reports:  "A workstation object with the same name and network address was found in the specified container.  The existing object will be used rather than creating a new one."

The Network address is not the same for the w/s since the NIC is different.

The existing object is not used.

Resolution

To always use the existing, imported workstation object, if it can be used and does not have to be re-imported:

For Netware:  Use the switch -Dalwaysreuse=true in the SYS:SYSTEM\ZENWSIMP.NCF .
 
Sample file :
 
Load Java envset zenAWSClassPath=SYS:java\njclv2\lib\jndi.jar;SYS:java\njclv2\lib\njclv2.jar;SYS:java\lib\zenWSDel.jar;SYS:java\lib\zenCommon.jar;SYS:java\lib\zenWS.jar;SYS:java\lib\autoWSManagement.jar java -classpath $zenAWSClassPath;$CLASSPATH -jszenWSImp -Dlogfile=SYS:zenworks\zenwsimp.log -Dlogfilelevel=3 -Dloglevel=3 -Dalwaysreuse=true -ns -sn"ZENworks Workstation Import" com.novell.application.zenworks.autowsmanagement.wsimport.ImportWorkstations "TREE-NAME""SERVER-NAME.CX"

For Windows environment:
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Novell\ZENworks\AutoWSImport]"zenwsimportCmdLine"="-Dlogfile=c:\\zenwsimp.log -Dlogfilelevel=3 -Dalwaysreuse=trueadd –-Dalwaysreuse=true.
 
For Linux environment:
 
Edit:   /etc/opt/novell/zenworks/zdm/novell-zdm-awsi.conf
Add:  alwaysreuse=true (at the bottom of the file preferably)
 
Sample clip from portion of /etc/opt/novell/zenworks/zdm/novell-zdm-awsi.conf  (with debug enabled):
 
-----
.
.
.
# Specify the log location.  If no location is set, no log
# will be generated
IMPORT_SERVICE_LOGFILE=/var/opt/novell/log/zenworks/awsi.log
REMOVAL_SERVICE_LOGFILE=/var/opt/novell/log/zenworks/awsr.log

# Specify the log level for log events reported to the console
# default=-1, valid levels are 0 to 3, 3 being the most verbose
#loglevel=-1
loglevel=3

# Specify the log level for log events reported to the log file
# default=-1, valid levels are 0 to 3, 3 being the most verbose
#logfilelevel=-1
logfilelevel=3

alwaysreuse=true
-----
 
Restart the import service.

Additional Information

A NIC went bad and was replaced, or a different NIC became 'standard'.  The workstation object is updated with the current IP address and MAC address on the existing w/s object but when the w/s has to re-import, for whatever reason (like problems with the health of eDir and / or the workstation object), a new object is created.

Monitor the debug import log to verify current behavior for when the workstations contact eDir for updating the existing object if it can be found and used.

Formerly known as TID# 10095169