I have been reading through the AD articles in here and still have a fog going about Sites compared to Child Domains.
I have been using a Windows 2012 R2 Domain and Functional level to manage a mini private cloud.
We wanted to make sure that users from one child domain could not see anything of any other child domains. We used segregated networking and child domain configs to accomplish this.
Having to stick an ADC in each Child domain is getting cumbersome and we want to convert to model that will allow for the same security segregation but central management.
I have kicked around the idea of separate OU's containing Computers and Users, but didn't think this was isolated enough.
Then I looked at Sites and this was more promising but revealed that I don't really understand the concept behind Sites as well as the benefits and pitfalls of them.
As I was reading through the articles here, I kept seeing reference to Child Domains being sort of pushed to the side in favour of a new model but couldn't connect the security isolation concept of a child domain to either an OU or a Site.
Is there anything or anywhere I cold go to get a much more in depth understanding of how and when to use either OU's or Sites?
make sure that users from one child domain could not see anything of any other child domains
? What exactly don't you want them to see or access?