How to configure the ZCM Agent and workstation to reduce ZCM overhead and increase logon speed

  • 7007583
  • 18-Jan-2011
  • 27-Apr-2012


Novell ZENworks 10 Configuration Management
Novell ZENworks 11 Configuration Management


The logon to Windows may significantly increase after installing the ZCM agent and Windows may be slightly sluggish immediately after logon to Windows.


The ZCM Agent will create some additional overhead that even in ideal circumstances will be perceptible, but there are many steps that can be taken to reduce that overhead.
Proper configuration of a workstation's Anti-Virus Package for ZCM is very important:
Delaying the start of NALVIEW.exe can significantly improve logon speed by reducing resource contention:
ZENLoginUserRefreshAsync=True may significantly increase logon performance, especially in ZCM 10.3.1 and greater:
NWSSO.DLL may slow down login if using an eDirectory User Source:
System Requirements on Bundles and Policies may take a significant amount of time to process:
Locally cached ZCM content files may significantly increase ZCM agent overhead:
Large APPSTATE files may take a long time to process:
ZENworks Software Inventory Scan may impact performance:
Assign local NTFS Permissions via a DLU Policy may impact performance:
Agent Configuration Setting to Slightly Improve DLU logon performance:

Additional Information

When Troubleshooting, it is recommended to get a baseline performance of a device without any Anti-Virus software, policies or bundles applied to get a baseline.
Running "zac cc" will not clear out all cached information, which may still affect performance.
On a test device, delete the entire %zenworks_home%\cache% folder. 
(Note: This will likely cause the device to lose registration.  Run "zac reg" to register the device again.)
Also test device performance during off-hours to minimize and isolate ZCM Server or Database Load issues from client issues.
Test Device performance both during an initial Windows boot as well as after the device has been running to isolate issues relating to events that occur on a device shortly after startup.