Module 3: Designing a Site Infrastructure

Contents Overview Lesson: Gathering Data for Site Design Lesson: Creating a Site Design Lesson: Modifying a Site Design for Replication Lesson: Placing Domain Controllers Lesson: Placing Global Catalog Servers Lab A: Designing a Site Infrastructure 1 2 5 8 17 23 34

Lesson: Placing Single Operations Masters 30

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. 2003 Microsoft Corporation. All rights reserved. Microsoft, MS-DOS, Windows, Windows NT, Windows Server, Active Directory, BackOffice, Microsoft Press, MSDN, PowerPoint, Visio, and Windows Media are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Module 3: Designing a Site Infrastructure

iii

Instructor Notes
Presentation: 130 minutes Lab: 70 minutes This module provides students with the knowledge and skills necessary to design a site infrastructure. The module explains the type of data that must be gathered for a site design, how to create a site design, and how to modify a site design for replication. The module also describes how to design for the placement of domain controllers, global catalog servers, and single operations masters. After completing this module, students will be able to:
! ! ! ! ! !

Determine the information needed to design a site infrastructure. Create a site design. Modify the site design for replication. Determine the placement of domain controllers in the site design. Determine the placement of global catalog servers in the site design. Determine the placement of single operations masters in the site design.

Required materials

To teach this module, you need Microsoft PowerPoint file 2282A_03.ppt. Important It is recommended that you use PowerPoint 2002 or later to display the slides for this course. If you use PowerPoint Viewer or an earlier version of PowerPoint, all features of the slides may not be displayed correctly.

Preparation tasks

To prepare for this module:

! !

Read all of the materials for this module. Complete the practices and review the assessment questions. Whenever possible, anticipate alternative answers that students may suggest and prepare responses to those answers. Complete the lab, practice discussing the answers, and become familiar with the lab environment. Read the additional reading for this module, located under Additional Reading on the Web page on the Student Materials compact disc. Document your own suggested additional readings to share with the class.

Classroom setup

The information in this section provides setup instructions that are required to prepare the instructor computer or classroom configuration for a lab. The computers in the classroom should be set up in the configuration specified in the Customization Information section at the end of the Automated Classroom Setup Guide for Course 2282A, Designing a Microsoft Windows Server 2003 Active Directory and Network Infrastructure. No additional classroom setup is required to perform the lab in this module.

iv

Module 3: Designing a Site Infrastructure

How to Teach This Module

This section contains information that will help you to teach this module.

Lesson: Gathering Data for Site Design

This section describes the instructional methods for teaching this lesson. In this lesson, students learn that the first step in designing an effective Active Directory site topology is collecting information about the structure of the organizations existing network. The lesson describes how to create a location map and the various components that should be included in the location map. Begin this section by determining your students knowledge level about sites. Ask the class what a site is and what its purpose is. Remind them that sites are one or more TCP/IP subnets with highly reliable and fast network connections. Sites are represented in Active Directory as site objects, and as such, are part of the Active Directory logical structure. Sites are primarily used to control replication traffic and logon authentication traffic across wide area network (WAN) links. Existing network information Emphasize that, before you can plan for sites, you must know your starting point. This means you need a clear grasp of your organizations existing network infrastructure, particularly, the speed and available bandwidth for each WAN link. Remind students that, when gathering data from individuals and groups in their organization, verify that the information they obtain, particularly charts, location maps, and etc., which may have been prepared some time ago, is up to date. There is no practice for this lesson.

Guidelines for gathering data for site design

Practice

Lesson: Creating a Site Design

This section describes the instructional methods for teaching this lesson. This lesson describes how to use the information you have gathered about an organizations existing network to create a site design. Guidelines for choosing sites Guidelines for creating a site design Practice Emphasize that, in most cases, sites are based on location.

Explain the components that should be included in a site design. Reinforce the need to document WAN links, link types, speed and available bandwidth, and the locations they connect. There is no practice for this lesson. However, students will practice creating a site design in the practice at the end of Lesson: Modifying a Site Design for Replication.

Module 3: Designing a Site Infrastructure

Lesson: Modifying a Site Design for Replication

This section describes the instructional methods for teaching this lesson. This lesson explains how to modify a site design for replication purposes. Strategies for using site links and site link bridges, which enable replication traffic to flow between sites, are discussed. Strategies for site links Strategies for site link bridges Take enough time to make sure students have a good grasp of site link concepts, which are vital to site design. To help students better understand these strategies, consider drawing a diagram on the whiteboard representing several sites and how replication would occur between these sites by default when bridging of all site links is enabled. Then draw a diagram of sites in a configuration where it would be logical to disable default bridging of all site links and manually configure two or more site link bridges. Explain that you cannot associate a site with a specific physical WAN link. For example, suppose that you have two physical WAN links that connect Site A and Site B: a T1 line, and a 56 kilobits per second (Kbps) dial-up link that is used for backup. Students might think that they should have two site links with different costs, each assigned to a different WAN link. However, this is not true, because a site link cannot be associated with a specific physical WAN link. Consider drawing a diagram of this scenario on the whiteboard to aid the students understanding of this concept. Emphasize that when specifying a cost for each site link, the cost should be based on the available bandwidth between the sites during peak hours, not on the speed of the WAN link. Reinforce that, when possible, the default configuration for bridging of all site links should be used. Practice The slide for this practice contains a graphic depicting the connectivity between the different locations of Northwind Traders. In this practice, students create a site design for Northwind Traders, including site links, cost for each site link, replication schedule, and site link bridges when necessary. Student site design answers will vary. It is okay for students to have different designs, so long as they can justify their designs.

Guidelines for modifying a site design for replication

Lesson: Placing Domain Controllers

This section describes the instructional methods for teaching this lesson. This lesson moves on to the next step in the site design process: determining where to place domain controllers. Domain controller hardware requirements Guidelines for placing forest root domain controllers If students want more detailed information on sizing domain controllers, refer them to the Microsoft Windows Server 2003 Deployment Kit. Highlight the general guideline, which is to place one forest root domain controller in each site that hosts a data center and in each hub site.

vi

Module 3: Designing a Site Infrastructure

Guidelines for placing domain controllers

Explain that security must be considered when placing domain controllers. A domain controller should not be placed in a site if you cannot ensure its physical security; otherwise, any person who has physical access to the domain controller can attack the system. When discussing the number of domain controllers required in each site, point out that if fault tolerance is desired, an additional domain controller is required beyond the minimum number needed in the site. There is no practice for this lesson. However, students will practice designing for the placement of domain controllers in the practice at the end of Lesson: Placing Global Catalog Servers.

Guidelines for determining the number of domain controllers Practice

Lesson: Placing Global Catalog Servers

This section describes the instructional methods for teaching this lesson. This lesson explores the process of determining where to place global catalog servers in a site design to meet specific business requirements. Considerations for placing global catalog servers Guidelines for placing global catalog servers Take time to review universal group membership caching, which is a new feature in Microsoft Windows Server 2003.

Because many Windows Server 2003 networks use only a single domain, emphasize that in a single domain forest, all domain controllers should be designated as global catalog servers, because no additional disk space or replication traffic is required. In this practice, students create a design for the placement of domain controllers and global catalog servers for Northwind Traders. Student design answers will vary. It is okay for students to have different designs, so long as they can justify their designs.

Practice

Lesson: Placing Single Operations Masters

This section describes the instructional methods for teaching this lesson. This lesson begins by explaining that single operations masters are domain controllers that have been assigned one or more special roles in an Active Directory domain. The lesson describes strategies and guidelines for placing single operations masters in a site design. Roles of operations master Guidelines for placing forest-level single operations masters The information contained here is probably a review for most of your students, so you should be able to move quickly through this topic. When discussing the guideline to designate the second domain controller as the standby operations master, point out that this is a procedural step that administrators perform, not an actual physical configuration. The administrator identifies a domain controller that will take over the operations master role if the original operations master is down, and then must ensure that the standby operations master is a direct replication partner of the actual operations master.

Module 3: Designing a Site Infrastructure

vii

Guidelines for placing domain-level single operations masters Practice

Reinforce the best practice that calls for placing all three domain-level roles on a single domain controller in the domain so as to simplify administration. There is no practice for this lesson.

Lab A: Designing a Site Infrastructure

In this lab, students create a site design, determine where site link bridges might be required, and determine the placement of domain controllers, global catalog servers, and single operations masters in the site design for Tailspin Toys. After completing this lab, students will be able to:
! ! !

Create a site design. Determine where site link bridges might be required. Determine placement in the site design of: Domain controllers. Global catalog servers. Single operations masters.

Note To prevent confusion, at the start of the lab, remind students that in the practices they have been working with Northwind Traders, but in the labs they are working with Tailspin Toys. To begin the lab, open Microsoft Internet Explorer and then, on the Web page that appears, click the link for this lab. Play the video interview for students, and then instruct students to begin the lab with their lab teams. To enable students to complete this lab in a timely manner, and to help focus their design efforts, point out that:
!

The e-mail from Lisa Jacobson provides the specific tasks that must be accomplished in this lab. When designing for site links, students should not assign costs or schedules to the site links. When designing for the placement of domain controllers and global catalog servers in a site, students only need to determine whether the site requires a domain controller from a domain, but do not need to calculate the number of domain controllers and global catalog servers required.

Give students approximately 35 to 45 minutes to complete their designs. Then spend approximately 20 to 25 minutes discussing the students designs as a class. Student answers will vary. Because there are several possible site design solutions, there is no one correct solution. After the teams develop their site designs, ask one person from each team to draw their teams design on a whiteboard or flip chart. Then, you can discuss all of the teams designs as a class.

viii

Module 3: Designing a Site Infrastructure

Note The answer for Exercise 2 is provided to the instructor in the form of a table. This table is not provided to students because it assumes a particular number of forests, and specific forest names, which might or might not coincide with students designs. Important Each team will carry forward their site design solutions from this lab as they go forward and complete the subsequent labs in this course. Keep the teams drawings on the whiteboard or flip chart throughout the remainder of the course. General lab suggestions For general lab suggestions, see the Instructor Notes for the Module 1 lab titled Preparing to Design an Active Directory Infrastructure for Course 2282A, Designing a Microsoft Windows Server 2003 Active Directory and Network Infrastructure. Those notes contain detailed suggestions for facilitating the lab environment in this course.

Customization Information
This section identifies the lab setup requirements for a module and the configuration changes that occur on student computers during the labs. This information is provided to assist you in replicating or customizing Microsoft Official Curriculum (MOC) courseware. The lab in this module is dependent on the classroom configuration specified in the Customization Information section at the end of the Automated Classroom Setup Guide for Course 2282A, Designing a Microsoft Windows Server 2003 Active Directory and Network Infrastructure. Important Although no computer configuration changes occur on student computers during the labs, the information gathered and many of the solutions produced in a lab carry forward to subsequent labs in the course. Therefore, if this course is customized and all of the modules are not used, or they are presented in a different order, when the instructor begins a lab the instructor might need to provide students with a possible answer from the previous lab(s) to use as a starting point for the current lab.

Module 3: Designing a Site Infrastructure

Overview

*****************************ILLEGAL FOR NON-TRAINER USE****************************** Introduction Excessive network traffic might occur between remote locations if large amounts of data and directory information are frequently exchanged. Designing an appropriate site topology helps you better organize the Microsoft Windows Server 2003 network in your organization and optimize the exchange of data and directory information. The Microsoft Active Directory directory service uses sites to define both the physical and logical structure of the network. Sites are one or more Transmission Control Protocol/Internet Protocol (TCP/IP) subnets with highly reliable and fast network connections. Sites are represented in Active Directory as site objects, and as such, are part of the Active Directory logical structure. You can use sites to control workstation logon traffic, replication traffic, Distributed File System (DFS) topology, and File Replication service (FRS). Objectives After completing this module, you will be able to:
! ! ! ! ! !

Determine the information needed to design a site infrastructure. Create a site design. Modify the site design for replication. Determine the placement of domain controllers in the site design. Determine the placement of global catalog servers in the site design. Determine the placement of single operations masters in the site design.

Module 3: Designing a Site Infrastructure

Lesson: Gathering Data for Site Design

*****************************ILLEGAL FOR NON-TRAINER USE****************************** Introduction The first step in designing an effective Active Directory site topology is to consult your organizations networking team to collect information about the structure of your existing network. In this lesson, you will learn how to create a location map and list communication links and their available bandwidth, Internet Protocol (IP) subnets in each location, domains, and number of users for each domain in each location. After completing this lesson, you will be able to:
! !

Lesson objectives

Explain how the existing network infrastructure influences site design. Identify the relevant information needed to design a site infrastructure.

Module 3: Designing a Site Infrastructure

Existing Network Information

*****************************ILLEGAL FOR NON-TRAINER USE****************************** Key points Include the following information in the location map:
!

Document each geographic location that contains groups of computers that are interconnected by local area network (LAN) links with a speed of 10 megabits per second (Mbps) or higher. Document each physical communication link between locations, including the wide area network (WAN) link speed, and the available bandwidth of the WAN link during peak usage. Document each location of routers, switches, bridges, proxy servers, and other network devices.

Example

If your existing network infrastructure includes remote offices, you must determine the use of each WAN link, WAN link speeds, and the available bandwidth of each WAN link during peak usage. You can use this information to decide whether to deploy domain controllers in branch offices and also to determine how many Active Directory sites to create. Note You can use Windows Server 2003-based diagnostic applications, such as Network Monitor, to gather information about your network. You can also use troubleshooting and configuration software offered by OEMs or software vendors. You can then create physical and logical network diagrams by using a product such as Microsoft Visio or other diagramming software.

Additional reading

For more information about evaluating network infrastructures for Active Directory deployment, see Designing the Site Topology under Additional Reading on the Web page on the Student Materials compact disc.

Module 3: Designing a Site Infrastructure

Guidelines for Gathering Data for Site Design

*****************************ILLEGAL FOR NON-TRAINER USE****************************** Guidelines Use the following guidelines to gather data for your site design:
!

Consult your organizations networking group to obtain accurate information about the physical network topology. Document your geographic locations and communications links, and record this information on a location map. This information will help you design your site topology. Document IP subnets in each location. If you do not know the subnet mask and IP address in each location, consult your networking group. Sites are defined by the IP subnets that they contain. Document domain names and the number of users for each domain in each location. This information influences the placement of regional domain controllers and global catalog servers.

Additional reading

For more information about gathering data for site design, see Designing the Site Topology under Additional Reading on the Web page on the Student Materials compact disc.

Module 3: Designing a Site Infrastructure

Lesson: Creating a Site Design

*****************************ILLEGAL FOR NON-TRAINER USE****************************** Introduction After you gather data about your existing network, you are ready to create your site design. This lesson describes what information to include in a location map and provides guidelines for creating a site design. After completing this lesson, you will be able to:
! !

Lesson objectives

Choose sites based on the network information that you have gathered. Create a site design.

Module 3: Designing a Site Infrastructure

Guidelines for Choosing Sites

*****************************ILLEGAL FOR NON-TRAINER USE****************************** Introduction Guidelines Sites are typically limited to computers and IP subnets within a single geographical location. Sites are connected to other sites by WAN links. To begin your new site design, determine which geographical locations will be designated as sites. Use the location map you created earlier, along with these guidelines to determine whether to designate a geographical location as a site.
!

Create a site for each location in which you plan to place a domain controller. Create a site for a location if it contains a server that is running a site-aware application. For example, domain-based DFS uses site objects to locate the server that is nearest to a client. Do not create a site for a location that has no domain controllers or servers that host site-aware applications. Instead, consider adding the IP subnet or subnets for the location to another existing site. Add the locations subnets to the site for which the location has the highest available WAN link bandwidth. Specify which IP subnets will be assigned to each site. Subnets are used to determine site membership for all computers within the Active Directory forest.

Additional reading

For more information about creating a site design, see Designing the Site Topology under Additional Reading on the Web page on the Student Materials compact disc.

Module 3: Designing a Site Infrastructure

Guidelines for Creating a Site Design

*****************************ILLEGAL FOR NON-TRAINER USE****************************** Guidelines When documenting a site design, include the following information for each site:
!

The name of the site. This name will be used to create the site object in Active Directory. Sites are typically named after the geographical locations that they represent. The geographical location that the site represents. A list of the subnets that will be associated with the site. For each IP subnet, record the name that will be assigned to the subnet in Active directory, the IP address range for the subnet, and the subnet mask. The WAN links, link types, link speeds, available bandwidth, and the sites that the WAN links connect.

! !

Module 3: Designing a Site Infrastructure

Lesson: Modifying a Site Design for Replication

*****************************ILLEGAL FOR NON-TRAINER USE****************************** Introduction After you create a site design, you will need to modify the design for replication purposes. To accomplish this, you will need to design site links and site link bridges. After completing this lesson, you will be able to:
! ! !

Lesson objectives

Compare strategies for site links. Compare strategies for site link bridges. Modify a site design for replication based on relevant business requirements.

Module 3: Designing a Site Infrastructure

Strategies for Site Links

*****************************ILLEGAL FOR NON-TRAINER USE****************************** Introduction A site link is an Active Directory object that represents the physical connectivity between two or more sites. Site links enable replication traffic between sites. Site links are logical paths that Knowledge Consistency Checker (KCC) uses to establish a connection for Active Directory replication. After you create a site design, you need to specify how to map the physical network connections between sites. You can use the Default IP Site Link to connect all of your sites, or you can use site links to create a logical representation of your network infrastructure. The default IP site link When you create the first domain in a forest, Active Directory creates a site link named DEFAULTIPSITELINK. This site link includes the first site created in Active Directory, and uses the IP for replication. If all of your sites are interconnected by WAN links, and all of the WAN links have the same bandwidth capabilities, you can use the DEFAULTIPSITELINK to connect all of your sites. You should create new site links to represent the network topology connecting your sites if your WAN does not use a mesh topology, or if your WAN links have different speeds. You must create new site links in the following situations:
!

When to create new site links

Each group of three or more sites are interconnected by WAN links of the same speed. For example, if three sites are interconnected by a frame relay network or an Asynchronous Transfer Mode (ATM) network, you must create one site link to represent the connection between the three sites. Each pair of sites is connected by a WAN link. For example, if more than one WAN link is used to connect two sites, you must only create a single site link to represent the connectivity between the sites because site links cannot be assigned to a specific WAN link.

10

Module 3: Designing a Site Infrastructure

Choosing a replication protocol

You can use either remote procedure call (RPC) over IP or Simple Mail Transfer Protocol (SMTP) for site links. RPC over IP is the default protocol. You should use RPC over IP if you have reliable, direct IP connectivity among sites. You should only use SMTP when you do not have reliable direct IP connectivity between sites. You can only use SMTP to replicate the schema, configuration, and global catalog information between sites. You cannot use SMTP to replicate the domain partition. In addition, you must install and configure a certificate authority (CA) to use SMTP because all replication traffic over SMTP must be digitally signed. Each site link must be assigned a cost when it is created. If all of your WAN links are the same speed, you can assign the default cost of 100 to all of your site links. If your WAN links have different speeds, assign costs according to the following table:
Available bandwidth (Kbps) 9.6 19.2 38.4 56 64 128 256 512 1024 2048 4096 Site link cost 1042 798 644 586 567 486 425 378 340 309 283

Assigning costs to site links

Important The values in the table above are based on the amount of bandwidth available for replication during hours of peak usage, not on the speed of the WAN link itself. To calculate the cost of a site link, divide 1024 by the log of the available bandwidth as measured in kilobits per second (Kbps). Specifying the schedule You can control site link availability by setting a schedule on site links. Use the default schedule which allows replication at any time unless you specifically want to prevent replication during hours of peak WAN link usage to free up the WAN link for other traffic. When replication between two sites traverses multiple site links, the intersection of the replication schedules on all relevant links between the sites determines the connection schedule between the two sites. Configure the replication interval for each site link to indicate how often you want intersite replication to occur during times when the schedule allows replication. For example, if the replication schedule only allows replication between 12:00 A.M. and 6:00 A.M., and you are using the default replication interval of 180 minutes, replication can occur twice during the scheduled time. For more information about designing site links, see Designing the Site Topology under Additional Reading on the Web page on the Student Materials compact disc.

Specifying the interval

Additional reading

Module 3: Designing a Site Infrastructure

11

Strategies for Site Link Bridges

*****************************ILLEGAL FOR NON-TRAINER USE****************************** Introduction A site link bridge connects two or more site links. A site link bridge enables replication between sites that are connected by two or more intervening site links. By default, all site links are bridged so that any site can directly communicate with any other site, regardless of how many site links the replication traffic must cross. When creating a strategy for site link bridges, you must determine whether to use the default configuration or to disable bridging of all site links and create one or more site link bridges. Use the following recommendations to determine your site link strategy:
!

Key points

If your IP network is fully routed, use the default setting in which all site links are bridged. If your network is not fully routed, or if you have a complex network and want to control replication traffic between two or more separate groups of sites, you must disable the Bridge All Site Links option, and then configure two or more site link bridges. For example, your network consists of two or more groups of sites that are separated by a firewall and you only want to allow replication between the two sites that have a direct connection to the firewall to replicate with each other. You must disable the Bridge All Site Links feature and create two site link bridges, one on each side of the firewall. The only replication traffic that can go through the firewall will be between the two sites that are directly connected to the firewall, and that have a site link between them.

Additional reading

For more information about designing site link bridges, see Designing the Site Topology under Additional Reading on the Web page on the Student Materials compact disc.

12

Module 3: Designing a Site Infrastructure

Guidelines for Modifying a Site Design for Replication

*****************************ILLEGAL FOR NON-TRAINER USE****************************** Introduction When modifying a site design for replication, consider your WAN links, the available bandwidth on your WAN links, the maximum replication latency you want to have, and the complexity of your network. Use the following guidelines when creating a site link design:
!

Site link guidelines

Create site links to logically represent the connectivity between sites in your network. Create a single site link for a group of three or more sites if this group of sites is connected by a single WAN provider, such as an ATM network. Use RPC over IP for all site links. Do not use SMTP for site links unless your network is not reliably fully routed. Use the default replication schedule unless you want to prevent replication during hours of peak WAN link usage. Specify a cost for each site link that is based on the amount of available bandwidth between the sites during hours of peak usage, not on the speed of the WAN link.

Site link bridge guidelines

Use the following guidelines when creating a strategy for site link bridges:
! !

Use the default configuration for inter-site replication where possible. Disable bridging of all site links and then create a site link bridge for each group of sites if your network is complex or you want to control replication between specific groups of sites because of WAN link limitations or firewall configuration. Use a site link to connect a specific pair of sites, one from each group of sites. The two sites that are used as a connecting point between the groups of sites must each have a domain.

Module 3: Designing a Site Infrastructure

13

Designing to minimize replication latency

Maximum allowable replication latency is the maximum amount of time that you want to pass before a change that is made to an Active Directory object is replicated to all domain controllers. To determine the maximum replication latency for your design, add up the longest latency periods for each site link in the longest replication path. To determine the longest latency period for each site link, add the replication interval to the number of minutes in the longest time period during which replication is not scheduled to occur. Then, configure the replication schedule and the replication interval so that the amount of replication latency is less than or equal to the predetermined value. For example, if replication is only scheduled to occur between midnight and 6:00 A.M., and the replication interval is 180 minutes, the longest replication interval for the site link is 1080 minutes (18 hours times 60 minutes) plus 180 (the replication interval) for a total of 1260 minutes. If the maximum replication latency for your design is longer than your predetermined maximum allowable replication latency interval, you must modify the schedule and interval settings for your site links to reduce the maximum replication latency for your design to an acceptable period.

Additional reading

For more information about site design for replication, see Designing the Site Topology under Additional Reading on the Web page on the Student Materials compact disc.

14

Module 3: Designing a Site Infrastructure

Practice: Creating a Site Design

*****************************ILLEGAL FOR NON-TRAINER USE****************************** Introduction Company background In this practice, you will create a site design for Northwind Traders. Northwind Traders manufactures a line of network appliances that are designed to help companies improve their data transmission capabilities. Northwind Traders currently uses a Microsoft Windows NT 4.0 master domain model. In recent years, the company has undergone significant growth and expansion. The company expects substantial growth over the next three years, including growth in market share, revenue, and number of employees. In addition to opening two new offices, the executive management has committed to implementing a new Windows Server 2003 Active Directory design to meet the current and future needs of the company. The following table shows the geographical locations, the departments residing in each location, and the number of users in each of the locations.
Location Paris, France Departments represented Headquarters (HQ) Management staff Finance Sales Marketing Production Research Development Information Technology (IT) Los Angeles, CA, United States Sales Marketing Finance IT 1,000 Number of users 2,000

Module 3: Designing a Site Infrastructure (continued) Location Atlanta, GA, United States Departments represented Customer Service Customer Support Training Glasgow, Scotland Research Development Sustained Engineering IT Sydney, Australia Consulting Production Sales Finance 500 750 Number of users 750

15

IT department issues

Most of the companys computing services are hosted in the corporate HQ in Paris. Corporate IT department wants to have central control of passwords and security settings. The local IT department at the Los Angeles office wants to maintain control of its infrastructure without the interference from the corporate IT department. The local IT department at the Glasgow office demands that they have exclusive control over their own environment due to security concerns of their research and development data. Corporate management shares the security concern over the R&D data and wants to ensure that this data is not compromised. The graphic on the slide illustrates the connectivity between the different locations of the company. In addition, Los Angeles and Atlanta have virtual private network (VPN) connections through the Internet to headquarters in Paris. The following table summarizes the rest of the connectivity information about Northwind Traders.
Link Paris - Internet Paris - Glasgow Paris - Sydney Atlanta - Internet LA - Internet Type Dual, redundant E3 Fractional E1 E1 Broadband T1 Speed 34.368 Mbps 768 Kbps 2.048 Mbps 1.5 Mbps 1.544 Mbps Available bandwidth 10 Mbps 128 Kbps 32 Kbps 384 Kbps 56 Kbps

Connectivity

16

Module 3: Designing a Site Infrastructure

Practice

Based on the scenario, answer the following questions. Discuss your results as a class. 1. Draw a site map for Northwind Traders, including all site links that you will create. Indicate the cost that you will assign to each site link. In addition, specify the schedule information for site links that will not use the default schedule.

Create one site link for each WAN link or VPN connection. Set schedules on connections with less than 64 Kbps to ensure that these connections are not available for replication between 8 A.M. and 5 P.M. local time in each location that is connected by the site link. The local times are converted to Greenwich Mean Time (GMT) for standardization. The site link costs are calculated by using the formula that is provided in the module. This is just one possible answer. Other solutions could be created and justified by students. ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ 2. Will you disable bridging of all site links? If so, will you create any site link bridges? Answers may vary. However, one possible answer is to disable bridging of all site links due to the regional domain model and the limited availability of bandwidth on the WAN links. No need to create any site link bridges. ____________________________________________________________ ____________________________________________________________ ____________________________________________________________

Module 3: Designing a Site Infrastructure

17

Lesson: Placing Domain Controllers

*****************************ILLEGAL FOR NON-TRAINER USE****************************** Introduction After modifying your site design for replication, you must decide the locations and number of domain controllers that are required for each site, based on the business needs of your organization. After completing this lesson, you will be able to:
! !

Lesson objectives

Explain the hardware requirements for domain controllers. Determine the placement of forest root domain controllers in the site design based on relevant business requirements. Determine the placement of domain controllers in the site design based on relevant business requirements. Determine the number of domain controllers required for each site based on relevant business needs.

18

Module 3: Designing a Site Infrastructure

Domain Controller Hardware Requirements

*****************************ILLEGAL FOR NON-TRAINER USE****************************** Introduction The capacity of a domain controller determines the maximum number of users within a site that the domain controller can support, and the maximum size of the directory database that the server can contain. Domain controllers running Windows Server 2003 have essentially the same hardware requirements as domain controllers running Microsoft Windows 2000. Consider the following when choosing hardware for your domain controllers:
!

Hardware requirements

Number of processors. The number of processors required in a domain controller is dependent on the number of users within a site that will be authenticated by the domain controller. The following table lists the guidelines for determining the number of processors required.
Users to support 1 to 499 500 to 1,499 >1,500 Processor required 1 processor with a speed of 866 megahertz (MHz) or higher is required 2 processors with a speed of 899 MHz or higher is recommended 4 processors with a speed of 899 MHz or higher is recommended

Module 3: Designing a Site Infrastructure

!

19

Amount of disk space. The amount of disk space required to host the domain database is directly proportional to the number of users in the domain. The following table lists the guidelines for determining the amount of disk space required.
Drive Drive that will contain the Active Directory database and NTDS.dit Disk space required 0.4 gigabytes (GB) for each 1,000 users. Add approximately 50 percent of the size of each domains database to the disk space requirements if the domain controller is hosting the global catalog. A minimum of 500 megabytes (MB) available space A minimum of 500 MB available space A minimum of 1.5 GB to 2 GB available space

Drive that will contain the Active Directory transaction log files Drive that will contain the SYSVOL share folder Drive that will contain the Windows Server 2003 operating system files

Note Additional disk space is required if the domain controller will host an application directory partition. The amount of space required to host the Domain Name System (DNS) application partition was included in the formula for the per-user requirements listed earlier. To determine the amount of space required for any other application partition, consult with the developer of the application.
!

Memory Requirements. The amount of memory required in a domain controller is dependent on the number of users within a site that will be authenticated by the domain controller. The following table lists the guidelines for determining your memory requirements.
User 1 to 499 500 to 1,500 > 1, 500 Memory required 512 MB is required 1 GB is recommended 2GB is recommended

Additional reading

For more information about placing domain controllers, see Designing the Site Topology, and Planning Domain Controller Capacity under Additional Reading on the Web page on the Student Materials compact disc.

20

Module 3: Designing a Site Infrastructure

Guidelines for Placing Forest Root Domain Controllers

*****************************ILLEGAL FOR NON-TRAINER USE****************************** Guidelines Forest root domain controllers are needed to create trust paths for clients that need to access resources in domains other than their own. When placing forest root domain controllers in a site design, use the following guidelines:
!

If a site hosts a data center or is a hub, place a forest root domain controller in that site. If users in a domain need access to resources from another domain in the same site, and there is no reliable network connection between the domain in which the users are located and thee nearest site that hosts the forest root domain controller, you can either add a forest root domain controller in the site or create a shortcut trust between the two domains.

Additional reading

For more information about placing forest root domain controllers, see Designing the Site Topology under Additional Reading on the Web page on the Student Materials compact disc.

Module 3: Designing a Site Infrastructure

21

Guidelines for Placing Domain Controllers

*****************************ILLEGAL FOR NON-TRAINER USE****************************** Introduction Guidelines By placing domain controllers appropriately, you can minimize the amount of time required for authentication requests. Use the following guidelines to help you determine whether to place one or more domain controllers in a location:
!

Place domain controllers in a site if many users from the domain are in the site. This enables users within the site to use a local domain controller for authentication, instead of authenticating to a remote domain controller over a WAN link. Place domain controllers in a site if users from the domain will access siteaware applications that are located on servers within the site. The servers that host these applications can then perform authentications for users from a local domain controller. Place domain controllers in a site if users from the domain must be able to access local server-based shared resources when the WAN link is unavailable. If the WAN link is unavailable and no local domain controllers are available to process logon requests, users log on by using cached credentials and cannot access resources on any computers other than the one to which they are logged on. Place domain controllers in a site if it is a hub site, and users from branch offices must be able to log on to the domain over a WAN link if their local domain controller is not available, or if no local domain controller has been placed in the site. Do not place a domain controller in a site that has inadequate physical security or limited maintenance capabilities.

Additional reading

For more information on placing domain controllers, see Designing the Site Topology under Additional Reading on the Web page on the Student Materials compact disc.

22

Module 3: Designing a Site Infrastructure

Guidelines for Determining the Number of Domain Controllers

*****************************ILLEGAL FOR NON-TRAINER USE****************************** Introduction Use your site design to help you determine the number of domain controllers that you need for each domain that has users in a site. The number of users from a domain in a site is the primary determining factor for the number of domain controllers that are required. Use the following guidelines to aid you in your decisions:
!

Guidelines

To support 1,000 users or less in a site, only one domain controller is required. To support between 1,000 and 10,000 users in a site, a minimum of two domain controllers are required. To support more than 10,000 users, at least one domain controller for each 5,000 users is recommended. If fault tolerance is required in a site (for example, if users from a domain must be able to log on and access shared resources located on servers within the site even when there is a WAN link failure), an additional domain controller is required. If the site is a hub site, or if it is connected to a large number of other sites that host the same domain, add one domain controller for every 15 replication connections for the site to the domain.

Note Each domain should have a minimum of two domain controllers so that if one domain controller fails, there is still one domain controller for the domain. Additional reading For more information about placing domain controllers, see Designing the Site Topology, and Planning Domain Controller Capacity under Additional Reading on the Web page on the Student Materials compact disc.

Module 3: Designing a Site Infrastructure

23

Lesson: Placing Global Catalog Servers

*****************************ILLEGAL FOR NON-TRAINER USE****************************** Introduction Global catalog servers facilitate user logon requests and forestwide searches. In your design, you must plan where to place global catalog servers. This lesson describes considerations for placing global catalog servers to address business requirements. After completing this lesson, you will be able to:
! !

Lesson objectives

Identify considerations for placing global catalog servers. Place global catalog servers in a site design based on relevant business requirements.

24

Module 3: Designing a Site Infrastructure

Considerations for Placing Global Catalog Servers

*****************************ILLEGAL FOR NON-TRAINER USE****************************** Introduction To make informed decisions regarding the placement of global catalog servers, you must first understand how global catalog servers are used on the network, and then apply that information to your site design. During the logon process, a users universal group memberships must be enumerated. To accomplish this, the domain controller that authenticates the user must either be located in a site that has universal group membership caching enabled, or it must contact a global catalog server to obtain this information. If the domain controller is unable to contact a global catalog server, and if it has not previously cached the users universal group membership information, the users logon request will be denied. If the domain controller is not available to authenticate the user because of a hardware failure or a WAN link failure, and if the user has previously logged on to the computer, the user will be logged on using cached credentials. When a user logs on using cached credentials, the user is able to access resources on the local computer, but cannot access any shared resources on the network. What is universal group membership caching? Universal group membership caching is a new feature in Windows Server 2003 and can be enabled for any site. When it is enabled for a site, domain controllers in that site cache universal group membership information for users that log on to the domain controller. Additionally, every eight hours by default, the domain controller will update its cached information by contacting the nearest global catalog server. If a domain controller has a cached copy of the users universal group membership information, it authenticates the user by using the cached information, instead of contacting the global catalog server. Universal group membership caching can be used in place of a global catalog server in small sites to avoid the additional replication traffic that would occur if a global catalog server were placed in the site.

The logon process

Module 3: Designing a Site Infrastructure

25

Active Directory searches

When a user or administrator searches Active Directory to locate a shared folder, a printer, or another user, the users computer must contact a global catalog server to complete the search. Directory-aware applications also use the global catalog to locate specific information required by the application. For example, Microsoft Exchange Server 2000, and Microsoft Exchange Server 2003 query the global catalog server to resolve mailbox names to user account names. The number of queries to the global catalog can be significantly increased by implementing this type of application on your network.

Additional reading

For more information about placing global catalog servers, see Designing the Site Topology under Additional Reading on the Web page on the Student Materials compact disc.

26

Module 3: Designing a Site Infrastructure

Guidelines for Placing Global Catalog Servers

*****************************ILLEGAL FOR NON-TRAINER USE****************************** Introduction Placing the appropriate number of global catalog servers in each location will provide the best response for users when they log on to the network, or search the directory. When placing global catalog servers, use the following guidelines:
!

Guidelines

In a single-domain forest, designate all domain controllers as global catalog servers because no additional disk space usage or replication traffic is required. If there is a directory aware application located in the site, place a global catalog server in the site. If a large number of roaming users visit a site, place global catalog servers in that site. If a site has fewer than 100 users, consider enabling universal group membership caching for the site instead of placing a global catalog server in the site. If you have multiple domain controllers in a site, place at least two global catalog servers in the site.

Module 3: Designing a Site Infrastructure

27

Practice: Designing the Placement of Domain Controllers and Global Catalog Servers

*****************************ILLEGAL FOR NON-TRAINER USE****************************** Introduction Scenario In this practice, you will design the placement of domain controllers and global catalog servers for Northwind Traders. The IT staff at corporate HQ in Paris anticipates performing a good deal of searches on the information that will be contained within the Active Directory database. They have made this claim based on the amount of time spent searching the current master domain model for various resources and account information. Additionally, there are quite a few representatives from regional offices who roam the Paris headquarters. These roaming users will need to log on easily in Paris as well as at any other locations that they visit from time to time. The Sydney office plans to roll out a number of server-based, site-aware Microsoft Distributed Component Object Model (DCOM) applications which will require quick response time. For the detailed Northwind Traders scenario, see Practice: Creating a Site Design earlier in this module.

28

Module 3: Designing a Site Infrastructure

Practice

Based on the scenario, answer the following questions. Discuss your results as a class. 1. How many domain controllers would you place in each site? Why? Use the table below to complete your design.
Number of domain controllers in each site Domain Nwtraders.local AsiaPacific.nwtraders.local NAeast.nwtraders.local NAwest.nwtraders.local Corp.nwtraders.local RDNwtraders.local Glasgow.RDNwtraders.local Paris 2 1 1 1 3 1 1 Glasgow Sydney Atlanta Los Angeles 0 0 0 0 1 2 2 1 2 0 0 1 0 0 1 0 2 0 2 0 0 1 0 0 2 1 0 0

This is one possible answer. Students might create other solutions that are equally feasible. Paris will host one domain controller for every other domain to enable easy logon for traveling users from other locations when they are in Paris. It will also host three domain controllers for the corp.nwtraders.local domain, two for local authentication and a third one for managing replication to remote offices. For redundancy purposes, it will also host two domain controllers for the forest root domain (nwtraders.local). Glasgow will host 2 domain controllers for the RDNwtraders.local forest root domain and two for the Glasgow.RDNwtraders.local domain. Two domain controllers for each domain are required to support fault tolerance for Active Directory. Glasgow will also host one domain controller for the corp.nwtraders.local domain so that traveling users from headquarters can log on without using the WAN link. For the rest of the sites, each site will host two domain controllers for the local regional domain for fault tolerance, one domain controller for the forest root domain, and one domain controller for the corp.nwtraders.local domain to enable traveling users from headquarters to log on without using the WAN link. ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________

Module 3: Designing a Site Infrastructure

29

2. In which sites will you place global catalog servers? In which sites will you enable universal group membership caching? Use the table below to complete your design.
Number of global catalog servers for nwtraders.local forest 2 1 1 1 1 Number of global catalog servers for RDnwtraders.loca l forest 1 1 0 0 0 Enable universal group membership caching for site (Yes/No) No No No No No

Site Paris Glasgow Sydney Atlanta Los Angeles

To support local logon, each site will host one copy of the global catalog for nwtraders.local forest except for Paris. Paris will have two copies of the global catalog to support both the large number of users in the location and the amount of Active Directory searches that are performed by the local IT staff. ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________

30

Module 3: Designing a Site Infrastructure

Lesson: Placing Single Operations Masters

*****************************ILLEGAL FOR NON-TRAINER USE****************************** Introduction Single operations masters are domain controllers that have been assigned one or more special roles in an Active Directory domain. The domain controllers that are assigned these roles control specific changes to Active Directory, which must not be made on multiple domain controllers at the same time to avoid corrupting the directory. Examples of these operations include resource identifier allocation, schema modification, adding a domain to the forest, and certain infrastructure changes. This lesson describes strategies and guidelines for placing single operations masters in your design. Lesson objectives After completing this lesson, you will be able to:
! !

Identify the operations master roles. Place forest-level single operations masters in a site design based on relevant business requirements. Place domain-level single operations masters in a site design based on relevant business requirements.

Module 3: Designing a Site Infrastructure

31

Operations Master Roles

*****************************ILLEGAL FOR NON-TRAINER USE****************************** Introduction Active Directory supports multimaster replication of directory data, which means that any domain controller can accept directory changes and replicate the changes to all other domain controllers. However, it is impractical to perform certain changes, such as schema modifications, by using multimaster replication. For this reason, certain domain controllers, known as operations masters, are responsible for accepting requests for those changes. Operations master roles exist at both the domain and forest level. The illustration provides information about these roles and the services they provide. There are three single operations master roles that exist in each domain, the Primary Domain Controller (PDC) emulator, the relative identifiers (RIDs) master, and the Infrastructure master. All three roles are automatically assigned to the first domain controller that is installed in the domain. There are two forest-level roles that exist in each forest, the schema master and the domain naming master. These two roles are automatically assigned to the first domain controller in the forest. This domain controller is also automatically assigned the three domain-level roles for the forest root domain, and is designated as a global catalog server. For more information about types of operations master roles, see Designing the Site Topology under Additional Reading on the Web page on the Student Materials compact disc.

Types of roles

Domain-level roles

Forest-level roles

Additional reading

32

Module 3: Designing a Site Infrastructure

Guidelines for Placing Forest-Level Single Operations Masters

*****************************ILLEGAL FOR NON-TRAINER USE****************************** Guidelines When placing forest-level single operations master roles, use the following guidelines:
!

In a forest with a single domain, or in a multiple domain forest in which all domain controllers in the forest root domain are also global catalog servers: Leave all the operations master roles on the first domain controller that is created in the forest root domain. Designate the second domain controller that is created in the forest as the standby operations master. This is accomplished by identifying the domain controller that can serve as the standby operations master if the actual operations master fails, and ensuring that it is a direct replication partner of the actual operations master. No other configuration of the domain controller is required.

In a multiple domain forest in which one or more domain controllers in the forest root domain do not host the global catalog: Move all of the forest and domain-level operations master roles to a domain controller in the forest root domain that is not designated as a global catalog server, and ensure that this domain controller is never configured as a global catalog server. The best practice is to keep all of the roles on a single server. The roles need to be moved because the infrastructure master role should not be co-located on a domain controller that is also a global catalog server unless all domain controllers in the domain are designated as global catalog servers. Designate a third domain controller in the forest root domain as the standby operations master, and ensure that this domain controller is never configured as a global catalog server.

Additional reading

For more information about placing forest-level operations master roles, see Designing the Site Topology under Additional Reading on the Web page on the Student Materials compact disc.

Module 3: Designing a Site Infrastructure

33

Guidelines for Placing Domain-Level Single Operations Masters

*****************************ILLEGAL FOR NON-TRAINER USE****************************** Guidelines When placing domain-level single operations master roles, use the following guidelines:
!

Place all three domain-level roles on a single domain controller in the domain to simplify administration. Place the domain controller that hosts the three domain-level roles in the site that hosts the largest number of users in the domain. However, if the users are evenly distributed among several satellite sites, place the domain controller that hosts these roles in a hub site that is connected to the satellite sites. Always designate another domain controller in the same site to be the standby operations master. This provides the domain administrator with a predetermined domain controller to which roles can be quickly transferred or seized as needed. If the server that hosts the three domain-level roles is not a global catalog server, the standby operations master should not be a global catalog server either. Leave the three domain-level roles on the first domain controller in the domain if all domain controllers in the domain will host the global catalog. Leave the three domain-level operations master roles on the first domain controller and verify that the first domain controller is never configured as a global catalog server if any domain controllers in the regional domain will not host the global catalog. When placed on a server that is a global catalog server, the infrastructure master cannot identify inconsistencies in cross-domain references because it has all objects in its directory database. For this reason, the three domainlevel roles should not be placed on a server that is also a global catalog server unless all domain controllers in the domain are global catalog servers.

34

Module 3: Designing a Site Infrastructure

Lab A: Designing a Site Infrastructure

*****************************ILLEGAL FOR NON-TRAINER USE****************************** Objectives After completing this lab, you will be able to:
! ! !

Create a site design. Determine where site link bridges might be required. Determine placement in the site design of: Domain controllers. Global catalog servers. Single operations masters.

Scenario

You have been hired as a consultant to create a site design for Tailspin Toys. The lab uses an interactive application to convey scenario-based information to help you complete the site design. To begin this lab, open Internet Explorer, and then, on the Web page that appears, click the link for this lab. View the video, read the e-mail message and other company documents, and then, using the exercises below as a guide, complete the tasks that are assigned in the e-mail message.

Estimated time to complete this lab: 70 minutes

Your instructor will break the class into groups to do the lab. Each group should be prepared to present their design to the class at the end of the lab.

Module 3: Designing a Site Infrastructure

35

Exercise 1 Creating a Site Design

In this exercise you will create a site design for Tailspin Toys, including all of its subsidiaries and new acquisitions. Use the information you have gathered in previous labs and the new information presented in the scenario to create your site design. For business reasons, Tailspin Toys is willing to redesign its WAN links only if required to support Active Directory replication. In the space below, draw a site design for Tailspin Toys and its subsidiaries and acquisitions. In your site design, indicate:
! ! !

The geographic locations that you will designate as sites. The site links that will be required. Whether to use the default setting to bridge all site links or to create site link bridges.

Answers may vary; the drawing below represents one possible answer in which there are nine sites. Other possible site designs can be created and justified given the information that is available to students in the lab scenario. Design for geographic locations that will be designated as sites: In the answer below, because each location of Tailspin Toys is geographically separated from other locations, each location is designated as a site. Design for site links: In the answer below, because New York is the headquarters for Tailspin Toys and functions as the hub for Tailspin, it has a site link to every site except Wicklow and Singapore. Site links are not needed from New York to Wicklow because Wicklow is linked to a nearby, larger site within the same domain. New York does not need a site link to Singapore because Singapore is connected to Fayetteville and has a site link to Fayetteville. Whether to use default setting to bridge all site links or to create site link bridges: The possible answer below uses the default setting to bridge all site link because the Tailspin Toys network is fully routed.

36

Module 3: Designing a Site Infrastructure

Module 3: Designing a Site Infrastructure

37

Exercise 2 Designing for the Placement of Domain Controllers, Global Catalog Servers, and Single Operations Masters
In this exercise you will design for placement of domain controllers, global catalog servers, and single operations masters in your site design for Tailspin Toys, including all its subsidiaries and new acquisitions. Use the information you have gathered in previous labs and the new information presented in the scenario to complete this exercise. Create a design for the placement of domain controllers, global catalog servers, and single operations masters in your site design. You might find it helpful to use the worksheet below to organize your design. When necessary, you can also modify the worksheet below to accommodate your design.
Domain-level single operations masters (Yes/No) Forest-level single operations masters? (Yes/No)

Site name

Domain(s) represented by domain controllers in this site

Global catalog server(s)

38

Module 3: Designing a Site Infrastructure

Answers may vary; the table below represents one possible answer. Many other possible answers can be justified given the information that is available to students in the lab scenario. In addition, there is not enough detailed information to calculate the specific number of domain controllers and global catalog servers required for each site. Placement of domain controllers in the site design: In the answer below, because the New York site is the companys headquarters location, and because the Finance department is primarily located in New York, the New York site hosts the Tailspin forest root domain, the Tailspin domain, and the Finance domain. In addition, because New York is the headquarters location, it hosts a domain controller from every other domain in the Tailspin forest. Each of the other sites hosts one or more domain controllers from the domain to which the users in that site belong to facilitate local authentication of users. For example, the Wicklow site hosts a domain controller for the Contoso domain. In addition, because the Istanbul and Monterrey sites also have Finance department personnel, each of these sites hosts a domain controller for the Finance domain. To enable members of the Finance department to access resources in other domains, a domain controller from the Tailspin forest root domain is placed in the Istanbul site and in the Monterrey site. Placement of global catalog servers in the site design: In the possible answer below, each site requires at least one global catalog server for the Tailspin forest to facilitate user logon. In addition, because Finance department personnel are based in New York, Istanbul, and Monterrey, a global catalog server for the Finance forest is required at each of these three sites to facilitate user logon. Placement of single operations masters in the site design: In the possible answer below, the domain-level single operations masters for each domain are placed in the site that contains the most users from the domain. All the forest-level single operations masters are placed in the New York site, because the IT department is based in New York.

Module 3: Designing a Site Infrastructure

39

Placement of domain controllers, global catalog servers, and single operations masters in the site design:
Domain-level single operations masters? (Yes/No) Yes Yes Yes No No No No No No No Yes No No Yes No No Yes No No Yes No Forest-level single operations masters? (Yes/No) Yes No Yes No No No No No No No No No No No No No No No No No No Global catalog server for the Tailspin forest in this site? (Yes/No) Yes Global catalog server for the finance forest in this site? (Yes/No) Yes

Site name New York

Domain(s) represented by domain controllers in this site Tailspin forest root domain Tailspin domain Finance domain Wingtip domain Contoso domain Trey domain Fabrikam domain Tailspin domain Tailspin domain Tailspin domain Wingtip domain Wingtip domain Tailspin domain Contoso domain Contoso domain Tailspin forest root domain Trey domain Finance domain Tailspin forest root domain Fabrikam domain Finance domain

Fayetteville Singapore Dublin Wicklow Osaka Kobe Istanbul

Yes Yes Yes Yes Yes Yes Yes

No No No No No No Yes

Monterrey

Yes

Yes

THIS PAGE INTENTIONALLY LEFT BLANK