Tài liệu Module 1: Introduction to Microsoft Exchange 2000 docx

„#Enhanced Site Administration Explain how the Exchange Server 5.5 Site concept is now separated into routing groups, administration groups, and policies.. # 0RGXOH#4=#,QWURGXFWLRQ#WR#0L

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

 2000 Microsoft Corporation All rights reserved

Microsoft, MS-DOS, MS, Windows, Windows NT, Active Directory directory service, ActiveX, BackOffice, FrontPage, Hotmail, MSN, Outlook, PowerPoint, SQL Server, Visual Studios, and Win32, are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A and/or other countries

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

Other product and company names mentioned herein may be the trademarks of their respective owners

Project Lead: David Phillips

Instructional Designers: Lance Morrison (Wasser), Janet Sheperdigian, Steve Thues

Lead Program Manager: Mark Adcock

Program Manager: Lyle Curry, Scott Hay, Janice Howd, Steve Schwartz (Implement.Com), Bill Wade (Wadeware LLC),

Graphic Artist: Kimberly Jackson, Andrea Heuston (Artitudes Layout and Design)

Editing Manager: Lynette Skinner

Editor: Elizabeth Reese (Write Stuff)

Copy Editor: Ed Casper (S&T Consulting), Carolyn Emory (S&T Consulting), Patricia Neff

(S&T Consulting), Noelle Robertson (S&T Consulting)

Online Program Manager: Debbi Conger

Online Publications Manager: Arlo Emerson (Aquent Partners)

Online Support: Eric Brandt

Multimedia Developer: Kelly Renner (Entex)

Compact Disc Testing: Data Dimensions, Inc

Production Support: Ed Casper (S&T Consulting)

Manufacturing Manager: Bo Galford

Manufacturing Support: Rick Terek

Lead Product Manager, Development Services:

Lead Product Manager: David Bramble

Group Product Manager: Robert Stewart

in greater detail later in the course

At the end of this module, students will be able to describe the new features and

To teach this module, you need the following material:

• Microsoft PowerPoint® file 1569A_01.ppt 3UHSDUDWLRQ#7DVNV#

To prepare for this module, you should:

• Read all of the materials for this module

LY# # 0RGXOH#4=#,QWURGXFWLRQ#WR#0LFURVRIW#([FKDQJH#5333#

0RGXOH#6WUDWHJ\#

Use the following strategy to present this module:

„#Exchange 2000 Product Goals Briefly discuss the key Exchange 2000 product goals

„#Microsoft Windows® 2000 Integration Focus on the new relationship with the Active Directory™ directory service and Internet Information Services (IIS)

„#Enhanced Site Administration Explain how the Exchange Server 5.5 Site concept is now separated into routing groups, administration groups, and policies

„#Reliable, Scalable Platform Discuss these features in terms of reliability and scalability, rather than their other benefits

„#Unified Collaboration Platform Give students a sense of the collaboration elements that work together to provide a complete platform

At the end of this module, you will be able to:

„#List the key Exchange 2000 product objectives

„#Describe the Exchange 2000 reliance on Active Directory

„#Explain how the site model has changed to an administration and routing model in Exchange 2000

„#Explain how Exchange 2000 is reliable and scalable

„#List the features and functions that support collaboration activities

products use MMC as well, so the administrative interface is unified across server applications

(QKDQFHG#6LWH#$GPLQLVWUDWLRQ#

In addition to simplified user administration, servers running Exchange are easier to manage in Exchange 2000 Routing groups and administrative groups provide flexibility to group well-connected servers for message transfer purposes, but still provide administrative permissions on a set of servers independent of connectivity

# 0RGXOH#4=#,QWURGXFWLRQ#WR#0LFURVRIW#([FKDQJH#5333# # 6#

5HOLDEOH/#6FDODEOH#3ODWIRUP#

Exchange 2000 continues to provide transaction logging with up-to-the-minute rollback recovery, just as it did in previous versions New to the product is the ability to configure multi-node clustering, which provides fault tolerance in the case of a system failure and ensures that users experience limited server outages

To provide greater scalability, many functions have been separated Depending

on server load requirements, certain processes can run together on a single server or be moved to multiple servers For example, protocols have been removed from the Information Store service and can be run on a separate server

A front-end/back-end server model can be established, if necessary, to provide a unified namespace in one server, the front-end, but support many thousands of users on the back-end servers Or several front-end servers can feed messages to

a single back-end server

Finally, a major new feature that supports both scalability and reliability is the concept of storage groups You can now configure multiple stores on a single server, providing flexibility and better recovery mechanisms for large sites 8QLILHG#&ROODERUDWLRQ#3ODWIRUP#

Exchange 2000 allows integration with Microsoft Office 2000 by providing event hooks that allow developers to extend Exchange 2000 The Web Store provides a solid platform for collaboration needs, by combining several key functions in a single location

Similarly, protocol support has moved from Exchange services into Internet Information Services (IIS)

Finally, the Exchange System Manager is an MMC console It can be added to MMC along with the Active Directory Users and Computers snap-in, in addition to any other console, to provide a single administration tool

# 0RGXOH#4=#,QWURGXFWLRQ#WR#0LFURVRIW#([FKDQJH#5333# # 8#

,QWHJUDWLRQ#ZLWK#$FWLYH#'LUHFWRU\#

Exchange 2000

Information StoreMTASystem Attendant

Information StoreMTASystem Attendant

Exchange 5.x

Exchange 5.x

Directory ServiceInformation StoreMTASystem Attendant

Directory ServiceInformation StoreMTASystem Attendant

Windows 2000

Active Directory

All Exchange 2000 directory information (including mailboxes, information about servers, and so on) is stored in Active Directory The Active Directory forest defines the boundaries of the Exchange organization Therefore, it is possible to host many distinct namespaces in the same Active Directory forest and Exchange organization However, because Active Directory defines boundaries, it is not possible to have a single Exchange organization span multiple un-trusted Active Directory domains

Active Directory stores data for a large and customizable set of objects In fact, the Active Directory database engine is based on Extensible Storage Engine (ESE), which is the database engine for Exchange 2000 information store Integration with Active Directory provides increased system performance and manageability while making directory management easier Some of the benefits

of Active Directory include the following:

„#Centralized object management Unified administration of Exchange 2000

and Windows 2000 directory objects will allow an administrator to manage all user data in one place, with one set of tools

„#Simplified security management Native Windows 2000 discretionary access

control lists (DACLs) are used in the Exchange 2000 information store Thus, a single set of security groups will apply to data stored in

Exchange 2000 in addition to Windows 2000 file shares

„#Creation of one distribution list Security groups in Windows 2000 can be

automatically used as distribution lists, removing the need to create a parallel set of distribution lists for each department or group

„#Easier access to directory information Lightweight Directory Access

Protocol (LDAP) is the preferred access protocol for directory information

9# # 0RGXOH#4=#,QWURGXFWLRQ#WR#0LFURVRIW#([FKDQJH#5333#

,QWHJUDWLRQ#ZLWK#,QWHUQHW#,QIRUPDWLRQ#6HUYLFHV#

Exchange 2000

Information StoreMTA

Information StoreMTA

IIS

SMTPPOP3IMAP4NNTPHTTP-DAV

SMTPPOP3IMAP4NNTPHTTP-DAV

In Exchange 2000, the protocols have been removed from the Information Store service and run as part of the IIS process By incorporating the protocols into IIS, system architects may host protocols on a different server, or multiple servers, than the server on which the Information Store service runs This means that IIS is now required for Exchange 2000 to function

Developers built large public e-mail systems by separating components onto different servers Separating the components also increases the reliability of Exchange organizations of any size, by isolating system failures in one server

In the case of Exchange 2000, the protocols can be run on a separate server or servers so that any protocol failure would not affect the Information Store service or Active Directory

The following protocols are supported by IIS for use with Exchange 2000:

„#Simple Mail Transfer Protocol (SMTP)

„#Post Office Protocol 3 (POP3)

„#Internet Message Access Protocol (IMAP)

„#Network News Transfer Protocol (NNTP)

„#Hypertext Transfer Protocol – Distributed Authoring and Versioning authoring and versioning (HTTP-DAV or Web-DAV)

This information is covered in greater detail in course 1569A module 4,

“Exchange 2000 Architecture,” and module 8, “Managing Virtual Servers and Protocols in Exchange 2000.”

„#The user object combines users and mailboxes

„#The group object combines groups and distribution lists

„#The contact object combines contacts and custom recipients

Exchange System Manager manages all Exchange 2000 settings and tasks In addition, you can add separate snap-ins that manage specific Exchange 2000 objects Using these various snap-ins allows you to customize MMC to include only the Exchange 2000 functions to which you need access

;# # 0RGXOH#4=#,QWURGXFWLRQ#WR#0LFURVRIW#([FKDQJH#5333#

The following table shows the available snap-ins

Snap-in Description

authenticate messages that have been digitally signed

This information is discussed in greater detail in course 1569A module 7,

“Managing Server Objects in Exchange 2000.”

1RWH#

# 0RGXOH#4=#,QWURGXFWLRQ#WR#0LFURVRIW#([FKDQJH#5333# # <#

‹# (QKDQFHG#6\VWHP#$GPLQLVWUDWLRQ#

6HDWWOH 6LWH 0LDPL 6LWH

Exchange 5.5 Sites

/RQGRQ 6LWH

7RN\R 6LWH

5RPH 6LWH

Exchange 2000 Routing Groups

Exchange 2000 Routing Groups

86$

5RXWLQJ

*URXS

/RQGRQ 5RXWLQJ#*URXS

5RPH 5RXWLQJ#*URXS

7RN\R 5RXWLQJ#*URXS

3ROLF\#$GPLQLVWUDWLYH#*URXS 86#$GPLQLVWUDWLYH#*URXS (XURSHDQ#$GPLQLVWUDWLYH#*URXS

Exchange 2000 Administrative Groups

Exchange 2000 Administrative Groups

Exchange 2000 Policies

Exchange 2000 Policies

The site concept in previous versions of Exchange Server defined three boundaries:

„#Single-hop routing between well-connected servers running Exchange

„#A collective administration unit within an X.500-like directory

„#An administrative unit to which policies can be applied

In Exchange 2000, the site concept is separated into three distinct concepts: the

administrative group, the routing group, and system policies These three

concepts operate independently of each other, providing greater administrative flexibility

5RPH 5RXWLQJ#*URXS

7RN\R 5RXWLQJ#*URXS

A routing group is a collection of well-connected servers running Exchange As

with an Exchange Server 5.5 site, messages sent between any two servers within a routing group are routed directly from source to destination Point-to-point, 24-hour connectivity is required between servers running Exchange in the same routing group

Bridgehead servers operate with different connectors to transfer messages between routing groups, much like site connectors transfer messages between

sites in previous versions of Exchange A connector defined as a routing group connector identifies a logical path between routing groups Such a connector

must be created in both directions

A link state table is a database of information that stores the up/down status of a

server, in addition to the costs of the connections between servers This table provides the data for determining the route a message takes between servers and

is replicated between all servers in all routing groups The link state table replaces the Gateway Address Routing Table (GWART) The link state algorithm (LSA) determines actual message routes

Exchange 2000 uses SMTP as the primary messaging protocol This insures better interoperability between Exchange 2000, the Internet, and other messaging systems The use of SMTP also reduces the requirement for high-bandwidth between servers within a routing group, as was needed in earlier versions of Exchange The Remote Procedure Calls (RPCs) used in earlier versions required high bandwidth networks, but SMTP simply requires reliable connections

This information is covered in greater detail in course 1569A module 9,

“Creating and Managing Routing Groups in Exchange 2000.”

# 0RGXOH#4=#,QWURGXFWLRQ#WR#0LFURVRIW#([FKDQJH#5333# # 44#

$GPLQLVWUDWLYH#*URXSV#

6HDWWOH 0LDPL

/RQGRQ

7RN\R 5RPH

3ROLF\#$GPLQLVWUDWLYH#*URXS 86#$GPLQLVWUDWLYH#*URXS (XURSHDQ#$GPLQLVWUDWLYH#*URXS

An administrative group is a collection of Exchange 2000 Active Directory

objects that are grouped together for the purposes of permissions management The collection of administrative groups defines the administrative topology of

an organization An administrative group can contain zero or more routing groups, public folder trees, policies, monitors, servers, conferencing services, and chat networks

For example, if your organization has two distinct sets of administrators that manage two distinct sets of servers running Exchange, you could create two administrative groups containing these two sets of servers To establish your permissions, you would add the appropriate Microsoft Windows 2000 users and/or groups to the security settings on the two administrative groups

This information is discussed in greater detail in course 1569A module 7,

“Managing Server Objects in Exchange 2000.”

45# # 0RGXOH#4=#,QWURGXFWLRQ#WR#0LFURVRIW#([FKDQJH#5333#

3ROLFLHV#

6HDWWOH 0LDPL

/RQGRQ

7RN\R 5RPH

Policy usage is a way for administrators to define properties on a large set of objects by defining those properties on a single policy object You can set server, public store, and mailbox store policies Recipient policies are also available, but this policy currently allows you to set only one property, which is the proxy address for recipients

The main purpose of policies is to allow an administrator to define settings and parameters for the Exchange 2000 organization on as wide a scale as desired In previous versions of Exchange, settings affect either a single server or all of the servers within a site These earlier products do not allow the user to apply settings to all sites simultaneously, or to a select number of servers within the site Policies overcome this limitation When a parameter needs to be changed, the administrator can simply make the change on the policy to affect all servers (or mailbox stores or public folder stores) to which the policy is applied Administrators can be given permissions to define policies independently of permissions that they would need to administer servers in administrative groups After a policy is defined, it can be applied by an administrator who has permissions on the servers within a specific administrative group

This information is discussed in greater detail in course 1569A module 7,

“Managing Server Objects in Exchange 2000.”