Slow login on agent machines after upgrading to ZCM 10.1

  • 7001541
  • 07-Oct-2008
  • 27-Apr-2012

Environment

Novell ZENworks 10 Configuration Management with Support Pack 1 - 10.1 Authentication

Situation

Login times on the ZCM 10.1 agent machines take 1 to 2 minutes.

Resolution

 This is fixed in version 10.2 - see KB 7003225 "ZENworks 10 Configuration Management 10.2" which can be found at https://www.novell.com/support

Additional Information

For other TIDs relating to login issues, see TID 3273870 - Troubleshooting ZCM login problems
 
Below is information that will help determine if this is related to your issue:
 

It turned out that there were three issues causing the slowness: the first issue was delaying the login process, the second issue delayed the display of bundle icons in the start menu.


The slow login was caused by the proxy auto-discovery of .Net 2.0. The WebRequest.Create() call that the ZENworks Windows Agent Service uses makes internally use of the proxy auto-discovery to fill in the default proxy. The solution was to turn off the proxy auto-discovery for the ZENworks Windows Agent Service. Configured proxies and proxies configured through the ZENworks zone are still being used. This issue has been resolved in zmd.dll.


The second issue delayed the processing of the user refresh, which held up the NAL views before they were able to display bundle items on the desktop and in the start menu. Specifically, a disk space requirement was causing the delay in the refresh, because WMI was not initialized when the ZEN Windows Agent Service made the request. We are now using a different class to determine the disk utilization which circumvent the issue. This issue has been resolved in requirements.dll.


A third issue was causing delay in the firewall handler, which does not directly influence the login time, but the opening of the port for the quick-task web service on the managed device. This issue has been resolved in firewallhandler.dll.
 
The proxy auto-discovery was turned off with the config file and it can be created.  Below is what should be in the ZenworksWindowsService.exe.config file if needed because the proxy auto-discovery has since been turned off in the code, so there is not a need to use the file any more, but it can still be used for troubleshooting agents previous to 10.1.1. This file should be placed in the ZENworks bin directory of the managed device, i.e., %ZENWORKS_HOME%\bin which is usually C:\program files\novell\zenworks\bin
 

<?xml version="1.0" encoding="utf-8" ?>

<configuration>

  <system.net>

    <defaultProxy>

      <proxy bypassonlocal="true" usesystemdefault="false" />

    </defaultProxy>

  </system.net>

</configuration>


Feedback service temporarily unavailable. For content questions or problems, please contact Support.