Ben Hart
asked on
Group Policy - inaccessible.. why?
Ok I created a new GPO at the Domain level, linked it to the Workstation ou (since all domain workstation are in this OU). In the scope security filtering I specified only myself. This GPO only has computer settings within, so the user configuration is disabled, the link is enabled and enforced.
I gpupdate /force on my local machine (where I am logging into using the same account specified in the Security Filtering), then run a gpresults /h "filename". This GPO in question is not applied and is instead listed as Denied with the reason "inaccessible".
Ok what am I doing wrong here? It's linked to the machine OU, filtering only to include my domain account and the GPO only consists of Computer Configuration. I'm pulling what little hair I have left out on this...
Thanks!
I gpupdate /force on my local machine (where I am logging into using the same account specified in the Security Filtering), then run a gpresults /h "filename". This GPO in question is not applied and is instead listed as Denied with the reason "inaccessible".
Ok what am I doing wrong here? It's linked to the machine OU, filtering only to include my domain account and the GPO only consists of Computer Configuration. I'm pulling what little hair I have left out on this...
Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
but in your security filtering you removed the workstation in essence when you removed authenticated users and only added your user object.
Yup, you can't security filter a user when it is a computer based policy. Only if you make it a user based policy.
ASKER
Gotcha.. feel like a tard now ;p Had it all mixed up in my head.
Thanks guys!!
Thanks guys!!
ASKER