[gptalk] Re: Making Sense of GPO Versioning

  • From: "Darren Mar-Elia" <darren@xxxxxxxxxx>
  • To: <gptalk@xxxxxxxxxxxxx>
  • Date: Wed, 9 Aug 2006 08:56:52 -0700

Yes, its not altogether intuitive with respect to the registry/rsop
versions. But here is how it works. That number, 3997757, converts to
003d003d in hex. That's 4 bytes of data. Each two bytes represents the
number of revisions found in the GPT and GPC, for that GPO, on the DC used
for GP processing by that cllient. 0x3d = 61 in decimal so 61 revisions
found for both the GPT and GPC, for that GPO, on that DC, for that client.


From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On
Behalf Of Ryan Brennan
Sent: Wednesday, August 09, 2006 8:23 AM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Making Sense of GPO Versioning

I think understand a little on how GPO versioning works with GPC/GPT each
having there own version etc. Can someone make some sense of how the
versions are stored between RSOP, GPT.INI, Registry and AD Container? 


            For example I have a Default Domain Policy

            GMPC Version: User/Computer 1/71

            GPT.INI Version: 65607

            RSOP Version: 3997757

            Registry History
Policy\History): 3997757


I understand the GPMC and GPT, but the Registry/RSOP ones are confusing me,
I am figuring there is some binary/hex/decimal conversions going on here,
thoughts? I need the laymen breakdown please..



Best Regards,


Ryan Brennan


Secure Vantage Technologies


410 Pierce #209

Houston, TX 77006

C: 832.724.3067

O: 832.476.9309

F: 832.553.1087


Other related posts: