I need assistance laying out an AD schema with plans for growth. Goal is to keep it simple.
Our company was recently purchased by another and we are merging the domains and setting up a new, clean, AD schema and group policy. Other than the DC and Exchange servers, both locations will maintain Citrix servers, Terminal servers, other member servers and computers. Between the two companies, we have approximately 64 servers and 500 users.
My plan is to break out the two companies under the single domain. Not using departments because I felt it would be too cumbersome. Each location OU would list its own OU'S for servers, computers, and users. Any servers (DC and Exchange) shared by both would be left at the root. Is this a good strategy or is there a better method? I was thinking the root would look much cleaner that way. How would you handle the other OU's, like Applications, Builds, Builtin, Citrix, etc? Move them under each location accordingly?
The current layout feels like spaghetti, and as I mentioned, I'm looking for help cleaning it up -- without breaking anything. Not sure if keeping the root clean is an attainable goal, any advice is greatly appreciated on this project.