The secret to an efficient and error-free Active Directory infrastructure is a well-designed replication topology. While this can be easy to design in a simple network, a large, complex network presents a challenge.
Multiple network hubs make topologies complicated
Networks are typically some type of hub-and-spoke formation, with a central hub and links radiating out to remote sites. In fact, it's not uncommon to see networks with two or more hubs and the remote sites split between the two, with a link between them. Diagram 1 shows the basic concept of a multiple hub and spoke topology. Here there are three main hubs in Atlanta, Singapore and London, with two secondary hubs in Caracas and Calgary.
Active Directory Topology Diagram 1
[IMAGE]
Making the Active Directory topology design efficient
Designing the Active Directory topology efficiently is to construct it so that it takes advantage of the strengths and minimizes the weaknesses of the network. In a complex network, you are likely to have a number of different link speeds connecting remote sites, especially for European and Asian sites.
This type of network can be quantified in a tier-type Active Directory topology as shown in Diagram 1. In this example we have quantified the network link speeds connecting sites into three main groupings. At the top we have a "Core" site link containing the prime hub sites connected with the fastest lin
To continue reading for free, register below or login
To read more you must become a member of SearchWindowsServer.com
');
// -->

ks. I have seen anywhere from two to 10 sites in this link. The second tier would be the next fastest links and the third tier, the slowest links. Note how we have identified a hub site for each tier, and created individual site links from each remote site in the tier to the hub. To make this all work, we have to connect the hub sites together, so we create site links between the Tier 2 and Tier 3 hubs and between the Tier 1 and Tier 2 sites.
Active Directory Topology Diagram 2
[IMAGE]
In our example, this would force replication from Birmingham to Atlanta to go first to Denver, then to Richmond, then Atlanta. This would tell us that the network routing and link speeds would be such that it is the most efficient way to replicate the AD data. Of course, you could expand this configuration so that Singapore connected to Tier 2 sites in Asia and those sites connected to Tier 3 sites in Asia, and similarly for Europe and the London hub.
AD Replication Design best practices
The best practices for Replication Design include:
Of course there are lots of good examples of poorly designed topologies that had to be fixed by changing the design. We'll examine a couple of them in the next article.
Gary Olsen is a systems software engineer for Hewlett-Packard in Global Solutions Engineering. He authored Windows 2000: Active Directory Design and Deployment and co-authored Windows Server 2003 on HP ProLiant Servers.