After now the domains are structured by OU´s in itself, comes now a part, which makes for most difficulties.

The Site configuration plays a very important role in a ADS with several locations, in order to make a smooth synchronisation possible of the Domain CONTROLLERs over the WAN connections.

A further important point, which is often ignored, as soon as more than one location exists, searches the Clients with boats the Domain CONTROLLER nearest over their DNS server.

If the Sites is not correctly configures, it can happen then already once that a Client gets a Domain CONTROLLER of another location, which straight is not very effective.

Resources should lie always in the proximity the user and/or Clients, geographically seen, however it looks in practice differently.

How does it look with Clients from remote locations, which do not have Domain CONTROLLER locally?

Completely simply, one registers the Subnet of the Clients, whose Domain CONTROLLER is to use her in the location.

If a location with Domain CONTROLLERs precipitates, it is no problem, the Client tries it also here then with a Domain CONTROLLER of the other locations.

They see thus, how important it is to accomplish the Site configuration correctly you can thereby also a Replikationstopologie specify, which Domain CONTROLLER synchronizes with whom and the Replikation to thus optimize.

This proceeding minimized also network traffic and is also necessary, if you only one domain with several Subnets or locations instaliert.

Table of contents:

01 Introduction
02 Setting-up of a Site configuration
03 Changing the standard configuration of the root Domain
04Creation of the further locations
05 Providing and assigns the Subnetze
06 Shifting the Domain CONTROLLERs
07 Adaptation of the Replikationsmethode
08 Adaptation the port address
09 Adaptation of the port address
10 imprint

Pages: 16 Size: 588 KB