I have
used this design before. They were generically under a server OU.
Under that, they were separated out by server functions.
Pros
- Apply generic server hotfixes (SUS), Service Packs (GPOs), or configs to servers.
- Since each function of computer generally has different admins (DB has DB admins, email has email admins) you can easily provide custom GPOs to the various server types.
Cons
- It make software distribution a little more difficult since the servers were not all located in one area.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 30, 2003 9:34 AM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] OUs by server function?
I am currently erdesigning our OU structure and was wondering:
Has anyone done an OU structure that accounts for server function i.e. file and print, web, database?
Was it useful? What other computer structures have you use successfully?
Michael Parent MCSE MCT
Analyst I - Web Services
ITOS - Systems Enablement
Maritime Life Assurance Company
(902) 453-7300 x3456
