|
Yes, I would definitely like to see that
script. From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Brian Desmond To a
certain extent is varies based on your business requirements. There are basic
things though: Computers Users Groups Contacts. My
standard for OUs is something like this CookieCutter
Division --Computes ----Workstations ----Laptops ----Servers --Users ----Employees ----Contractors ----Temporary --Groups --Contacts I let
people create OUs under the bottom most OU in each subtree and do whatever to
the relevant objects. I provision users centrally so I don't delegate exchange.
It's way easier to have some sort of central exchange provisioningysstem or
site rather than trying to delegate it. I have a
sript I wrote that creates the OU structure, groups, and delegates various
rights, you're welcome to a copy if you want it. You'll have to modify it for
your organization, but, it's a good start. From:
[EMAIL PROTECTED] on behalf of 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 Harding, Devon
- RE: [ActiveDir] OU Delegation Brian Desmond
- 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
- RE: [ActiveDir] OU Delegation al_maurer
- RE: [ActiveDir] OU Delegation Gil Kirkpatrick
- RE: [ActiveDir] OU Delegation neil.ruston
