Tài liệu Module 4: Designing a Routing Topology docx

!"#$%#$&''
!"#$"%#&' ('
)*+, %*/'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#
! "#$%&'!()!*'+, , !/!0#%1, !2#3#&#-4! ! I!

",H'$!"#$'!#6!8/1,B'!"#$'W!
Administrators can modify routing group membership without limitations
whenever Exchange 2000 is in native mode. If your Exchange 2000

organization is in mixed mode, all servers within each routing group must
belong to the same administrative group to which that routing group belongs.
However, you can also create multiple routing groups that include members
from the same administrative group.
GH,+1, !"'++/-, !2#3#&#-4!
Most enterprise environments will already have an existing messaging topology
in place. It is especially important to consider the available bandwidth between
existing routing boundaries. Because Simple Mail Transfer Protocol (SMTP) is
the default transport protocol for Exchange 2000, it may be possible to remove
existing routing boundaries and then to group these servers with lower
connectivity rates together. It is important to consider both the reliability of the
network connection and the other traffic that uses this connection.
(! ! "#$%&'!()!*'+, , !/!0#%1, !2#3#&#-4!

#
##
#
!
9&/ , !0#%1, !L6#%3+!
!
S./&4O, !?,.;!Y%/&,14!E'1R''.!?#7/1,#.+
!
S./&4O, !1K'!C,1'!*'+, !#D!X,.$#R+!P===


The next step in designing an effective routing topology involves planning
routing groups. Planning number of routing groups that your company needs
involves analyzing link quality and analyzing the site design of Microsoft
Windows
®

2000.
2#3,7!Q@T'71,B'!
!"#"1.2'+)#./)#."$'34#./*.#*%)#
%)2*.)(#."#$2*++'+;#%"1.'+;#
;%"1$47#
?'/$U,.!
@2*++'+;#%"1.'+;#;%"1$4#
%)A1'%)4#*+*2:<'+;#5"./#2'+B#
A1*2'.:#*+(#./)#4'.)#()4';+#"-#
C'+(",4#DEEE7#
! "#$%&'!()!*'+, , !/!0#%1, !2#3#&#-4! ! >!

S./&4O, !?,.;!Y%/&,14!E'1R''.!?#7/1,#.+!
North
America
London
Australia
256 KB
56 KB
T2
!
0'&,/@,&,14!#D!1K'!!!!
J# '71,#.
!
SB/,&/@&'!
E/.$R,$1K


Before you begin to design routing groups, make sure that you understand
where all physical offices and network links are located. This information will

help you identify the types of connectors to use when you separate servers into
multiple routing groups. Primarily, you need to consider both the reliability of
the connection and the available bandwidth across the connection.
0'&,/@,&,14!#D!1K'!J# '71,#.!
If your connection is intermittent or unreliable, you will be forced to define
routing group boundaries in such a way that servers in the same routing group
do not need to utilize the intermittent or unreliable link to communicate with
each other.
E/.$R,$1K!SB/,&/@&'!S76#++!1K'!J# '71,#.!
The bandwidth available across the connection is especially important to
consider when you are planning public folder access. Microsoft Outlook
®

Messaging Application Programming Interface (MAPI) clients use Remote
Procedure Calls (RPCs) to gain access to public folders. Because public folder
access within a routing group is random and cannot be limited to a specific
server, you may need to define multiple routing groups both in order to
accommodate public folder access and in order to avoid low bandwidth
connections.
In addition to public folder access, you must also consider the average size of
messages that will be sent between routing groups. By default, users can send
messages of any size between routing groups. If you have an unreliable or low
available bandwidth connection between two routing groups, consider including
message size limits in your design.
2#3,7!Q@T'71,B'!
!"#)?$2*'+#/",#./)#A1*2'.:#"-#
./)#2'+B4#5).,))+#2"3*.'"+4#
* )3.4#*#%"1.'+;#;%"1$#
."$"2";:7#
?'/$U,.!

>+*2:<'+;#2'+B#A1*2'.:#,'22#
/)2$#:"1#$2*+#/",#."#
3"++)3.#%"1.'+;#;%"1$47#
Z! ! "#$%&'!()!*'+, , !/!0#%1, !2#3#&#-4!

S./&4O, !1K'!C,1'!*'+, !#D!X,.$#R+!P===!
Windows 2000
Site 2
Domain
Controller
Global
Catalog
Windows 2000
Site 1
Domain
Controller
Global
Catalog
Exchange 2000 Routing Group


You do not need to base your routing group design on an existing Microsoft
®
Windows 2000-based site design. In Windows 2000, sites define which global
catalog server and which domain controller will service each directory query
that is sent by an Outlook client or by the server running Exchange 2000.
Y%'64!96#7'++!
If a global catalog server is available in the same Windows 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 the server
running Exchange 2000 and a global catalog server into a new, dedicated site.
This helps to optimize client application performance.
*'+, !J#.+,$'6/1,#.+!
Before deciding to map your routing groups in Exchange 2000 directly to your
Windows 2000 sites, you need to address the following considerations:
!"
Unless a routing group includes a server running Exchange Server 5.5,
Exchange 2000 uses SMTP between all servers within that routing group.
!"
Exchange 2000 will not typically have the same network requirements as
Windows 2000 does. You can design Exchange 2000 routing groups that
span multiple Windows 2000 sites.
!"
Regardless of the Windows 2000 site design, it is best to have as few
routing groups as possible in Exchange 2000. If you can meet your business
requirements by doing so, and if your Exchange 2000 organization is in
native mode, you can begin by using only one routing group; and then later,
if it becomes necessary, you can move servers into additional routing
groups.
2#3,7!Q@T'71,B'!
!"#)?$2*'+#/",#./)#4'.)#
()4';+#"-#C'+(",4#DEEE#
3*+#* )3.#*#%"1.'+;#;%"1$#
."$"2";:7#
?'/$U,.!
>2./"1;/#:"1#("#+".#+))(#."#
5*4)#:"1%#%"1.'+;#;%"1$#

()4';+#"+#*+#)?'4.'+;#4'.)#
()4';+9#./)%)#*%)#4)&)%*2#
()4';+#'0$2'3*.'"+4#./*.#:"1#
+))(#."#3"+4'()%7#
['4!9#,.1+!
F"1#3*+#()4';+#
G?3/*+;)#DEEE#%"1.'+;#
;%"1$4#./*.#4$*+#012.'$2)#
C'+(",4#DEEE#4'.)47#
#
H);*%(2)44#"-#./)#
C'+(",4#DEEE#4'.)#()4';+9#'.#
'4#5) )%#."#/*&)#*4#-),#
%"1.'+;#;%"1$4#*4#$"44'52)#
'+#G?3/*+;)#DEEE7#
! "#$%&'!()!*'+, , !/!0#%1, !2#3#&#-4! ! A!

!"
You cannot schedule message transfers between servers within the same
routing group. In order to schedule a transfer between two servers running
Exchange 2000, the servers need to located be in two separate routing
groups.
!"
In a Windows 2000 site, all server communication is remote procedure call
(RPC) based; whereas in an Exchange 2000 routing group running in native
mode, all communication is SMTP-based. RPC and SMTP have different
requirements for network bandwidth, reliability, and speed.


Converting an Exchange 2000 organization from mixed mode, the

default, to native mode creates an irreversible change in the Exchange 2000
organization. As a result, you will no longer be able to run Exchange Server 5.5
within the same Exchange 2000 organization, and you will not be able to use
the Exchange 5.5 Move Server Wizard.



J/%1,#.!
\! ! "#$%&'!()!*'+, , !/!0#%1, !2#3#&#-4!

#
##
#
!
9&/ , !0#%1, !L6#%3!E#%.$/6,'+!
!
['4!*'+, !J#.+,$'6/1,#.+
!
9&/ , !/!C, &'!0#%1, !L6#%3
!
9&/ , !"%&1,3&'!0#%1, !L6#%3+
!
*,+7%++,#.)!9&/ , !/!0#%1, !L6#%3!C16/1'-4
!
S77#NN#$/1, !9%@&,7!M#&$'6!0'D'66/&+
!
*'B'&#3, !/!0#%1, !L6#%3!8/N, !C16/1'-4


As is the case with many design decisions, there is no single formula to apply

when designing routing group boundaries. In Exchange 2000, you can create
and remove routing groups as needed; you can also dynamically alter group
membership. When designing routing group boundaries, it is important to
consider whether your company will use a single or a multiple routing group
structure, and also to consider both how to accommodate public folder referrals
and how to develop an effective naming strategy.
2#3,7!Q@T'71,B'!
!"#('43144#./)#$2*++'+;#
'441)4#%)2*.)(#."#()4';+'+;#
%"1.'+;#;%"1$#5"1+(*%')47#
?'/$U,.!
!/)%)#*%)#4)&)%*2#()4';+#
'0$2'3*.'"+4#."#3"+4'()%#
,/)+#()3'('+;#5).,))+#*#
4'+;2)#*+(#*#012.'$2)#%"1.'+;#
;%"1$#4.%13.1%)7#
! "#$%&'!()!*'+, , !/!0#%1, !2#3#&#-4! ! ]!

['4!*'+, !J#.+,$'6/1,#.+!
C'6B'6+!R,1K!+&#R!&,.;+!7/.!@'!
3/61!#D!1K'!+/N'!6#%1, !-6#%3
C'6B'6+!R,1K!+&#R!&,.;+!7/.!@'!
3/61!#D!1K'!+/N'!6#%1, !-6#%3
Routing
Group 1
56K
9%@&,7!D#&$'6!/77'++!7/.!@'!
/DD'71'$!@4!1K'!6#%1, !-6#%3
/67K,1'71%6'
9%@&,7!D#&$'6!/77'++!7/.!@'!

/DD'71'$!@4!1K'!6#%1, !-6#%3
/67K,1'71%6'
Routing
Group 1
Public
Folder
Routing
Group 2
Public
Folder
Routing Group
Connector
0#%1, !-6#%3+!/6'!$4./N,7F!/.$!
4#%!7/.!7K/ '!1K'!N'N@'6+K,3
/1!/.4!1,N'
0#%1, !-6#%3+!/6'!$4./N,7F!/.$!
4#%!7/.!7K/ '!1K'!N'N@'6+K,3
/1!/.4!1,N'
Routing Groups
First Routing Group
Connectors
Members
RG2
Connectors
Members


Whenever your company’s network infrastructure changes because network
links are being created or upgraded, you can also reconfigure the routing
network to take advantage of the changes. The only requirement for this is that

the Exchange 2000 organization must be running in native mode.
The most important factor to consider when you are planning routing group
boundaries is the stability of the network connections between the servers
running Exchange 2000. In a network environment in which network links are
prone to failure or to other problems, you should design a multiple routing
group structure. The key considerations to keep in mind when designing routing
groups are that:
!"
Servers with slow links can be part of the same routing group.
!"
Routing groups are dynamic, and you can change their memberships at any
time.
!"
Public folder access can be affected by the routing group architecture.

2#3,7!Q@T'71,B'!
!"#"1.2'+)#./)#B):#()4';+#
3"+4'()%*.'"+4#./*.#*%)#
%)2*.)(#."#$2*++'+;#%"1.'+;#
;%"1$#5"1+(*%')47#
?'/$U,.!
C/)+#:"1#*%)#$2*++'+;#
%"1.'+;#;%"1$#5"1+(*%')49#
:"1#014.#3"+4'()%#./)#
4.*5'2'.:#"-#:"1%#+).,"%B#
3"++)3.'"+47#
<=! ! "#$%&'!()!*'+, , !/!0#%1, !2#3#&#-4!

9&/ , !/!C, &'!0#%1, !L6#%3!
C'6B'6+!N%+1!@'&# !1#!1K'!+/N'!S71,B'!

*,6'71#64!$,6'71#64!+'6B,7'!D#6'+1
C'6B'6+!N%+1!K/B'!3'6N/.'.1!7# '71,B,14!1#!
'/7K!#1K'6
S&&!+'6B'6+!R,1K,.!1K'!6#%1, !-6#%3!N%+1!@'!
/@&'!1#!7# '71!1#!1K'!6#%1, !-6#%3!N/+1'6
2K'!D#&&#R, !7#.$,1,#.+!N%+1!'H,+1!D#6!+'6B'6+!6% , !
GH7K/ '!P===!1#!@'&# !1#!1K'!+/N'!6#%1, !-6#%3)
2K'!D#&&#R, !7#.$,1,#.+!N%+1!'H,+1!D#6!+'6B'6+!6% , !
2K'!D#&&#R, !7#.$,1,#.+!N%+1!'H,+1!D#6!+'6B'6+!6% , !
GH7K/ '!P===!1#!@'&# !1#!1K'!+/N'!6#%1, !-6#%3)
GH7K/ '!P===!1#!@'&# !1#!1K'!+/N'!6#%1, !-6#%3)


The following conditions must exist for servers running Exchange 2000 to
belong to the same routing group:
!"
All servers running Exchange 2000 must belong to the same Microsoft
Active Directory
™
forest and Exchange 2000 organization.
!"
All servers running Exchange 2000 must have permanent connectivity to
each other server.
!"
All servers running Exchange 2000 within the routing group must be able to
connect to the routing group master.
The routing group master is the only server in each routing group that
maintains the link state table. By default, the first server running
Exchange 2000 installed into a routing group becomes the routing group
master.

If the routing group master for a specific routing group becomes
unavailable, any server running Exchange 2000 located in that routing group
will not be able to provide updated link state information to the routing
group master. This means that servers running Exchange 2000 in the routing
group may make undesirable routing decisions. If you do not have reliable
connectivity between the routing group master and every other server
running Exchange 2000 in the routing group, the link state table may fail to
propagate correctly.

2#3,7!Q@T'71,B'!
!"#)?$2*'+#,/)+#*+#
*%3/'.)3.#3*+#$2*+#."#14)#*#
4'+;2)#%"1.'+;#;%"1$7#
?'/$U,.!
F"1#3*+#4'0$2'-:#
*(0'+'4.%*.'&)#*+(#+).,"%B#
"&)%/)*(#5:#14'+;#*#4'+;2)#
%"1.'+;#;%"1$#4.%13.1%)7#
! "#$%&'!()!*'+, , !/!0#%1, !2#3#&#-4! ! <<!

9&/ , !"%&1,3&'!0#%1, !L6#%3+!
8''$!$,/&U%3!7# '71,#.+!@'1R''.!+'6B'6+
8''$!1#!+7K'$%&'!N'++/-'!$'&,B'64
8''$!1#!36'B'.1!7&,'.1+!D6#N!%+, !/!XS8!&,.;!1#!
/77'++!3%@&,7!D#&$'6+
8''$!1#!$'D,.'!6#%1, !-6#%3+!D#6!/$N,.,+16/1,B'!
6'/+#.+
8''$!1#!/77#NN#$/1'!%.6'&,/@&'!&,.;+
8''$!1#!/77#NN#$/1'!,.+%DD,7,'.1!@/.$R,$1K
0'/+#.+!D#6!%+, !N%&1,3&'!6#%1, !-6#%3+)

0'/+#.+!D#6!%+, !N%&1,3&'!6#%1, !-6#%3+)
0'/+#.+!D#6!%+, !N%&1,3&'!6#%1, !-6#%3+)


Effective planning for multiple routing groups involves understanding both the
situations in which a multiple routing group structure is appropriate, and the
disadvantages that are associated with using multiple routing groups.
0'/+#.+!D#6!^+, !"%&1,3&'!0#%1, !L6#%3+!
There are several business situations that require at least two routing groups
within an Exchange 2000 organization. Design a multiple routing group
structure if you:
!"
Need dial-up connections between servers in your Exchange 2000
organization.
!"
Need the ability to schedule message delivery between servers or locations.
!"
Need to prevent clients in one physical location from using a Wide Area
Network (WAN) link to gain access to public folder content that is located
on servers in a different physical location.
!"
Need to define routing groups for internal administrative reasons.
!"
Need to identify intermittent or unreliable permanent links, which would
necessitate the addition of a routing group to accommodate those links.
!"
Need to increase bandwidth because the present bandwidth is not sufficient
to accommodate client application access to public folders or to
accommodate the flow of message traffic, forcing you to configure an
additional routing group.

2#3,7!Q@T'71,B'!
!"#)?$2*'+#,/)+#*+#
*%3/'.)3.#4/"12(#()4';+#
012.'$2)#%"1.'+;#;%"1$47#
?'/$U,.!
>2./"1;/#*#4'+;2)#%"1.'+;#
;%"1$#'4#$%)-)%*52)9#./)%)#
*%)#4)&)%*2#4'.1*.'"+4#'+#
,/'3/#3"0$*+')4#+))(#."#
'0$2)0)+.#*#012.'$2)#%"1.'+;#
;%"1$#4.%13.1%)7#
<P! ! "#$%&'!()!*'+, , !/!0#%1, !2#3#&#-4!

*,+/$B/.1/-'+!#D!"%&1,3&'!0#%1, !L6#%3+!
Having too many routing groups is problematic, because multiple routing
groups:
!"
Take more time to administer.
!"
Require more connectors.
!"
Require multiple hops. This means that more servers are involved in
processing each message, which increases server overhead.

! "#$%&'!()!*'+, , !/!0#%1, !2#3#&#-4! ! <I!

*,+7%++,#.)!9&/ , !/!0#%1, !L6#%3!C16/1'-4!
*'B'&#3!/!6#%1, !-6#%3!+16/1'-4!D#6!M#%61K!J#DD''!
H)2)&*+.#3*4)#4.1(:#-*3."%4

@"44'52)#4"21.'"+


Use the Fourth Coffee case study and the Determining Routing Group
Boundaries job aid to develop a routing group strategy for Fourth Coffee.
RELEVANT CASE STUDY FACTORS:
Fourth Coffee would like to control message flow between offices.
The information technology (IT) group has convinced the owners that
client application performance will be decreased if the users in all
offices must connect to mailbox servers that are located in Portland.

POSSIBLE SOLUTION:
Implement 5 routing groups, one for each office.
2#3,7!Q@T'71,B'!
!"#('43144#*#%"1.'+;#;%"1$#
4.%*.);:#-"%#I"1%./#J" ))7#
?'/$U,.!
K4)#./)#I"1%./#J" ))#3*4)#
4.1(:#*+(#./)#LM).)%0'+'+;#
H"1.'+;#N%"1$#O"1+(*%')4P#
6"5#*'(#."#()&)2"$#*#%"1.'+;#
;%"1$#4.%*.);:#-"%#I"1%./#
J" ))7#
<(! ! "#$%&'!()!*'+, , !/!0#%1, !2#3#&#-4!

S77#NN#$/1, !9%@&,7!M#&$'6!0'D'66/&+!
Public
Folder
Server 3
Routing

Group 1
Server 2
1. Server 3
2. Server 4
…
…
…
1. Server 3
2. Server 4
…
…
…
List of Replicas
List of Replicas
List of Replicas
Routing Group 2
Routing Group 3
Cost = 10
Public
Folder
Server 4
Routing Group Connector
Cost = 20
Routing Group Connector
M"#+".#*22",#$152'3#-"2()%#%)-)%%*247
Server 1
User


Public folder referral is a feature that enables you to provide users with access

to public folders in the event that the local public folder server either is down or
does not contain an instance of the requested public folder. In Exchange 2000,
this process occurs by default.
9%@&,7!M#&$'6!0'D'66/&!96#7'++!
The following steps outline the public folder referral process:

1. The user attempts to view the contents of a folder.
2. Store.exe retrieves the replica list of the requested folder.
3. If the replica exists on the local public folder server, and if the user has the
appropriate permissions, then the user gains access to the folder.
4. If the replica exists on another public folder server in the same routing
group, then the client is referred to that public folder server.
5. If no public folder server in the same routing group contains the requested
public folder content, then Exchange 2000 will refer the user's request
across the routing group connectors to another routing group that contains
the requested folder. The Store.exe process sorts the replica list by
connector cost, and will attempt to access the folder by using the least cost
route possible.

2#3,7!Q@T'71,B'!
!"#"1.2'+)#./)#) )3.4#"-#./)#
$152'3#-"2()%#%)-)%%*2#-)*.1%)#
"+#%"1.'+;#;%"1$#()4';+7#
?'/$U,.!
C/)+#()4';+'+;#:"1%#
%"1.'+;#;%"1$#4.%13.1%)9#:"1#
014.#B+",#/",#" )+#14)%4#
,'22#+))(#."#;*'+#*33)44#."#
$152'3#-"2()%4#./*.#"+2:#/*&)#
%)$2'3*4#'+#%)0".)#%"1.'+;#

;%"1$47#
!/)4)#4.)$4#0*$#."#./)#
*+'0*.)(#;%*$/'3#
*44"3'*.)(#,'./#./'4#."$'37#
! "#$%&'!()!*'+, , !/!0#%1, !2#3#&#-4! ! <>!

0#%1, !L6#%3!*'+, !E'+1!96/71,7'+!
Accommodating the public folder referral process means designing your
routing topology with the following best practices in mind:
!"
Locate public folders on servers that are in the same routing group as the
users’ mailboxes.
!"
Perform public folder referrals based on the connector cost that you define.
If you want to prevent MAPI clients from gaining access to remote public
folders that are located across WAN links, you will need to create an
additional routing group to contain the servers located across the link, and to
disable public folder referrals across that connection.

['4!9#,.1+!
Q."%)#$152'3#-"2()%4#"+#
4)%&)%4#./*.#*%)#'+#./)#4*0)#
%"1.'+;#;%"1$4#*4#./)#
0*'25"?)4#"-#./)#14)%4#,/"#
,'22#+))(#."#14)#./"4)#
-"2()%4#0"4.#-%)A1)+.2:7#
#
@)%-"%0#$152'3#-"2()%#
%)-)%%*24#5*4)(#"+#./)#
3"++)3."%#3"4.#./*.#:"1#

()-'+)7#
<Z! ! "#$%&'!()!*'+, , !/!0#%1, !2#3#&#-4!

*'B'&#3, !/!0#%1, !L6#%3!8/N, !C16/1'-4!
North America
South RG
North America
South RG
North America
West RG
North America
West RG
North America
Midwest RG
North America
Midwest RG
North America
East RG
North America
East RG


You should name routing groups in a consistent, logical manner to facilitate
easy management. Using non-descriptive names such as Routing Group 1 and
Routing Group 2 makes it difficult to identify the physical locations of the
servers in the group.
8/N, !?,N,1/1,#.+!
Each routing group name is limited to 64 characters. You can use dashes and
underscores when naming a routing group.
The following characters are not allowed in routing group names:

!"
# (number sign)
!"
; (semicolon)
!"
, (comma)
!"
“ ” (quotation marks)
!"
/ (slash mark)
!"
\ (backslash)
!"
< > (angle brackets)
!"
+ (plus sign)
!"
* (asterisk)

2#3,7!Q@T'71,B'!
!"#"1.2'+)#./)#$%"3)44#"-#
()&)2"$'+;#*#+*0'+;#
4.%*.);:#-"%#%"1.'+;#;%"1$47#
?'/$U,.!
8.#'4#'0$"%.*+.#."#()4';+#*#
%"1.'+;#;%"1$#+*0'+;#
4.%*.);:#./*.#'4#3"+4'4.)+.9#
2";'3*29#*+(#'+.1'.'&)7#
! "#$%&'!()!*'+, , !/!0#%1, !2#3#&#-4! ! <A!

0'7#NN'.$'$!8/N, !C16/1'-4!
It is a good idea to develop a naming strategy that is based on factors that will
not change at any time in the near future.
For example, you could use a regional naming strategy to name your routing
groups. A regional naming strategy allows you flexibility for future growth, as
well as easy identification of the locations of servers within the routing group.
Routing 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 group after a specific town,
because at some point in the future you may want to expand that routing group
to include one or more of the nearby towns.