<div>
<div class="content wysiwyg-content">
We have an AD forest that covers 60+ sites, which is made up of 24 child domains attached to a root. <br />
<br />
Currently our AD site links do not represent our physical network layout. &nbsp;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.<br />

</div>
</div>


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.


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

Windows 2000 is an operating system for use on both client and server computers. It is the successor to Windows NT 4.0, and is the last version of Microsoft Windows to display the "Windows NT" designation. Four editions of Windows 2000 were released (Professional, Server, Advanced Server, and Datacenter Server) that shared a core set of features, including many system utilities such as the Microsoft Management Console. All versions of the operating system support NTFS 3.0, Encrypting File System, as well as basic and dynamic disk storage. The Windows 2000 Server family includes support for Active Directory services, Distributed File System and fault-redundant storage volumes.