Title: PLANNING ACTIVE DIRECTORY SITES AND SERVER PLACEMENT
1PLANNING ACTIVE DIRECTORY SITES AND SERVER
PLACEMENT
2DESIGN TASKS
3UNDERSTANDING SITES
4SITES AND DOMAINS ARE INDEPENDENT
5DESIGNING SITE BOUNDARIES
6SITE DESIGN GUIDELINES
7MORE SITE DESIGN GUIDELINES
8DESIGNING A REPLICATION STRATEGY
9SITE LINKS
10SITE LINK PROPERTIES
11ASSIGNING SITE LINK COSTS
12SITE LINK BRIDGES
13SITE LINK BRIDGE AND COST EXAMPLE
14BRIDGEHEAD SERVERS
15PLANNING A DOMAIN CONTROLLER STRATEGY
16DETERMINING WHETHER A LOCATION NEEDS A DOMAIN
CONTROLLER
17DETERMINING THE NUMBER OF REQUIRED DOMAIN
CONTROLLERS
18PLACING FOREST ROOT DOMAIN CONTROLLERS
19PLANNING FOR GLOBAL CATALOG SERVERS
20PLANNING FOR OPERATIONS MASTER SERVERS
21FSMO 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.
22DOCUMENTING THE DESIGN
- Site topology
- Domain controller planning
- Domain controller placement
23SUMMARY
- 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.
24SUMMARY (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.