Little background on our environment: we are a bank with approx 100 branches and three main office locations. In each main office location, the servers and workstations are on seperate subnets. Each branch is its own subnet, so the servers and workstations are in the same subnet per branch. Our server folk have seen the success we have been having with SCCM managing the desktops and would like to create their own server site. They would like this in its own SCCM architecture, as opposed to Primary Child site. In essence, they are trying to create two seperate SCCM Sites, in a single AD Forest, that has overlapping boundaries. I know that this is not supported. What does everyone else do, when the servers and workstations must be manged in seperate SCCM Sites? Thanks.--Joe.

This is what we do: We convince the server support team that having a separate site server isn't necessary. All security can be scoped at the Central primary site such that server support personnel cannot see workstation objects, and workstation support personnel cannot see server objects. I work at a bank, by the way.Standardize. Simplify. Automate.

To add to what Sherry said... Most companies that I see who start with this exact scenario soon realize that they are doing duplicate work and spending duplicate dollars so they end up collapsing the two sites into one site eventually. SCCM admins are not cheap having two seperate hierarchies because team A doesn't trust team B is a waste of money. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |