The GPTalk Mailing List

The GPTALK mailing list is where you can send and receive email related to Windows Group Policy. You must subscribe to the list to send and receive mail from the list. The purpose of the list is to provide a forum for asking and answering technical questions related to Group Policy. Any question is fair game as long as it is related to Windows Group Policy. The Archives for this list can be found on this page.

List Posts

Unanswered Active Topics

Forums Search

Forums >GPTalk >GPTalk Mailing List

Subject: [gptalk] AGPM and GPO Version Number question

Prev Next

You are not authorized to post a reply.

Author

Messages

ccraig

Posts:2

06/03/2009 11:58 PM
All, Can someone please explain this behavior that I am seeing in AGPM...... AGPM increments the version number by 2 in the local repository during the check-in process if a change is made to the policy. Once the policy is deployed to production the Group Policy version increments the version by 1 (which is what one would expect), discounting the agpm version. See screenshot. [cid:image001.png@01C9E47C.B4FD8140] This leads to a mismatch in the version # between production and what in the local agpm repository. Yes I realize that this may be a non-issue but it make it confusing when looking at the History. My only thought is that the "deploy" process doesn't replace\merge the gpt.ini in production. Anybody have insight on this?

omar

Posts:75

06/04/2009 12:17 AM
I always though that the version increases based on the node you are editing. In your example it looks like you are modifying the computer configuration node several times and almost never the user configuration node. Omar From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Craig, Coleman Sent: Wednesday, June 03, 2009 3:57 PM To: xxxxxxxxxxxxxxxx Subject: [gptalk] AGPM and GPO Version Number question All, Can someone please explain this behavior that I am seeing in AGPM.. AGPM increments the version number by 2 in the local repository during the check-in process if a change is made to the policy. Once the policy is deployed to production the Group Policy version increments the version by 1 (which is what one would expect), discounting the agpm version. See screenshot. This leads to a mismatch in the version # between production and what in the local agpm repository. Yes I realize that this may be a non-issue but it make it confusing when looking at the History. My only thought is that the "deploy" process doesn't replace\merge the gpt.ini in production. Anybody have insight on this?

ccraig

Posts:2

06/04/2009 12:33 AM
Correct. I made a change to the computer configuration in the policy but not the user configuration. But AGPM incremented the version by 2, from 6 to 8. After deploying the policy the version in Sysvol is 7. The gpt.ini for the Default Domain Controllers Policy in production is: Version=65543 Which converted to Hex and taking the 2nd set of 4 octets is = 7 The gpt.ini for the Default Domain Controllers Policy in the AGPM repository is: Gpreport.xml = 8 From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Omar Droubi Sent: Wednesday, June 03, 2009 7:17 PM To: xxxxxxxxxxxxxxxx Subject: RE: [gptalk] AGPM and GPO Version Number question I always though that the version increases based on the node you are editing. In your example it looks like you are modifying the computer configuration node several times and almost never the user configuration node. Omar From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Craig, Coleman Sent: Wednesday, June 03, 2009 3:57 PM To: xxxxxxxxxxxxxxxx Subject: [gptalk] AGPM and GPO Version Number question All, Can someone please explain this behavior that I am seeing in AGPM...... AGPM increments the version number by 2 in the local repository during the check-in process if a change is made to the policy. Once the policy is deployed to production the Group Policy version increments the version by 1 (which is what one would expect), discounting the agpm version. See screenshot. [cid:image001.png@01C9E480.966889B0] This leads to a mismatch in the version # between production and what in the local agpm repository. Yes I realize that this may be a non-issue but it make it confusing when looking at the History. My only thought is that the "deploy" process doesn't replace\merge the gpt.ini in production. Anybody have insight on this?

You are not authorized to post a reply.

Forums >GPTalk >GPTalk Mailing List > [gptalk] AGPM and GPO Version Number question

ActiveForums 3.7

Ads

The GPTalk Mailing List

List Posts

Members

Ads