RE: Placement of computer objects in AD
From: Desmond Lee (mcp_at_donotspamplease.mars)
Date: 02/01/05
- Next message: Desmond Lee: "RE: AD User Objects & Permission Inheritance"
- Previous message: Cary Shultz [A.D. MVP]: "Re: new forest"
- In reply to: Ageing Brilliantine Stick Insect: "Placement of computer objects in AD"
- Next in thread: Jimmy Andersson [MVP]: "Re: Placement of computer objects in AD"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 31 Jan 2005 21:07:03 -0800
Segregation of computer and user objects into different OUs allows better
definition and application of Group Policy Objects (GPOs) to the intended
target. This can even be further broken down for granular control.
e.g.
domain.com
--- Servers OU
--------- File OU
--------- Terminal Server / Citrix OU
--------- Database Server OU
etc.
The GPO loopback feature is an option for consideration as well.
Do let us know if this helps. Thanks.
"Ageing Brilliantine Stick Insect" wrote:
> I have been advised that I shouldn't put computer objects in the same OUs as
> the people who will be using those computers. (I found the other day that
> some Group Policy settings weren't being applied to computers in our domain
> coz those computer objects were in the default 'Computers' OU in our
> AD.....seemed logical to put those computers in the same OUs as their users)
>
> Can anybody tell me why computers shouldn't be in the same OUs as their
> users, and does anybody know of any good articles on this subject?
- Next message: Desmond Lee: "RE: AD User Objects & Permission Inheritance"
- Previous message: Cary Shultz [A.D. MVP]: "Re: new forest"
- In reply to: Ageing Brilliantine Stick Insect: "Placement of computer objects in AD"
- Next in thread: Jimmy Andersson [MVP]: "Re: Placement of computer objects in AD"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|