Microsoft KB Archive/814609

= Group Policy Object Is Not Applied After You Edit the VersionNumber Attribute =

Article ID: 814609

Article Last Modified on 2/28/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Web Edition
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise x64 Edition
 * Microsoft Windows Server 2003, 64-Bit Datacenter Edition

-





SYMPTOMS
After you manually edit the versionNumber attribute of a Group Policy object (GPO) by using ADSIEdit or another Directory Services (DS) editor, the policy may no longer be applied. When you view the properties of the GPO by using the Group Policy Object Editor Microsoft Management Console (MMC) snap-in, 0 (zero) appears as the revision number next to the Computer and User revisions instead of the correct revision number. If you view the properties of the GPO in the Group Policy Management Console (GPMC) add-on program, no revision numbers are displayed next to Computer or User.



CAUSE
This problem occurs because the deletion of the version number causes damage to the GPO. This creates an unusable GPO that is no longer applied to the destination computers or users.



WORKAROUND
To work around this problem, re-create the damaged GPO, or restore it from a backup.



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.



MORE INFORMATION
You can use the GPMC to create backup copies of your GPOs. For additional information about the GPMC, visit the following Microsoft Web sites:

http://technet2.microsoft.com/windowsserver/en/technologies/featured/gp/faq.mspx

http://msdn2.microsoft.com/en-us/library/aa814149.aspx

Keywords: kbprb kbnofix kbbug KB814609

-

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

© Microsoft Corporation. All rights reserved.