Solved

Group Policy is applying after GPO deletion

Posted on 2009-05-11
16
1,482 Views
Last Modified: 2012-05-06
I have a group policy setting which is still affecting clients event after the GPO has been deleted (not just the link).  I have verified that the policy no longer exists in the "\\DOMAIN_NAME\SYSVOL\DOMAIN_NAME\Policies" folder.  I have restarted the clients several times and RSOP still shows the policy in effect.  The policy name is no longer present but the SID is still showing.
WSUS-GPO-Issue.JPG
0
Comment
Question by:CCBIL
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 7
  • 5
  • 4
16 Comments
 
LVL 8

Expert Comment

by:Perry_IDITC
ID: 24356202
Hi,

It looks like the cached copies of the policy are still out there. You can create another tmp policy to delete the cached policies by going Computer Configuration \ Administrative Templates \ System \ User Profiles. and setting the Delete cached copies of roaming profiles as described here: http://support.microsoft.com/kb/274152

Cheers,
Perry
0
 
LVL 1

Author Comment

by:CCBIL
ID: 24356261
The Group Policy setting applies to computer settings rather than user settings.   Also, the GPO setting deals with WSUS settings rather than roaming user profiles.  A new policy that modifies the same values exists and shows as being applied, however when using RSOP the old policy "wins".
0
 
LVL 8

Expert Comment

by:Perry_IDITC
ID: 24356335
Have you run gpupdate /force and netdiag /v /l ? and/or restarted your server?
0
Free eBook: Backup on AWS

Everything you need to know about backup and disaster recovery with AWS, for FREE!

 
LVL 47

Expert Comment

by:Donald Stewart
ID: 24356463
Try this on your Domain Controller.
Browse to:
 
C:\WINDOWS\SYSVOL\sysvol\<DomainName>\Policies
Locate the ghost GUID and delete.

0
 
LVL 47

Expert Comment

by:Donald Stewart
ID: 24356502
oops, you already did that
0
 
LVL 47

Expert Comment

by:Donald Stewart
ID: 24356535
0
 
LVL 1

Author Comment

by:CCBIL
ID: 24357414
I used ADSI Edit and navigated to DOMAIN > CN=System >CN=Policies
However the GPO SID is not listed.  Any Idea if the registry keeps a cached list of Group Policies?  I know that it keeps a history of policies under [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\History

I found the reference to the old GPO and removed it from the client but that did not solve the issue.

0
 
LVL 47

Expert Comment

by:Donald Stewart
ID: 24357447
did you try doing a search for the guid throughout the registry?
0
 
LVL 47

Expert Comment

by:Donald Stewart
ID: 24357669
0
 
LVL 1

Author Comment

by:CCBIL
ID: 24358090
The only location in the registry showing the guid is

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\History

I removed the entry under this key for one of the clients but it did not change anything.
0
 
LVL 1

Author Comment

by:CCBIL
ID: 24364359
dstewartjr:

I do not think the SYSVOL article applies to my issue.
I have generated a list of orphan GPO objects, however the GPO does not exist in the directory.  

0
 
LVL 8

Expert Comment

by:Perry_IDITC
ID: 24366697
Can you recreate the policy with all the settings you had, apply it then remove it?

Heres an intersting artical on Group Policy Tattooing. Hopefully it will help.
http://www.gpoguy.com/FAQs/FAQs/Whitepapers/tabid/63/articleType/ArticleView/articleId/5/Understanding-Policy-Tattooing.aspx

Also, what all was in the group policy you deleted?
0
 
LVL 1

Author Comment

by:CCBIL
ID: 24367667
The GPO contained computer settings for Windows Update services.  I have a new GPO with different settings but as you can see from the RSOP screen shot the old nonexistent GPO still "wins".
0
 
LVL 1

Author Comment

by:CCBIL
ID: 24376936
The location of the windows update settings falls within the "no tattooing" zone in the registry.  I have pushed several updates out, however the old GPO which does not exist still wins.
0
 
LVL 8

Accepted Solution

by:
Perry_IDITC earned 500 total points
ID: 24386459
Ok.. I think you are going to have to resore your group policy objects to their orginal state. Then recreate them.

I would run gpupdate /force on the server then restart it, as a last resort before you try whats next.

Back up a Group Policy object using GPMC
http://technet.microsoft.com/en-us/library/cc782589(WS.10).aspx

Default Group Policy objects become corrupted: disaster recovery
http://technet.microsoft.com/en-us/library/cc739095(WS.10).aspx
-or-
Fix Corrupt Group Policy Database File
http://www.techzonez.com/forums/showthread.php?t=17510
1. Open the %SystemRoot%\Security folder, create a new folder, and then name it "OldSecurity".
2.Move all of the files ending in .log from the %SystemRoot%\Security folder to the OldSecurity folder.
3.Find the Secedit.sdb file in the %SystemRoot%\Security\Database folder, and then rename this file to "Secedit.old".
4.Click Start, click Run, type mmc, and then click OK.
5.Click Console, click Add/Remove Snap-in, and then add the Security and Configuration snap-in.
6.Right-click Security and Configuration and Analysis, and then click Open Database.
7.Browse to the %SystemRoot%\Security\Database folder, type Secedit.sdb in the File name box, and then click Open.
8.When you are prompted to import a template, click Setup Security.inf, and then click Open.

Good luck!
0
 
LVL 1

Author Comment

by:CCBIL
ID: 24389468
Winner!!!

Fix Corrupt Group Policy Database file resolved the issue.  I will add one step that I had to perform.

The system would not let me create the new database with the name Secedit.sdb.  I named the datebase test.sdb then selected the Setup Security.inf template.  I then applied the tempate the the computer.  After this I renamed test.sdb to secedit.sdb, ran gpupdate and the setting old corrupted setting was remove and the new correct setting applied.

0

Featured Post

On Demand Webinar - Networking for the Cloud Era

This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
change home folder path 4 59
Migration of AD user accounts from Server 2003 to 2012R2 5 120
SBS 2003 RWW Login 3 50
How to decline Windows updates with SCCM? 2 58
This may not be a text book method to resolve VSS backup issues but it seemed to have worked on few of the Windows 2003 servers we had issues while performing a Volume Shadow Copy backup. If you have issues while performing a shadow copy backup usin…
On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…

749 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question