Stage Four—Creating a Site Topology Plan

After analyzing your organization’s requirements, the first step in creating a TS windows 7 configuration topology plan is to define sites. The main purpose of a site is to physically group computers to optimize network traffic. In Active Directory, site structure mirrors the location of user communities. You must define a site for each of the following:
Each LAN or set of LANs that are connected by a high-speed backbone
Each location that does not have direct connectivity to the rest of the network and
is reachable only by using SMTP mail
The second step in creating a site topology plan is to place domain controllers. Because the availability of Active Directory depends on the availability of domain controllers, a domain controller must always be available so users can be authenticated. For optimum network response time and application availability, you must place at least
One domain controller in each site
Two domain controllers in each domain
In addition, you might need to place additional domain controllers in a site if
There are a large number of users in a site and the link to the site is slow or near capacity
The link to a site is historically unreliable or only intermittently available
The third step in creating a 70-680 practice test topology plan is to define a replication strategy. An effective replication strategy ensures efficient replication and fault tolerance. In this step you configure site links, which includes designating the method of replication transport, site link cost, replication frequency, and replication availability. You also have the option to specify preferred bridgehead servers.
The final step in creating a site topology plan is to place global catalog servers and operations masters within a forest. The end result of a site topology plan is a site diagram that includes site links and a site link table that provides details about site link configurations, as well as locations of domain controllers and operations masters roles. Depending on the needs of the organization, a site topology plan might also include a table that provides details about site link bridges and preferred bridgehead servers.
To read more about DNS, launch an Internet search engine and run a search for RFC 1034 and RFC 1035. Requests For Comments (RFCs) are the official documents of the Internet Engineering Task Force (IETF) that specify the details for new Internet specifications or protocols. RFC 1034 is entitled “Domain Names—Concepts and Facilities,” and free Microsoft practice tests is entitled “Domain Names—Implementation and Specification.”

Read more on Stage Four—Creating a Site Topology Plan…

How Information Is Replicated

Active Directory replicates information in two ways: intrasite (within a site) and 70-680 practice test. The need for up-to-date directory information is balanced with the limitations imposed by available network bandwidth.
Intrasite Replication Within a site, a Windows Server 2003 service known as the knowledge consistency checker (KCC) automatically generates a topology for replication among domain controllers in the same domain using a ring structure. The KCC is a built-in process that ains on all domain controllers. The topology defines the path for directory updates to flow from one domain controller to another until all domain controllers in the site receive the directory updates. The KCC determines which servers are best suited to replicate with each other, and designates certain domain controllers as replication partners on the basis of connectivity, history of successful replication, and the matching of full and partial replicas. Domain controllers can have more than one replication partner. The KCC then builds connection objects that represent free 70-680 test questions replication connections between the replication partners.
The ring structure ensures that there are at least two replication paths from one domain controller to another; if one domain controller is down temporarily, replication still continues to all other domain controllers, as shown in Figure 1-10.
The KCC analyzes the replication topology within a site every 15 minutes to ensure that it still works. If you add or remove a domain controller from the network or a site, the KCC reconfigures the topology to reflect the change.
When more than seven domain controllers are added to a site, the KCC creates additional connection objects across the ring structure so that if a change occurs at any one domain controller, replication partners are available to ensure that no domain controller is more than three replication hops from another domain controller, as shown in Figure 1-11. These optimizing connections are created at random and are not necessarily created on every domain controller.
Extensions to schema in a global catalog should be approached carefully. Schema extensions can have disastrous effects on large networks because the extensions cannot be deleted (only disabled) and because of the large amount of network Free MCSE PDF questions traffic generated as the extensions are synchronized throughout the forest.

Read more on How Information Is Replicated…