Microsoft KB Archive/822155

= Client does not reset the permissions on some registry keys in Systems Management Server 2.0 =

Article ID: 822155

Article Last Modified on 10/25/2006

-

APPLIES TO


 * Microsoft Systems Management Server 2.0 Standard Edition

-





Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
As part of the daily Systems Management Server (SMS) client's maintenance cycle, Client Configuration Installation Manager (CCIM) tries to reset the incorrect registry permissions and ownership on a selected set of registry keys. However, CCIM may not reset the permissions and ownership on some of the keys. Therefore, the client may not operate correctly. This behavior may occur, for example, when the client does not connect to a Client Access Point (CAP). If this problem occurs, you receive the following message in the Ccim32.log file:

Warning: SecureRegEx returned 5 for key path

Additionally, CCIM's maintenance cycle does not try to reset the permissions on any one of Copy Queue's registry keys. This behavior can potentially prevent files from being copied from a client to a CAP.



CAUSE
This problem occurs because CCIM does not recursively set the permissions for certain registry keys and does not take ownership of those registry keys. CCIM also does not include Copy Queue's registry keys in the list of keys that it examines during the maintenance cycle.



Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Systems Management Server 2.0 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

To resolve this problem, install the hotfix that is described in the following Microsoft Knowledge Base article.

813847 Clients stop working if a package has many advertisements



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



WORKAROUND
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To work around this problem use Registry Editor to manually reset the registry permissions on the affected client registry keys so that the Administrators group has Full Control permissions. Also grant registry key ownership to the Administrators group.



MORE INFORMATION
When CCIM runs, it examines, and then resets the permissions and ownership on selected registry keys if that is required. CCIM processes some keys recursively so that the key and all its subkeys are checked and corrected. In particular, the problem that this article mentions affects these keys. CCIM does not process most of the keys recursively. Such keys do not exhibit the problem. CCIM does not change the subkeys of the keys that it processes non-recursively.

CCIM processes the following keys recursively:

CCIM processes the following keys non-recursively:

This hotfix updates the SMS client in two ways. First, with the hotfix, the SMS client correctly sets recursive permissions. Second, the hotfix includes a functional change to Copy Queue so that it recursively resets any incorrect registry permissions and ownership for the following key every time Copy Queue runs:

Keywords: kbqfe kbhotfixserver kbregistry kbclient kbsms200presp6fix kbsoftwaredist kbfix kbbug KB822155

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.