|
You want to look at a couple of main
points
1. How do you plan to delegate the permisisons, I.E. the
groupings of machines, users, etc.
2. How do you play to do GPOs if at
all.
3. How is the administration really going to work. For
instance, if you use a provisioning system for managing users (highly
recommended) you don't generally want to delegate those to local OU admins but
instead keep them in a main OU that the provisioning system only has control to.
Why one domain and one root domain? I am not arguing one
way or the other, just curious for the reasoning.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Harding, Devon Sent: Wednesday, January 11, 2006 4:24 PM To: [email protected] Subject: [ActiveDir] OU Delegation We’re in the process of
consolidating 21 child domains into just one and one root. We want to
separate the divisions (domains) into different OUs. Is there a guide or
best practice out there on delegating admin permissions on OUs? Also,
we’ve got Exchange permissions to deal with too. Windows Systems
Engineer Southern Wine & Spirits
- BSG 954-602-2469
__________________________________ |
- RE: [ActiveDir] OU Delegation joe
- RE: [ActiveDir] OU Delegation Harding, Devon
- RE: [ActiveDir] OU Delegation joe
- RE: [ActiveDir] OU Delegation Brian Desmond
- RE: [ActiveDir] OU Delegation Harding, Devon
- RE: [ActiveDir] OU Delegation Chianese, David
- RE: [ActiveDir] OU Delegation Gil Kirkpatrick
- RE: [ActiveDir] OU Delegation al_maurer
- RE: [ActiveDir] OU Delegation joe
- RE: [ActiveDir] OU Delegation Rocky Habeeb
- RE: [ActiveDir] OU Delegation Gil Kirkpatrick
