Link to home
Start Free TrialLog in
Avatar of LockDown32
LockDown32Flag for United States of America

asked on

Need Help Understanding GPO Inheritance

Well... in the Default Domain Policy I disable the Offline Files service on workstations. I then created an OU called Laptops, move the laptops out of Computers in to this Laptop OU then created a GPO and Linked it to this Laptop OU that set the Offline Files service to automatic start.

   I them did a GPResults on a Laptop in that OU and it said the Offline Files service was disabled because the winning GPO was the Default Domain Policy. I guess I need help. I though the GPO linked to this Laptop OU would have taken precedence but it didn't.

Can anyone straighten me out?
Avatar of Cliff Galiher
Cliff Galiher
Flag of United States of America image

Did you gpupdate first? Gpresults only tells you the current state, which can change based on refresh cycles. Gpmodelling is more accurate in these instances.
Avatar of LockDown32

ASKER

I gpupdated the server first then gpupdated the workstation. I used the GPMC on the server (Gpmodelling) for the results.
Your understanding is correct that OU takes precedence when all other things are equal. So you have something else going on. Enforced policies, disabled links, security or WMI filters can all change the default precedence behavior.
OK. Maybe it is a GPUpdate problem and I should give it a couple reboots to take effect. The whole domain is pretty much at the defaults and not a whole lot is being done GPO wise. You say "Enforced Policies". Might that be where I am going wrong? As soon as I link the GPO I enforce it. I have always assumed that is what should be done. When would you want to link one yet not enforce it? Doesn't that defeat the purpose?
ASKER CERTIFIED SOLUTION
Avatar of Cliff Galiher
Cliff Galiher
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
OK. All of the GPOs I linked are also enforced. I will go back and un-enforce them. Thanks for the heads-up.