Following up to my own question, I found this KB article
this morning. Might be good to have on hand for anyone if they were to run
into this sort of situation.
Took alot of digging :-)
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Wassell
Sent: Wednesday, February 11, 2004 9:56 AM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] Stale GPO GUID in SYSVOL
This is going to be
hard to explain but I thought I would give it a shot and put it in a
nutshell.
Before I started my
position the previous admin decided to rollout internal software using
GPO. A mistake was made and an attempted rollback was performed. The
GPO was then deleted by the rollback process, but the process errored out and
the GUID remained within SYSVOL. This caused the original software
packages which were being published by the deleted GPO to continue distributing
to the clients, but the GPO could not be modified through the Group Policy
Editor snap-in. I researched the issue and could not seem to find any
relevant KB articles or mention of this problem happening in any other
environments, which meant the range of solutions were unfortunately few.
The easiest solution was to of course delete the files which were being
published but that was highly unfavourable from an administration
standpoint.
But, to make a long
story short. That problem was "patched up" at best (by creating a new
default GPO and forcing no override), a domain migration was planned from
the existing Windows 2000 AD structure to a seperate domain using a Windows 2003
AD structure. Which pretty much meant the stale GPO GUID and messy schema
went out the window with the previous structure. Fine and dandy, although
it seems the GPO still appears in the workstations rsop. This isn't
causing any problem, and is only a result of my being anal. Does anyone
have any idea what my next step could be in removing this
curse?
Hope this all makes
sense!
Thanks!
