Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a test environment where I have an DC and 1 XP client on the same network. I created a GPO and because of a syntax error, I removed it. On the client, I have ran GPUPDATE /force several times and even restarted the client. However, in the application event log, I see that the GPO is still being processed on the client (?? CACHED ??). I don't understand how after I removed the GPO from AD, rebooted and forced another GPUPDATE on the client, the old policy still exists. Is there any document on how to flush out the non-existent policy?


share|improve this question

migrated from Jan 7 '10 at 20:31

This question came from our site for computer enthusiasts and power users.

What policy did you apply, not all policies get removed with the GPO being unlinked – Zypher Jan 7 '10 at 20:50
Did you run the gpupdate on the server? did you attempt to restart the server? – p858snake Jan 8 '10 at 3:22

Your first stop would be the event logs on the client, it will clearly log whether policies are being applied or not.

share|improve this answer

On one of the test Domain Controllers, navigate to: C:\WINDOWS\SYSVOL\sysvol\\Policies Locate the ghost GUID and delete.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.