Die-Tech
asked on
GPO problem
In my active directory, I have setup an OU called Information Systems
Under Information System, I have an OU called Terminal Servers
I put one of my terminal servers in teh Terminal Servers OU and setup a group policy for that OU to "Hide these specified drives in My Computer"
- User Configuration, Administrative Templates, Windows Explorer
When I log on to the terminal server in the Terminal Servers OU, the drives are not hidden.
If I move the Terminal Servers OU directly under the domain and login, the drives are hidden.
Any ideas why I can't leave the OU as shown below
OurDomain.com
Information System
Terminal Servers
To make the GPO work, I currently have the OUs set like this..
OurDomain.com
Terminal Servers
Under Information System, I have an OU called Terminal Servers
I put one of my terminal servers in teh Terminal Servers OU and setup a group policy for that OU to "Hide these specified drives in My Computer"
- User Configuration, Administrative Templates, Windows Explorer
When I log on to the terminal server in the Terminal Servers OU, the drives are not hidden.
If I move the Terminal Servers OU directly under the domain and login, the drives are hidden.
Any ideas why I can't leave the OU as shown below
OurDomain.com
Information System
Terminal Servers
To make the GPO work, I currently have the OUs set like this..
OurDomain.com
Terminal Servers
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Did you link the GPO to that OU? You can also create another GPO and place it in side the OU.
Also might have to use loopback processing.
Sorry about the multiple posts, ideas keep comming in. I have spent alot of time with issues like this. We have a kind of complex TS enviorment here. The GPO management tools are a god send. Use the report tool to see what Policys are applied and which one are not. It will also tell you why.
Keep in mind that Group Policy objects are processed according to the following order:
The local Group Policy object (LPGO) is applied.
GPOs linked to sites.
GPOs linked to domains
GPOs linked to organizational units. In the case of nested organizational units, GPOs associated with parent organizational units are processed prior to GPOs associated with child organizational units.
GPO links to a specific site, domain, or organizational unit are applied in reverse sequence based on link order. For example, a GPO with Link Order 1 has highest precedence over other GPOs linked to that container.
In general, the last policy to be applied wins if different GPOs attempt to apply conflicting values.
Using the Group Policy Management console, review the list of GPOs that are applied to each OU, paying close attention to any differences in the "Information System" and "Terminal Servers" OUs. I would look for any GPOs linked to the "Information System" OU that are set as "enforced", meaning they cannot be overrode by a later GPO.
The local Group Policy object (LPGO) is applied.
GPOs linked to sites.
GPOs linked to domains
GPOs linked to organizational units. In the case of nested organizational units, GPOs associated with parent organizational units are processed prior to GPOs associated with child organizational units.
GPO links to a specific site, domain, or organizational unit are applied in reverse sequence based on link order. For example, a GPO with Link Order 1 has highest precedence over other GPOs linked to that container.
In general, the last policy to be applied wins if different GPOs attempt to apply conflicting values.
Using the Group Policy Management console, review the list of GPOs that are applied to each OU, paying close attention to any differences in the "Information System" and "Terminal Servers" OUs. I would look for any GPOs linked to the "Information System" OU that are set as "enforced", meaning they cannot be overrode by a later GPO.
ASKER
Thanks everyone who posted...
I have to give the points to hypercat... he answered first.
After I moved the Terminal Servers OU back under the Information Systems OU, the policy started working... I'm guessing it was the inheritance issue hypercat mentioned... Moving the OU out and back fixed it.
BTW... I love the GPMC... thanks again hypercat for that suggestion.
I have to give the points to hypercat... he answered first.
After I moved the Terminal Servers OU back under the Information Systems OU, the policy started working... I'm guessing it was the inheritance issue hypercat mentioned... Moving the OU out and back fixed it.
BTW... I love the GPMC... thanks again hypercat for that suggestion.
Thanks for the points, and you're welcome - I love it too. They should've had it back when they first designed GPOs as an upgrade from the old NT group policy way...bit I guess better late than never. And, just a friendly reminder - there are those of us out here (me) who are she's, not he's, regardless of the gender-free online naming.
ASKER
Sorry for showing my inner caveman.... :)
It's nice to see she's who know what they're talking about !!
It's nice to see she's who know what they're talking about !!