Whats the best Active directory site design for an MPLS any-to-any ip network

We have an AD forest that covers 60+ sites, which is made up of 24 child domains attached to a root.

Currently our AD site links do not represent our physical network layout.  I have been given the job to sort this out. I am having trouble finding any information on the best way of recreating our physical MPLS any-to-any network in AD. The previous person who used to look after Active Directory created site links in a random sort of fashion which was just plain wrong. I am after some advice from anyone with experience in this sort of setup. My plan was to create a new server-less site representing the MPLS network cloud then connect all 60 + sites to the MPLS site. I would then assign replication costs and times to the site links based on the bandwidth of those connections. Once that had all been setup I would then start to remove all the old site links and I should be left with my ideal AD site link design. Would this work? Would the ISTG running on one of the domain controllers in each of the sites calculate the replication cost between different sites by using the MPLS site even though there is not a domain controller in it? I would be grateful for any advice on this matter.
LVL 1
adavidmAsked:
Who is Participating?
 
exx1976Connect With a Mentor Commented:
According to the Official MS way of doing things, I would have to advise against creating a site for the MPLS cloud.  Sites are logical representations of physical boundaries of a network.  Since there would be no client machines and no DCs in the MPLS site, it would be useless to create it, since replication doesn't traverse sites..  The machines would spend their time looking for machines that belong to that site (the MPLS site) that don't exist...  The boundaries of a site are as follows:

If two physical networks do not have a high speed link (defined by MS bas being <256k), or if they have an unreliable link, or if the link between two sites does not have 50% average available bandwidth.

I would simply create a site for each physical location, and add whatever subnets are in use at that location, and then create your site links accordingly.  If it were my network, I would create site links between all physical locations in a domain, and then site links from the sites containing the FSMO role holders for each domain to the site that contains the root domain FSMO role holders and DCs.

YMMV.

HTH,
exx
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.