PLANNING ACTIVE DIRECTORY SITES AND SERVER PLACEMENT

1
PLANNING ACTIVE DIRECTORY SITES AND SERVER
PLACEMENT

• Chapter 6

2
DESIGN TASKS
3
UNDERSTANDING SITES
4
SITES AND DOMAINS ARE INDEPENDENT
5
DESIGNING SITE BOUNDARIES
6
SITE DESIGN GUIDELINES
7
MORE SITE DESIGN GUIDELINES
8
DESIGNING A REPLICATION STRATEGY
9
SITE LINKS
10
SITE LINK PROPERTIES
11
ASSIGNING SITE LINK COSTS
12
SITE LINK BRIDGES
13
SITE LINK BRIDGE AND COST EXAMPLE
14
BRIDGEHEAD SERVERS
15
PLANNING A DOMAIN CONTROLLER STRATEGY
16
DETERMINING WHETHER A LOCATION NEEDS A DOMAIN
CONTROLLER
17
DETERMINING THE NUMBER OF REQUIRED DOMAIN
CONTROLLERS
18
PLACING FOREST ROOT DOMAIN CONTROLLERS
19
PLANNING FOR GLOBAL CATALOG SERVERS
20
PLANNING FOR OPERATIONS MASTER SERVERS
21
FSMO Role Placement

• Domain-level FSMO roles on one domain controller
• Place this domain controller in site with most
  users.
• Designate a stand-by domain controller to host
  FSMO roles in case the selected domain controller
  fails.
• If all domain controllers are hosting the global
  catalog, you can leave all domain-level roles on
  the original (first) domain controller.

22
DOCUMENTING THE DESIGN

• Site topology
• Domain controller planning
• Domain controller placement

23
SUMMARY

• When designing the site structure, you should
  know the company geography, WAN links, and link
  speed as well as link utilization statistics.
• Sites are used to control Active Directory
  replication, DFS, FRS, and logon traffic.
• Placing a domain controller in a site allows you
  to cut down on WAN utilization. As long as that
  benefit outweighs the burden of replication
  traffic and management, it is a good approach.

24
SUMMARY (continued)

• Site links are logical objects that represent
  physical connectivity. You can use site link
  bridges, costs, and site schedules to control
  intersite replication.
• FSMO role placement rules.