! "#$%&'!()!*'+, , !/!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+!/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#
Không có nhận xét nào:
Đăng nhận xét