User-assigned bundles are missing after login

  • 7014370
  • 06-Jan-2014
  • 30-May-2014


Novell ZENworks Configuration Management 11.2 Bundles


Bundles are user-assigned.
Bundles have a requirement checking for existence of a file on a network share.
This has been primarily reported for NCP network shares connect through Novell Client.

The bundle requirement fails to pass shortly after user authentication depending on how quick the user login goes through.

Bundles are not available to the logged-in user, but the user can access the referenced files on the network share.


A fix for this issue is intended to be included in a future update to the product: however, in the interim, Novell has made a Patch available for testing, as part of an FTF Roll Up patches collection: it can be obtained at as "FTF Roll Up 1 for ZENworks (11 SP3)". This update should only be applied if the symptoms above are being experienced, and are causing problems.

Please report any problems encountered when using this Patch, by using the feedback link on this TID.

Note: The fix also includes an optional registry value to further delay the ZCM agent user session refresh, see the Additional Information section for more detail.


Trigger a general refresh of the ZCM agent on the affected device so that the bundle requirements are getting reevaluated and missing bundles become available.


The agent triggers the general refresh of the user session and the related bundle requirements verification too early in the user login process before networking might be completely initialized. It is even possible that the ZCM agent tries to verify bundle requirements before the so-called ZenUserDaemon process is started, allowing the ZCM agent to actually interact with the logged-in user session. In this case the requirements test falls back to the device session which can only access network paths with public rights.

The ZCM agent does not depend on Novell Client or Microsoft networking so that there is not direct sync between ZENworks user login / user session refresh and network redirection.

Additional Information

The fix is to better time when the user session refresh gets triggered so that it actually starts when user login, not only to ZCM but also the local Windows login, is completed.

Additional it is possible to further delay this ZCM agent user session refresh for a specified amount of seconds. This has been added since it might take some additional time until driver mappings become accessible and to overcome the fact that the ZCM agent is not depending on a network provider like Novell Client:
Under HKLM\Software\Novell\ZCM\Refresh\, create a DWORD value as UserRefreshDelay and data (decimal value) in number of secs user refresh needs to be delayed.