Download ppt - 10.1 © 2004 Pearson Education, Inc. Exam 70-297 Designing a Microsoft ® Windows ® Server 2003 Active Directory and Network Infrastructure Lesson 10: Planning

10.1 © 2004 Pearson Education, Inc.

Exam 70-297 Designing a Microsoft® Windows® Server 2003 Active Directory and Network Infrastructure

Lesson 10: Planning the Site Structure

Goals Understand sites

Design a site structure

Understand operations masters

Place domain controllers




Sites

Logical representations of physical structure

Locations where all computers are well-connected

Well-connected means that all computers in a single site are connected by high-speed, reliable, and cost-effective links (such as a LAN)

Sites and site links have three main purposes

Controlling replication

Providing local logons

Controlling certain directory-enabled applications (Dfs)

Understanding Sites

(Skill 1)




Controlling replication

Types of replication

Intrasite

Occurs spontaneously based on database changes

Allows for fast database convergence, but can be chaotic and bandwidth-intensive

Intersite

Occurs between designated bridgehead servers according to a schedule and interval

Always compressed

Path can be influenced by modifying the costs associated with site links

Understanding Sites (2)

(Skill 1)




Site link properties

Sites participating in the link

Schedule upon which the link should be used

Interval in which replication will occur over the link

Cost for the link

Understanding Sites (3)

(Skill 1)




Figure 10-2 an example site link

(Skill 1)




Site design

An important aspect of overall Active Directory design

Components

Defining sites

Associating subnets with sites

Defining site links

Defining site link bridge

Defining preferred bridgeheads

Designing a Site Structure

(Skill 2)




Defining sites

In most networks, each physical location is its own site

If links between locations are fast, reliable, and inexpensive, may be able to combine more than one physical location into a single site

Designing a Site Structure (2)

(Skill 2)




Associating subnets with sites

Subnets are used to allow clients to determine the site to which they are connected in order to correctly locate local servers

Create and configure site links

Mirror physical connectivity

Specify site link properties: cost, schedule, and interval


(Skill 2)




Site link schedule

To define, analyze the physical link(s) between sites with a monitoring application to determine periods of peak activity and amount of available bandwidth during period

If link(s) have a low amount of available bandwidth during peak periods, configure a schedule for the site link that excludes peak periods


(Skill 2)




Site link bridging

Automatically enabled by default

Allows direct replication to occur between sites that do not have a dedicated site link


(Skill 2)




Preferred bridgeheads

Bridgeheads are the focus of intersite replication

Knowledge Consistency Checker

Creates connection objects only between bridgehead servers for intersite replication

You can provide KCC with a list of one or more preferred bridgehead servers


(Skill 2)




Figure 10-8 Automatic site link bridging allows replication from site A to site C

(Skill 2)




Figure 10-10 Specifying a preferred bridgehead

server

(Skill 2)




Flexible Single Masters of Operations (FSMOs)

Commonly referred to as operations masters

Two general types of functions

Forest-wide operations master roles

Schema master

Domain naming master

Domain-wide operations master roles

Primary domain controller (PDC) emulator

Relative identifier (RID) master

Infrastructure master

Understanding Operations Masters

(Skill 3)




Flexible Single Masters of Operations (FSMOs)

When you create the first domain in a new forest, all five operations master roles are assigned to the first domain controller in the domain

In child domains, only the domain-wide operations masters roles are assigned to the first domain controller in the domain

Understanding Operations Masters (2)

(Skill 3)




Domain controller placement

Goals

Ensure that logons are possible regardless of any single point of failure

Ensure that logons are performed locally whenever possible

Each site should contain at least one domain controller

To ensure local logons in case of any single point of failure, need two domain controllers

Placing Domain Controllers

(Skill 4)




Also analyze need for supporting servers

Global catalog server

DNS servers

DHCP servers

WINS server

Placing Domain Controllers (2)

(Skill 4)




Placement of FSMO roles

Assign two forest-wide roles to a high-uptime server

Assign schema master and domain naming master roles to a single domain controller

Always have at least one additional domain controller to act as a standby operations master

Assign both the RID master and PDC emulator roles to the same domain controller

Do not assign the infrastructure master role to a domain controller that is also a global catalog server if there is more than one domain

Placing Domain Controllers (3)

(Skill 4)




Figure 10-11 Planning forest-wide operations master roles

(Skill 4)




Figure 10-12 Planning domain-wide operations

master roles

(Skill 4)