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?
fstincAsked:
Who is Participating?
 
motnahp00Commented:
If you want to implement multiple WSUS policies you will need computer objects within their respective OUs.
0
 
motnahp00Commented:
I would create OUs for users.
0
 
fstincAuthor Commented:
isn't WSUS OU computer based thought?

what if i want different depts to have a different wsus policy?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
motnahp00Commented:
The OU for users wasn't necessarily meant just for WSUS.

You can apply different WSUS policies to your depts if you choose.
0
 
fstincAuthor Commented:
without the computers being a sub object within the OU?
0
 
DonNetwork AdministratorCommented:
Why would you want multiple WSUS policies other than servers, workstations and maybe a test group???
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.