Jason- That script looks at all the GPT folders in SYSVOL and, based on the GUID, then looks in AD to see if the GPO is missing the AD side. The assumption there is that somewhere along the way, you deleted a GPO but its GPT (SYSVOL part) did not get deleted along with the GPC (AD part). I would be highly suspect that you are getting 67 orphans. I would do a manual spot check of the AD GP container to verify that indeed those GUIDs that its finding are not in AD. Darren -----Original Message----- From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Jason B. Halladay Sent: Monday, December 10, 2007 3:20 PM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] FindOrphanedGPOsInSYSVOL.wsf Hi all, I'm attempting to clean up an inordinate amount of GPOs in our environment. I'm starting with the FindOrphanedGPOsInSYSVOL.wsf script and it shows 67 orphaned GPOs. I'm curious what makes the GPOs "orphaned" and how we ended up with 67 orphans. From what I've read, it's safe to delete these without causing any issues or removing valid GPOs. Is this correct? Thanks! Jason *********************** You can unsubscribe from gptalk by sending email to gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by logging into the freelists.org Web interface. Archives for the list are available at //www.freelists.org/archives/gptalk/ ************************ *********************** You can unsubscribe from gptalk by sending email to gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by logging into the freelists.org Web interface. Archives for the list are available at //www.freelists.org/archives/gptalk/ ************************