!"#$%#$&'' !"#$"%#&' (' )*+, %*/'01#'23%40%*/'2*"%$5*6#*0' 7' 8,+**%*/'95:0%*/';$5:<4' =' 8,+**%*/'95:0%*/';$5:<'>5:*?+$%#4' @' 8,+**%*/'A#44+/#'B,5&' (@' 8,+**%*/'C5**#D05$4'>#0&##*'95:0%*/'' ;$5:<4' 7E' F#65*40$+0%5*G'C$#+0%*/'+'95:0%*/'' ;$5:<4'C5*0+%*#$' 7H' I+J')G'F#4%/*%*/'+'95:0%*/'K5<5,5/-' LE' I+J'>G'M6<,#6#*0%*/'+'95:0%*/'K5<5,5/-' LN' I+J'F%4D:44%5*' =O' ' Module 4: Designing a Routing Topology Information in this document is subject to change without notice. The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted. Complying with all applicable copyright laws is the responsibility of the user. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microsoft Corporation. If, however, your only means of access is electronic, permission to print one copy is hereby granted. 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.  2001 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, BackOffice, FrontPage, NetMeeting, Outlook, PowerPoint, SQL Server, Visio, Visual Studio, Win32, Windows, Windows Media, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries. Other product and company names mentioned herein may be the trademarks of their respective owners. ! "#$%&'!()!*'+, , !/!0#%1, !2#3#&#-4! ! ,,,! 5.+16%71#6!8#1'+! This module provides students with the knowledge required to design a routing topology for a Microsoft ® Exchange 2000 organization in an enterprise environment. After completing this module, students will be able to: !" Analyze the existing business environment and network infrastructure. !" Plan routing groups. !" Plan routing group boundaries. !" Plan message flow. !" Plan connectors between routing groups. "/1'6,/&+!/.$!96'3/6/1,#.! This section provides the materials and preparation tasks that you need to teach this module. 0':%,6'$!"/1'6,/&+! To teach this module, you need the following materials: !" Microsoft PowerPoint ® file 1573A_04.ppt !" The Connecting Routing Groups job aid. !" The Determining Routing Group Boundaries job aid. !" The Northwind Traders Case Study. !" The Fourth Coffee Case Study. 96'3/6/1,#.!2/+;+! To prepare for this module, you should: !" Read all of the materials for this module. !" Complete the labs and review the lab discussion questions. !" Review the Connecting Routing Groups job aid. !" Review the Determining Routing Groups Boundaries job aid. !" Review the Northwind Traders Case Study. !" Review the Fourth Coffee Case Study. The job aids are in the Exchange 2000 Design Tool located at C:\MOC\1573A\LabFiles\Exchange_2000_Design_Tool, and on the student compact disc. The case studies are in the Appendices and on the student compact disc. 96'+'.1/1,#.)!! <=>!",.%1'+! ! ?/@)! A>!",.%1'+! 8#1'! ,B! ! "#$%&'!()!*'+, , !/!0#%1, !2#3#&#-4! 5.+16%71#6!C'1%3!D#6!/!?/@! This section provides setup instructions that are required to prepare the instructor computer or classroom configuration for a lab. ?/@!EF!GH'67,+'!I)!J# '71, !1K'!0#%1, !L6#%3+! !" To prepare for the lab • Determine the destination server and the destination routing group based on your classroom setup. You must accomplish this task before students can perform this exercise. ?/@!EF!GH'67,+'!()!*,+/@&, !9%@&,7!M#&$'6!0'D'66/&+! !"To prepare for the lab • Determine the appropriate routing group connector for your students to configure based on the configuration that you determined for Lab B, exercise 3. You must accomplish this task before students can perform this exercise. ! "#$%&'!()!*'+, , !/!0#%1, !2#3#&#-4! ! B! "#$%&'!C16/1'-4! Use the following strategy to present this module: !" Analyzing the Existing Environment Discuss the aspects of a company’s existing environment that need to be analyzed before designing a routing group structure. Then, discuss how to assess current needs, and how to plan for future growth. !" Planning Routing Groups Explain how to plan routing groups. Discuss how to analyze link quality. Make sure that students understand how link quality affects a routing topology. Finish this topic by explaining the design issues that are related to the site design for Microsoft Windows ® 2000. !" Planning Routing Group Boundaries Explain the key considerations that are associated with planning routing group boundaries. Discuss the planning and design issues that are related to single and multiple routing groups, and make sure students understand when to use each structure. Next, focus on how to design routing groups that enable administrators to control the public folder referral process. Finish this topic by discussing the design considerations that are involved in developing a routing group naming strategy. !" Planning Message Flow Explain how companies can plan message flow by either configuring routing groups into a hub-and-spoke topology, or by using a full-mesh topology. !" Planning Connectors Between Routing Groups Explain how to plan connectors between routing groups. Begin by discussing when to use each type of connector. Make sure that students understand when to use a routing group connector, when to use a Simple Mail Transfer Protocol (SMTP) connector, and when to use an X.400 Connector. Next, focus on how to calculate connector costs, emphasizing the related exercise and the accompanying discussion that are provided in the module. Finish this topic by discussing situations in which planning additional connectors is appropriate. B,! ! "#$%&'!()!*'+, , !/!0#%1, !2#3#&#-4! J%+1#N,O/1,#.!5.D#6N/1,#.!! 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. ?/@!C'1%3! The following list describes the setup requirements for the labs in this module. C'1%3!0':%,6'N'.1!<! The labs in this module require the Northwind Traders Case Study and the following job aids and diagrams: !" Determining Routing Group Boundaries !" Connecting Routing Groups !" Physical Intranet Topology !" Physical Microsoft Active Directory ™ Topology C'1%3!0':%,6'N'.1!P! The labs in this module require the following: !" For each student, a Microsoft Management Console (MMC) custom console must be created. This custom console must include both the Active Directory Users and Computers snap-in and the Exchange System snap-in, and must be named your_firstname Console. !" For each student, a personalized user account must be created in the appropriate domain. This user account must be added to the Domain Admins group, and assigned a mailbox on the server running Exchange 2000 that the student is using. !" For each student, a user profile must be created on the student’s computer that enables the student to access their mailbox by using Microsoft Outlook ® 2000. !" An administrative group named Central Admin Group. !" Administrative roles must be delegated to each administrative group in Northwind Traders. ! "#$%&'!()!*'+, , !/!0#%1, !2#3#&#-4! ! B,,! ?/@!0'+%&1+! Performing the lab in this module introduces the following configuration changes: !" Six new routing groups are created within the Central Admin Group: RG1- NAmerica, RG1-SAmerica, RG1-Europe, RG1-Africa, RG1-Asia, and RG1-SPacific. !" The servers in each domain are moved from the Default Routing Group in the First Administrative Group to their assigned routing group in the Central Admin Group. !" Routing group connectors are configured to create a hub and spoke topology that uses the RG1-NAmerica routing group as the hub routing group. Each connector is configured as a two-way routing group connector. !" Each side of each routing group connector is configured so that none of the connectors allow public folder referrals. ! "#$%&'!()!*'+, , !/!0#%1, !2#3#&#-4! ! <! QB'6B,'R! ! S./&4O, !1K'!GH,+1, !G.B,6#.N'.1 ! 9&/ , !0#%1, !L6#%3+ ! 9&/ , !0#%1, !L6#%3!E#%.$/6,'+ ! 9&/ , !"'++/-'!M&#R ! 9&/ , !J# '71#6+!E'1R''.!0#%1, !L6#%3+ The ability to send and receive e-mail messages reliably is crucial to any company. An effective routing group topology outlines how many routing groups a company needs, where to locate each routing group, how messages will flow through the company, and how to connect the routing groups to one another. To design a routing group topology, architects must consider both the immediate and the future business needs of the company, the physical capabilities of the existing network environment, and the Microsoft ® Exchange 2000 messaging environment in which the routing groups will function. After completing this module, you will be able to: !" Analyze the existing business environment and network infrastructure. !" Plan routing groups. !" Plan routing group boundaries. !" Plan message flow. !" Plan connectors between routing groups. 2#3,7!Q@T'71,B'! !"#$%"&'()#*+#"&)%&'),#"-# ./)#0"(12)#."$'34#*+(# "56)3.'&)47! ?'/$U,.! 8+#./'4#0"(12)9#:"1#,'22#2)*%+# *5"1.#()4';+'+;#*#%"1.'+;# ;%"1$#."$"2";:#./*.#,'22# "$.'0'<)#:"1%#3"0$*+:=4# *5'2'.:#."#4)+(#*+(#%)3)'&)# 0)44*;)4#%)2'*52:7# P! ! "#$%&'!()!*'+, , !/!0#%1, !2#3#&#-4! S./&4O, !1K'!GH,+1, !G.B,6#.N'.1! Future Growth Future Future Growth Growth Examine Existing Mail Routes Examine Examine Existing Mail Routes Existing Mail Routes V#R!N/.4!+'6B'6+W XK'6'!/6'!1K'! +'6B'6+!&#7/1'$W V#R!/6'!1K'!+'6B'6+! 7# '71'$W Designing an effective routing topology requires a comprehensive understanding of the specific business needs of a company. Areas that deserve special attention are the administrative structure, the existing messaging topology, and future growth. M%1%6'!L6#R1K! Planning how you want your Exchange 2000 organization to function in the future affects how you plan your routing group topology now. Future growth must be considered in the design of message routing because, as an office grows and e-mail usage increases, the available network bandwidth can decrease. For example, you may need to place a satellite office that is a member of a large routing group into its own routing group, so that you can control message flow and resulting bandwidth utilization. Consider the following questions when designing routing groups: !" Is a remote office likely to expand or reduce its number of employees over the next year? !" Is another remote location likely to experience an increase in the frequency with which its employees send and receive e-mail? S$N,.,+16/1,B'!C16%71%6'! Another important consideration is the administrative structure of the Exchange 2000 organization. XK#!X,&&!S$N,.,+1'6W! In an Exchange 2000 environment, you must assign routing groups to specific administrative groups. As a result, you can assign specific administrators to specific routing groups based on the overall administrative structure of the organization. You can also modify the membership of any routing group at any time. 2#3,7!Q@T'71,B'! !"#"1.2'+)#./)#."$'34#%)2*.)(# ."#*+*2:<'+;#*#3"0$*+:=4# 514'+)44#)+&'%"+0)+.7# ?'/$U,.! >331%*.)2:#*+*2:<'+;#./)# -1.1%)#+))(4#"-#*#3"0$*+:9# *4#,)22#*4#./)'%#)?'4.'+;#*+(# $2*++)(#*(0'+'4.%*.'&)# 4.%13.1%)49#,'22#)+*52)#:"1#."# ()4';+#*#0"%)#) )3.'&)# %"1.'+;#."$"2";:7# [...]... !" Cost values range from 1-100 You can use cost values to configure primary and backup paths for message transfer These values are typically assigned based on the amount that each specific network link costs to install, maintain, and use For example, an X.400 Connector that uses a satellite link will cost more than a routing group connector that uses a T1 link !" Maintain a consistent relationship... topologies are a typical choice for smaller messaging environments The principal advantages of this topology are that message traffic between any two routing groups usually travels only a single hop, and that there are multiple alternate routes to each destination routing group should any of the connections fail You can use a full-mesh topology if you have full network connectivity between all routing. .. 2000 site as the server running Exchange 2000, all queries are passed to the global catalog server or domain controller in that site If a global catalog server is not available in that site, Exchange 2000 will query a global catalog server in a different site If you want to avoid using the same global catalog server for Exchange 2000 directory queries and client computer authentication, you can move... groups are usually based on the network topology, with fast and reliable networks links between locations functioning as the boundaries As a result, it often makes sense to name routing groups after the area that they service For example, if a routing group includes servers in the western region of North America, you could name that routing group North America West RG You probably do not want to name a routing. .. "#$%&'!()!*'+,-.,.-!/!0#%1,.-!2#3#&#-4! ! . routing because, as an office grows and e-mail usage increases, the available network bandwidth can decrease. For example, you may need to place a satellite. global catalog server or domain controller in that site. If a global catalog server is not available in that site, Exchange 2000 will query a global catalog