• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Domain restructuring

rasczak

Lifer
I work on a dev project that currently has a lab with development and test servers that are networked under the same domain (ideally I would have setup separate domains but I inherited this). I've begun setting up a couple of machines to simulating the field systems/network. My question is this, would it be better at this point to:

a.) Have the three "networks" (all with their own subnet) set up under one domain placing each (development, test, field and subsequent workstations) in it's own OU?

or

b.) Restructure the domain so that the development, test and field networks have their own domains with the development domain being the parent and the test/field being child domains?

Other ideas are welcome. At this point the easy solution seems to just connect the "field" workstations and servers to the current domain and place them in their own OU and separating the test and development into separate OU's as well.
 
I would make a sub domain or completely different domain if I wanted to have said group of servers seperated security wise. If they dont need to be seperated security wise then keep them in a single domain.
 
Back
Top