Compare multiple GPOs in Windows 2003


I have a task to clean up the GPOs in our Windows 2003 environment in preparation to upgrade to Windows 2008.  We have 109 (yes, one hundred and nine) group policy objects.  I need a utility to parse through these GPOs to give me a report on duplicate and conflicting settings.
I have downloaded Microsoft's Advanced Group Policy Management tool, but that does not seem to have the functionality to do this.

Any suggestions on a method to do this?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DonNetwork AdministratorCommented:
Mike KlineCommented:
I don't think there is anything that will go through all of them and compare (would be a nice product).  Most compare two GPOs


Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

CanHasCheezburgerAuthor Commented:
dstewartjr : those products only compare two GPOs at a time. I need to compare 109.
DonNetwork AdministratorCommented:
DonNetwork AdministratorCommented:
sorry link should have been

Automated approaches to this task may never give you what you want because GPOs sometimes link to external objects such as software packages, configuration files, login scripts, startup scripts, and more. These external objects generally will need to be evaluated manually to determine purpose.

Perhaps your best bet is to divide and conquer. Separate the GPOs into "user only", "computer only" and "mixed". Start with the GPOs at or near the root of the AD tree and study the cumulative effect of similar type GPOs as you travel down the OU branches, taking into account GPOs that may be filtered by security group or by WMI evaluation, link order, blocking and blocking override and loop back. Generally the GPOs near the root should contain the generic settings that apply to most everyone and the GPOs further down the tree branches should be very specific to the objects that that they apply to.

In a well designed OU/GPO structure there sould be relatively little contradiction in settings, and hopefully where contradictions do occur, they'll be made obvious by the name of the GPO or the name of the OU to which the GPO is applied.

When I've done this type of work in the past, I find it helps to carefully rename GPOs as you work through them so as to clarify their purpose. I find that GPO content can be changed over time, but IT folks don't bother to give the GPO a more appropriate name to reflect new functionality.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.