Initial user login slow or not possible at all after device start-up

  • 7008565
  • 12-May-2011
  • 06-Sep-2012


Novell ZENworks 11 Configuration Management Installation - Windows Agent
ZCM 11.0 - Cumulative Agent Patch 1


User login only possible when waiting up to 5 minutes on the login prompt.
User login gets delayed by 40 seconds.


This is fixed in version 11.1 - see KB 7008746 "ZENworks Configuration Management 11.1 - update information and list of fixes" which can be found at

Workaround: if it is not possible to upgrade to 11.1 at this time, in the interim, Novell has made a Patch available for testing, in the form of a Field Test File (FTF): it can be obtained at as part of "ZCM 11.0 - Cumulative Agent Patch 2a". This Patch should only be applied if the symptoms above are being experienced, and are causing problems.

This Patch has had limited testing, and should not be used in a production system without first being checked in a test environment. Some Patches have specific requirements for deployment, it is very important to follow any instructions in the readme at the download site. Please report any problems encountered when using this Patch, by using the feedback link on this TID.


Create a ZenworksWindowsService.exe.config XML file at %zenworks_home%\bin with the following content:
             <generatePublisherEvidence enabled="false"/>
This setting avoids possible delays on module start in .net.

Additional Information

The ZENLGN.log files will show a delay between the two entries below if the ZENworks login is waiting on the initial refresh to complete:
ZENLGN [][10:37:30:000] About to call ZENLogin in agent service
ZENLGN [][10:38:20:546] Returned from calling ZENLogin in agent service
Disabling the .NET Publisher Verification calls may reduce the amount of the delay by allowing the ZENworksWindowsService.exe to start it's refresh sooner, but a delay will generally still exist on any login attempts performed as soon as a device is booted to allow for the initial device refresh to complete.
The .NET issue is explained in further detail in the following articles: