Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

So today, I'm going through and cleaning up/consolidating our GPOs and moved a couple from a second-level OU to the domain level. These (user) policies are used to block/allow access to the command prompt. By default, all users are blocked from using the command prompt. Users can then be added to a security group that has permission to run the second (higher precedence) GPO to turn it back on.

When the GPOs are in the second level, they work as expected. But once I move them to domain level, all users are blocked from using the command prompt, to include the onces that should have access.

Our GPOs are well segregated, and I verified there were no conflicting GPOs. Link order and policy inheritance precedence was verified. Group Policy results showed both policies applying on the appropriate users, yet command prompt access is still blocked. Moved the GPOs back down... and everything works again?

What gives? Is there something special at the domain level that would cause this behavior?

share|improve this question

1 Answer 1

up vote 1 down vote accepted

There's nothing special about the root of the domain as compared to a sub-OU when it comes to Administrative Template Group Policy settings (password policy treats it specially, but that's not what you're talking about).

I don't know what you mean by "conflicting GPOs". GPOs don't "conflict". They are applied in the order specified and the last setting applied is the one that "takes". There are no "conflicts" and no "conflict resolution" protocol.

Examine the output of a gpresult /z for both "types" of users with the policies linked as you'd like them and as they were. You should be able to find the cause of your issue in comparing those outputs. My gut says that you've got your link order wrong for what you want.

Microsoft didn't make it easy to tell in the Group Policy Management Console what order the GPOs are applied in. It was a lot easier in the W2K3 / WK2 "gold" releases, in my opinion, to see what order the GPOs were going to be applied.

share|improve this answer
    
Thanks Evan. I guess it was a poor choice of words to say "conflicting" GPO. What I was trying to convey was that there are no other GPOs that manipulate the same settings. I verified the link order in GPMC, but will check gpresult and see what the results are. –  newmanth Sep 14 '11 at 20:02

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.