fstinc
asked on
Organizational Units best practices for WSUS and structure in general
server: windows 2008 R2 domain controller
Is this a good way to structure my OU's and Objects?
headquarters(parent ou)
-computers(sub ou)
accounting(parent ou)
.james (user account object)
.lynn (user account object)
-computers (sub ou)
.james-pc (computer name object)
.lynn-pc (computer name object)
Right now my users are all under the default "users" folder. I want to start using scripts so I want to clean up AD and put users under their respective departments, setup WSUS, printer and network drive scripts for specific departments, etc...
is the above setup the recommended way? or will that have any implications now or int the future?
Is this a good way to structure my OU's and Objects?
headquarters(parent ou)
-computers(sub ou)
accounting(parent ou)
.james (user account object)
.lynn (user account object)
-computers (sub ou)
.james-pc (computer name object)
.lynn-pc (computer name object)
Right now my users are all under the default "users" folder. I want to start using scripts so I want to clean up AD and put users under their respective departments, setup WSUS, printer and network drive scripts for specific departments, etc...
is the above setup the recommended way? or will that have any implications now or int the future?
I would create OUs for users.
ASKER
isn't WSUS OU computer based thought?
what if i want different depts to have a different wsus policy?
what if i want different depts to have a different wsus policy?
The OU for users wasn't necessarily meant just for WSUS.
You can apply different WSUS policies to your depts if you choose.
You can apply different WSUS policies to your depts if you choose.
ASKER
without the computers being a sub object within the OU?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Why would you want multiple WSUS policies other than servers, workstations and maybe a test group???