ZCM 10.3.1: Bundles and policies do not apply if the user logs in very quickly

  • 7007169
  • 08-Nov-2010
  • 27-Apr-2012

Environment

Novell ZENworks 10 Configuration Management with Support Pack 3 - 10.3 Authentication
Novell ZENworks 10 Configuration Management with Support Pack 3 - 10.3 Bundles
Novell ZENworks 10 Configuration Management with Support Pack 3 - 10.3 Policies

Situation

When a workstation with the ZCM 10.3.1 agent is booted, if the user logs in within around 20 seconds of the prompt first appearing, assigned bundles and policies may not be shown.
 
In the status page of the Z-Icon, the "Next Contact with Server:" field may show the value "not scheduled "
 
The problem does not occur if the user waits for one minute before login.

Resolution

For ZCM 10.3: This is fixed in version 10.3.2 - see KB 7007237 "ZENworks Configuration Management 10.3.2 - update information and list of fixes" which can be found at https://www.novell.com/support
 
Workaround: if it is not possible to upgrade to 10.3.2 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 https://download.novell.com/Download?buildid=rVFuD4alXGQ~ as "ZCM10.3.1 Bundles and policies do not apply if you login too soon - see TID 7007169". 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.

For ZCM 11: A fix for this issue is included in ZENworks 11, see KB 7006995 "ZENworks 11 - information and updates" which can be found at https://www.novell.com/support

Workaround:
The bundles and policies are applied if the agent is manually refreshed

Additional Information

The problem arose when a Random Refresh ran before the General Refresh, and then the General Refresh started before the Random Refresh finished.