Software Restriction Policies Do Not Persist After You Define Them (830678)
The information in this article applies to:
- Microsoft Windows Server 2003, Standard Edition
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, 64-Bit Enterprise Edition
SYMPTOMSAfter you define Software Restriction Policies (also known as SAFER) under the User Configuration node of your domain policy, when you later click that Software Restriction Policies container, you receive the following message in the right pane of Group Policy Object Editor: No Software Restriction Policies Defined
Software restriction policies are not defined in this Group Policy object. If you define software restriction policies in this Group Policy object, they will override inherited policy settings from other Group Policy objects.
To define software restriction policies, in the Action menu, click New Software Restriction Policies.
This problem may also occur if you remove existing Software Restriction Policies. They may reappear after you enter the snap-in again.CAUSEThis problem occurs if you define Software Restriction Policies but if you do not change one or more of the default settings before you quit Group Policy Object Editor. In this scenario, the domain controller is not correctly updated with the information that the policy is changed. RESOLUTIONHotfix InformationA 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 Microsoft Windows Server 2003 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: 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. PrerequisitesNo prerequisites are required. Restart RequirementYou do not have to restart your computer after you apply this hotfix. Hotfix Replacement Information This hotfix does not replace any other hotfixes. File InformationThe English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.Windows Server 2003, 32-Bit Editions Date Time Version Size File name
--------------------------------------------------------------
03-Nov-2003 18:04 5.2.3790.99 462,848 Certmgr.dll Windows Server 2003, 64-Bit Edition Date Time Version Size File name
-----------------------------------------------------------------
03-Nov-2003 18:05 5.2.3790.99 1,396,736 Certmgr.dll IA-64
03-Nov-2003 18:04 5.2.3790.99 462,848 Wcertmgr.dll x86 WORKAROUNDTo work around this problem, modify one of the default Software Restriction Policy rules, and then apply the changes. Reopen the Software Restriction Policy item, restore the modified rule to its default setting, and then save your changes. The domain controller is then successfully updated with the information that the policy is changed.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
Modification Type: | Minor | Last Reviewed: | 10/27/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbBug kbfix kbQFE kbWinServ2003preSP1fix KB830678 kbAudITPro |
---|
|