Novell is now a part of Micro Focus

My Favorites


Please to see your favorites.

ZCM Icons are missing with NoDesktop GPO enabled

This document (7011389) is provided subject to the disclaimer at the end of this document.


Novell ZENworks Configuration Management 11.2 Policies


After upgrading to 11.2.1 on the ZCM agent. ZCM icons no longer appear in Start > Programs.
Using windows Group Policy NoDesktop, no icons should appear on the desktop, but ZCM icons should appear in Start > Programs
GPO worked properly in ZCM 11.1.
GPO worked properly in ZCM 11.2 with registry key  see additional information below.
ZCM icons appear in Nalwin if assigned to Nalwin.


This is fixed in version 11.2.3a - see TID 7011295 "ZENworks Configuration Management 11.2.3a - update information and list of fixes" which can be found at

Workaround: if it is not possible to upgrade to ZCM 11.2.3a at this time, in the interim, Novell has made a Patch available for testing, as part of a Monthly patch update: it can be obtained at as "ZCM 11.2.2 Monthly Update 1 - see TID 7010464". 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.

Additional Information

The Registry key required for 11.20 is in the ZCM 11.2 readme
Go to HKLM\Software\Novell\ZCM\NAL.
Create a DWORD called SetIconOnDesktop and set the value to 1.
The registry key for the GP NoDesktop =1 is HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\NoDeskop


This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7011389
  • Creation Date:16-NOV-12
  • Modified Date:11-APR-13
    • NovellZENworks Configuration Management

Did this document solve your problem? Provide Feedback