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

Module 1: Introduction
to Microsoft
Exchange 2000
&RQWHQWV##
2YHUYLHZ#

4#

([FKDQJH#5333#.H\#2EMHFWLYHV#

5#

:LQGRZV#5333#,QWHJUDWLRQ#

7#

(QKDQFHG#6\VWHP#$GPLQLVWUDWLRQ#

<#

5HOLDEOH/#6FDODEOH#3ODWIRUP#

46#

8QLILHG#&ROODERUDWLRQ#3ODWIRUP#

4<#

5HYLHZ#

57#

#


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


#

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

#

LLL#

,QVWUXFWRU#1RWHV#
3UHVHQWDWLRQ=##
93#0LQXWHV#
#

/DE=##
33#0LQXWHV#

This module provides students with an overview of the features and technology
changes between Microsoft® Exchange Server 5.5 and Microsoft
Exchange 2000. It describes the significant new features of Exchange 2000 in
addition to any feature improvements over Exchange Server 5.5. The module
covers this content at the highest conceptual level, introducing new features and
terminology. Particular emphasis is placed on a feature or technology that
affects several areas of the product. These new concepts or features are covered
in greater detail later in the course.
At the end of this module, students will be able to describe the new features and
benefits of Exchange 2000.

0DWHULDOV#DQG#3UHSDUDWLRQ#
This section provides you with the required materials and preparation tasks that
are needed to teach this module.

5HTXLUHG#0DWHULDO#
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.


#

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

#

4#

2YHUYLHZ#
6OLGH#2EMHFWLYH#

7R#SURYLGH#DQ#RYHUYLHZ#RI#
WKH#PRGXOH#WRSLFV#DQG#
REMHFWLYHV1#

„

([FKDQJH#5333#.H\#2EMHFWLYHV

/HDG0LQ#

„

:LQGRZV#5333#,QWHJUDWLRQ#

„

(QKDQFHG#6\VWHP#$GPLQLVWUDWLRQ

„

5HOLDEOH/#6FDODEOH#3ODWIRUP

„

8QLILHG#&ROODERUDWLRQ#3ODWIRUP

,Q#WKLV#PRGXOH/#\RX#ZLOO#OHDUQ#
DERXW#WKH#QHZ#IHDWXUHV#DQG#
LPSURYHPHQWV#LQ#0LFURVRIW#
([FKDQJH#5333#FRPSDUHG#
ZLWK#SUHYLRXV#YHUVLRQV1#

'HOLYHU\#7LS#

,Q#WKLV#PRGXOH/#\RX#ZLOO#
SURYLGH#DQ#RYHUYLHZ#DQG#
EULHI#GHVFULSWLRQ#RI#WKH#
IHDWXUHV#DQG#LPSURYHPHQWV#
WKDW#ZLOO#EH#GLVFXVVHG#LQ#
JUHDWHU#GHWDLO#WKURXJKRXW#WKH#
FRXUVH1#5HIUDLQ#IURP#
VSHQGLQJ#WRR#PXFK#WLPH#RQ#
WKH#VSHFLILFV#RI#DQ\#WRSLF1#

Microsoft® Exchange 2000 provides a reliable, scalable messaging platform that
also offers a full set of features and components to support collaboration. It is
tightly integrated with Active Directory™ directory service in Microsoft
Windows® 2000 and gains many administrative advantages by using the same
administration console.
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.


5#

#

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

([FKDQJH#5333#.H\#2EMHFWLYHV#
6OLGH#2EMHFWLYH#

7R#OLVW#DQG#EULHIO\#GLVFXVV#
WKH#PDLQ#([FKDQJH#5333#
SURGXFW#JRDOV1#

„

:LQGRZV#5333#,QWHJUDWLRQ

/HDG0LQ#

„

(QKDQFHG#6LWH#$GPLQLVWUDWLRQ

„

5HOLDEOH/#6FDODEOH#3ODWIRUP

„

8QLILHG#&ROODERUDWLRQ#3ODWIRUP

([FKDQJH#5333#LV#GHVLJQHG#

DV#D#UHOLDEOH/#VFDODEOH/#DQG#
VHFXUH#SODWIRUP#WKDW#LV#
LQWHJUDWHG#ZLWK#
:LQGRZV#53331#

Exchange 2000 was designed to meet several key product goals.

:LQGRZV#5333#,QWHJUDWLRQ#
Exchange 2000 reduces total administrative overhead by integrating completely
with Active Directory in Windows 2000. Mailbox options and network settings
are configured in one place by using one tool. Administration is performed in
Microsoft Management Console (MMC). Exchange 2000 includes several
consoles so that administrators can choose to work only with the objects they
need, rather than the entire Exchange System. Other Microsoft BackOffice®
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.


7#

#

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

‹# :LQGRZV#5333#,QWHJUDWLRQ#
6OLGH#2EMHFWLYH#

7R#JLYH#DQ#RYHUYLHZ#RI#WKLV#
WRSLF1#

/HDG0LQ#

([FKDQJH#5333#UHOLHV#
FRPSOHWHO\#RQ#$FWLYH#
'LUHFWRU\1#

„

,QWHJUDWLRQ#ZLWK#$FWLYH#'LUHFWRU\

„

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

„

2EMHFW#8QLILFDWLRQ#DQG#0DQDJHPHQW

Unlike earlier versions of Exchange Server, Exchange 2000 no longer has a

dedicated directory. Instead, Exchange 2000 integrates with Active Directory in
Windows 2000.
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\#
6OLGH#2EMHFWLYH#

7R#JLYH#D#EULHI#RYHUYLHZ#RI#
WKH#VFRSH#RI#LQWHJUDWLRQ#ZLWK#
$FWLYH#'LUHFWRU\1#

Exchange 5.x
Exchange 5.x
Directory Service
Directory Service

/HDG0LQ#

2QH#RI#WKH#PRVW#IDU0
UHDFKLQJ#QHZ#IHDWXUHV#LQ#
([FKDQJH#5333#LV#WKH#XVH#RI#
$FWLYH#'LUHFWRU\#WR#UHSODFH#
WKH#([FKDQJH#GLUHFWRU\1#

Exchange 2000
Exchange 2000
Information Store
Information Store
MTA
MTA
System Attendant
System Attendant

Information Store
Information Store
MTA
MTA

Windows 2000
Windows 2000

System Attendant
System Attendant

Active Directory
Active Directory

All Exchange 2000 directory information (including mailboxes, information
about servers, and so on) is stored in Active Directory. The Active Directory
7KLV#LQIRUPDWLRQ#LV#
forest defines the boundaries of the Exchange organization. Therefore, it is
GLVFXVVHG#LQ#JUHDWHU#GHWDLO#LQ#
VHYHUDO#PRGXOHV#WKURXJKRXW# possible to host many distinct namespaces in the same Active Directory forest
and Exchange organization. However, because Active Directory defines
WKH#FRXUVH1#
boundaries, it is not possible to have a single Exchange organization span
multiple un-trusted Active Directory domains.
'HOLYHU\#7LS#

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#
6OLGH#2EMHFWLYH#

7R#JLYH#DQ#RYHUYLHZ#RI#KRZ#
SURWRFROV#DUH#LPSOHPHQWHG#
LQ#([FKDQJH#53331#

IIS
IIS

/HDG0LQ#

$QRWKHU#LQFUHDVH#LQ#ERWK#
UHOLDELOLW\#DQG#VFDODELOLW\#LQ#
([FKDQJH#5333#LV#GXH#WR#
PRYLQJ#SURWRFROV#RXW#RI#WKH#
,QIRUPDWLRQ#6WRUH#VHUYLFH1#

Exchange 2000
Exchange 2000

SMTP
SMTP
POP3
POP3
IMAP4
IMAP4
NNTP
NNTP

Information Store
Information Store
MTA
MTA

HTTP-DAV
HTTP-DAV

)RU#
7KLV#LQIRUPDWLRQ#LV#FRYHUHG#

LQ#JUHDWHU#GHWDLO#LQ#PRGXOH#7/#
³([FKDQJH#5333#
$UFKLWHFWXUH/´#DQG#PRGXOH#;/#
³0DQDJLQJ#9LUWXDO#6HUYHUV#
DQG#3URWRFROV#LQ#
([FKDQJH#53331´#

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)

1RWH# 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.”


#

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

#

2EMHFW#8QLILFDWLRQ#DQG#0DQDJHPHQW#
6OLGH#2EMHFWLYH#

7R#JLYH#D#EULHI#RYHUYLHZ#RI#
0LFURVRIW#0DQDJHPHQW#
&RQVROH#+00&,1#

„

$FWLYH#'LUHFWRU\#8VHUV#DQG#&RPSXWHUV
z

„

*URXSV#FDQ#EHFRPH#GLVWULEXWLRQ#OLVWV

z

0LFURVRIW#0DQDJHPHQW#
&RQVROH#SURYLGHV#D#VLQJOH#
ORFDWLRQ#IRU#DGPLQLVWUDWRUV#WR#
SHUIRUP#DGPLQLVWUDWLYH#WDVNV#
RQ#DOO#0LFURVRIW#%DFN2IILFH#
SURGXFWV1#

1HWZRUN#DQG#PHVVDJLQJ#VHWWLQJV#DUH#ERWK#FRQILJXUHG#RQ#
XVHU#REMHFW

z

/HDG0LQ#

&RQWDFWV#UHSODFH#FXVWRP#UHFLSLHQWV

([FKDQJH#6\VWHP#0DQDJHU
z

0DQDJHV#([FKDQJH#5333#V\VWHP#REMHFWV

Several Active Directory objects have been unified with Exchange objects,
reducing the duplication of administrative tasks that used to be required in
7KLV#LQIRUPDWLRQ#LV#
previous versions of Exchange. The following objects maintain configuration
GLVFXVVHG#LQ#JUHDWHU#GHWDLO#LQ#
PRGXOH#:/#³0DQDJLQJ#6HUYHU# settings for both network access and messaging properties:
'HOLYHU\#7LS#

2EMHFWV#LQ#([FKDQJH#53331´#

„#

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

Exchange System Manager

Manage all aspects of an Exchange 2000 system.

Exchange Advanced Security

Digitally encrypt e-mail messages and
authenticate messages that have been digitally
signed.

Exchange Conferencing Services

Administrate the Exchange Conferencing
Service.

Exchange Folders

Administer Exchange public folder trees and
public folders.

Exchange Message Tracking Center

Track messages that have been processed by
Exchange 2000.

1RWH# This information is discussed in greater detail in course 1569A module 7,
“Managing Server Objects in Exchange 2000.”


#

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

#

‹# (QKDQFHG#6\VWHP#$GPLQLVWUDWLRQ#
6OLGH#2EMHFWLYH#

7R#JLYH#DQ#RYHUYLHZ#RI#WKLV#
WRSLF1#

6HDWWOH
86$
6LWH
5RXWLQJ
*URXS

/HDG0LQ#

7KH#FRQFHSW#RI#VLWHV#LQ#
SUHYLRXV#YHUVLRQV#RI#
([FKDQJH#6HUYHU#KDV#EHHQ#
UHSODFHG#E\#WKUHH#VHSDUDWH#
DGPLQLVWUDWLYH#HQWLWLHV1#

/RQGRQ
/RQGRQ
5RXWLQJ#*URXS
6LWH

5RPH
5RXWLQJ#*URXS
6LWH

0LDPL
6LWH

Exchange 2000
Exchange 2000
Exchange 5.5 Sites
Exchange 5.5 Sites
Administrative Groups
Routing Groups
Policies
Administrative Groups
Routing Groups
Policies

7RN\R

7RN\R
5RXWLQJ#*URXS
6LWH

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

'HOLYHU\#7LS#

7KH#DQLPDWLRQ#VWDUWV#ZLWK#D#
JUDSKLF#RI#DQ#([FKDQJH#
6HUYHU#818#RUJDQL]DWLRQ1#
(DFK#PRXVH#FOLFN#SURGXFHV#
WKH#IROORZLQJ#HIIHFWV=#
4,#([FKDQJH#6HUYHU#818#
6LWHV#GLVVROYHV#LQWR#
([FKDQJH#5333#URXWLQJ#
JURXSV1#
5,#6HUYHUV#FKDQJH#FRORUV#WR#
GHSLFW#WKUHH#GLIIHUHQW#
DGPLQLVWUDWLYH#JURXSV1#
6,#7KH#SROLF\#V\PERO#
DSSHDUV#RQ#HDFK#VHUYHU1#

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.

<#


43#

#

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

([FKDQJH#5333#0HVVDJH#5RXWLQJ#
6OLGH#2EMHFWLYH#

7R#GHILQH#WHUPV#UHODWHG#WR#
URXWLQJ#JURXSV1#

/HDG0LQ#

5RXWLQJ#JURXSV#GHILQH#D#VHW#
RI#ZHOO0FRQQHFWHG#VHUYHUV#
UXQQLQJ#([FKDQJH1#

86$
5RXWLQJ
*URXS

/RQGRQ
5RXWLQJ#*URXS
5RPH
5RXWLQJ#*URXS

7RN\R
5RXWLQJ#*URXS

)RU#
7KLV#LQIRUPDWLRQ#LV#FRYHUHG#
LQ#JUHDWHU#GHWDLO#LQ#PRGXOH#³&UHDWLQJ#DQG#0DQDJLQJ#
5RXWLQJ#*URXSV#LQ#
([FKDQJH#53331´#

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-topoint, 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 highbandwidth 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.
1RWH# 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#
6OLGH#2EMHFWLYH#

7R#GHILQH#DQG#H[SODLQ#WKH#
SXUSRVH#RI#DGPLQLVWUDWLYH#
JURXSV1#

/HDG0LQ#

$Q#DGPLQLVWUDWLYH#JURXS#
SURYLGHV#D#VLPSOH#PHWKRG#
IRU#GLYLGLQJ#DGPLQLVWUDWLYH#
UHVSRQVLELOLWLHV1#

/RQGRQ

6HDWWOH

5RPH
0LDPL

7RN\R

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.
7KLV#LQIRUPDWLRQ#LV#
The collection of administrative groups defines the administrative topology of
GLVFXVVHG#LQ#JUHDWHU#GHWDLO#LQ#

PRGXOH#:/#³0DQDJLQJ#6HUYHU# an organization. An administrative group can contain zero or more routing
2EMHFWV#LQ#([FKDQJH#53331´# groups, public folder trees, policies, monitors, servers, conferencing services,
and chat networks.
)RU#
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.
1RWH# 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#
6OLGH#2EMHFWLYH#

7R#LQWURGXFH#WKH#FRQFHSW#RI#
SROLFLHV#DQG#OLVW#WKH#DYDLODEOH#
W\SHV1#

/HDG0LQ#

$#SROLF\#LV#D#PHDQV#IRU#

PDNLQJ#D#VSHFLILF#VHWWLQJ#
FKDQJH#WKDW#FDQ#WKHQ#EH#
DSSOLHG#DFURVV#DQ#
RUJDQL]DWLRQ1#

/RQGRQ

6HDWWOH

5RPH
0LDPL

7RN\R

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
7KLV#LQIRUPDWLRQ#LV#
server, public store, and mailbox store policies. Recipient policies are also
GLVFXVVHG#LQ#JUHDWHU#GHWDLO#LQ##
PRGXOH#:/#³0DQDJLQJ#6HUYHU# available, but this policy currently allows you to set only one property, which is
the proxy address for recipients.
2EMHFWV#LQ#([FKDQJH#5333´#
)RU#
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.
1RWH# This information is discussed in greater detail in course 1569A module 7,
“Managing Server Objects in Exchange 2000.”


#

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

#

‹# 5HOLDEOH/#6FDODEOH#3ODWIRUP#
6OLGH#2EMHFWLYH#

7R#JLYH#DQ#RYHUYLHZ#RI#WKLV#
WRSLF1#

/HDG0LQ#

6HYHUDO#NH\#QHZ#IHDWXUHV#
PDNH#([FKDQJH#5333#ERWK#
UHOLDEOH#DQG#VFDODEOH1#

„

7KH#,QIRUPDWLRQ#6WRUH

„

0XOWLSOH#3XEOLF#)ROGHU#7UHHV#

„

9LUWXDO#6HUYHUV#

„

&OXVWHULQJ

While some features in Exchange 2000 specifically address either reliability or
scalability, many features support both goals.
Reliability is enhanced by clustering and by information store enhancements
that allow databases to be restored more quickly.
Scalability is enhanced by virtual servers, by storage groups, and by the ability
to create multiple public folder trees.

46#


47#

#

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

7KH#,QIRUPDWLRQ#6WRUH#
6OLGH#2EMHFWLYH#

7R#JLYH#D#EULHI#RYHUYLHZ#RI#
FKDQJHV#WR#WKH#LQIRUPDWLRQ#
VWRUH#WKDW#HQKDQFH#UHOLDELOLW\#
DQG#VFDODELOLW\1#

„

6WRUH#&DQ#'\QDPLFDOO\#0RXQW#0XOWLSOH#3K\VLFDO#
'DWDEDVHV
Storage Group A

/HDG0LQ#

ESE
ESE

ESE
ESE

Store

Store

Store

Store

Store

Store

Store

Store

Store

Transaction Log
Transaction Log

7KLV#LQIRUPDWLRQ#LV#FRYHUHG#
LQ#JUHDWHU#GHWDLO#LQ#PRGXOH#
43/#³0DQDJLQJ#WKH#
([FKDQJH#5333#,QIRUPDWLRQ#
6WRUH1´#

Store

Store

)RU#
Store

Transaction Log
Transaction Log

7KH#LQIRUPDWLRQ#VWRUH#KDV#
PDLQWDLQHG#LWV#YHU\#UHOLDEOH#
SURFHVVHV/#EXW#QRZ#KDV#WKH#
FDSDELOLW\#WR#VXSSRUW#YHU\#
ODUJH#HQWHUSULVHV#LQ#RQH#
RUJDQL]DWLRQ1#

Storage Group B

Exchange Server has always delivered a transaction-based, single-instance
messaging and collaboration database that enables very high levels of reliability
and performance.

3DUWLWLRQLQJ#WKH#,QIRUPDWLRQ#6WRUH#
Exchange Server 5.5 enhanced this functionality by eliminating the 16-gigabyte
(GB) limit on the message store and allowing message stores of up to 16
terrabytes (TB). Exchange 2000 takes the next step in this evolution by
enabling you to partition the Information Store into separate managable stores,
each of unlimited size.

0XOWLSOH#6WRUHV#,QFUHDVH#5HOLDELOLW\#
Information store architecture gives administrators both the opportunity for
very large databases and the option to create multiple smaller physical
databases on a single server. Exchange 2000 databases are more commonly
referred to as stores. Smaller physical stores increase overall system reliability,
enable a much faster backup process, and speed up the recovery process in the
event of hardware failure. For example, if the hardware that contains one of
your stores fails, only that store is affected during repair, while any stores
contained on different drives continue to serve their e-mail users.

#

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

#

48#

6WRUDJH#*URXSV#3URYLGH#(IILFLHQF\#
Exchange 2000 uses storage groups to optimize the use of transaction log files
for multiple stores. A storage group is a collection of up to six stores that are
run with a single instance of the database engine and share a set of transaction
log files.
1RWH# This information is covered in greater detail in course 1569A module 10,
“Managing the Exchange 2000 Information Store.”


49#

#

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

0XOWLSOH#3XEOLF#)ROGHU#7UHHV#
6OLGH#2EMHFWLYH#

7R#EULHIO\#H[SODLQ#KRZ#
PXOWLSOH#SXEOLF#IROGHU#WUHHV#
HQKDQFH#VFDODELOLW\1#

([FKDQJH#5333#VXSSRUWV#
PRUH#WKDQ#RQH#SXEOLF#IROGHU/#
DOORZLQJ#PXOWLSOH#SXEOLF#
IROGHU#WUHHV#WR#EH#VWRUHG#RQ#
D#VLQJOH#VHUYHU1##

All Public Folders
Business

Sales

Sales

Marketing

Marketing

Training

:HE21173

All Public Folders
Business

Marketing

/HDG0LQ#

All Public Folders
Business

Sales

0$3,

Training

Training

Sales

Training

Public Folders
Business

)RU#
7KLV#LQIRUPDWLRQ#LV#FRYHUHG#
LQ#JUHDWHU#GHWDLO#LQ#FRXUVH#
PRGXOH#44/#³&UHDWLQJ#DQG#
0DQDJLQJ#3XEOLF#)ROGHUV#LQ#
([FKDQJH#53331´#

Sales

Public Folders
Business

Marketing

Public Folders
Business

Exchange 2000 supports multiple public folder trees, which are also referred to
as top-level hierarchies, for greater administrative control and flexibility of
public folders. For example, a separate public folder tree might be created to
collaborate with external users and keep that content separate from the default
public folder tree. In another example, an additional tree might be created at a
remote location for the users at that location to access data that is only relevant
for them.
The multiple public folders feature may affect your public folder strategy.
While the default public folder tree is created on every public folder server and
its list of folders, or hierarchy, is always replicated, additional public folder
trees only affect the servers on which they are configured. A set of departmental
or local folders can be created on a single server or a subset of servers. The
hierarchy for these additional public folders does not have to be replicated to
every server.
When Exchange 2000 is installed, the default “All Public Folders” tree is
created. This tree is available to all MAPI, IMAP4, NNTP, and HTTP Web
clients. Additional public folder trees are only available to NNTP and Web
clients and not clients, such as Microsoft Outlook® 2000 (unless viewed on a
Web page hosted in Outlook 2000). A primary initial use of these non-MAPI
accessible folders will be for collaboration with browsers and applications that
can use HTTP to access the store, such as Office 2000.
1RWH# This information is covered in greater detail in course 1569A module 11,
“Creating and Managing Public Folders in Exchange 2000.”


#

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

#

4:#

9LUWXDO#6HUYHUV#
6OLGH#2EMHFWLYH#

7R#JLYH#D#EULHI#RYHUYLHZ#RI#
YLUWXDO#VHUYHUV1#

/HDG0LQ#

9LUWXDO#VHUYHUV#DOORZ#D#VLQJOH#
SK\VLFDO#VHUYHU#WR#WUDQVPLW#
PHVVDJHV#ZLWK#GLIIHUHQW#
VHFXULW\#VHWWLQJV#WR#GLIIHUHQW#
QHWZRUNV1#

Server 2
Server 1

Internet

LAN/WAN

9LUWXDO
9LUWXDO
6HUYHU#$

6HUYHU#$

9LUWXDO#
9LUWXDO#
6HUYHU#%
6HUYHU#%
Server 3

)RU#
7KLV#LQIRUPDWLRQ#LV#FRYHUHG#
LQ#JUHDWHU#GHWDLO#LQ#PRGXOH#;/#
³0DQDJLQJ#9LUWXDO#6HUYHUV#
DQG#3URWRFROV#LQ#
([FKDQJH#53331´#

A virtual server resides on a physical server but appears to the user as a
separate server. Several virtual servers can reside on one physical server, each
capable of running its own programs and each with individualized access to
input and peripheral devices. Each virtual server has its own domain name and
IP address and appears to the user as an individual Web site.
In Exchange 2000 each virtual server acts as an independent host and has its
own configuration information, such as bound Internet Protocol (IP) addresses,
port number, and authentication settings. As an independent host, each virtual
server can support different levels of security and can connect to different
networks. For instance, one virtual server can connect to the Internet, enabling
all users to send and receive messages over the Internet; and another virtual
server can be configured only to deliver messages between Exchange 2000
computers within an organization. This allows you to set a higher level of
security for messages coming in from the outside.

By default, only one virtual server per protocol is present on each server
running Exchange 2000. This default virtual server can be configured to support
the desired configuration through the Exchange System Manager. For example,
a restriction may be placed on the virtual server to block anonymous access or
to perhaps perform reverse Domain Name System (DNS) lookup.
1RWH# This information is covered in greater detail in course 1569A module 8,
“Managing Virtual Servers and Protocols in Exchange 2000.”


4;#

#

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

&OXVWHULQJ#
6OLGH#2EMHFWLYH#

7R#JLYH#D#EULHI#RYHUYLHZ#RI#
KRZ#FOXVWHULQJ#EHQHILWV#
UHOLDELOLW\1#

Servers

/HDG0LQ#

([FKDQJH#5333#VXSSRUWV#
DFWLYH0DFWLYH#FOXVWHULQJ/#
ZKLFK#LQFUHDVHV#WKH#
UHOLDELOLW\#WR#XVHUV1#

Clients

Clients

An Exchange 2000 cluster provides high reliability to users. A cluster consists
of two physical computers, or nodes, connected to each other and a shared
storage device. One or more virtual servers run on one of the nodes in the
cluster. Clients connect to the virtual servers the same way that they would
connect to a stand-alone server.
The cluster service monitors the virtual servers in the cluster. In the event of a
failure, the cluster service restarts or moves the virtual servers on the failed
node to a healthy node. For planned outages, the administrator can manually
move the virtual servers to other nodes. In either event, the client will see an
interruption of service during only the brief time that the virtual server is in a
transition state. The ability to use multiple servers at all times reduces system
costs while increasing reliability because no dedicated servers are needed for
emergency recovery.
Exchange 2000 Server supports active/active clustering. Active/active
clustering describes clustering when both members of the cluster are online and
able to accept user service requests. This is different from Exchange Server 5.5
active/passive clustering where only one member of a cluster provides service
to users at a time.
1RWH# Clustering is only supported with Windows 2000 Advanced Server.


#

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

#

4<#

‹# 8QLILHG#&ROODERUDWLRQ#3ODWIRUP#
6OLGH#2EMHFWLYH#

7R#JLYH#DQ#RYHUYLHZ#RI#WKLV#
WRSLF1#

/HDG0LQ#

([FKDQJH#5333#GHOLYHUV#D#
IXOO#VHW#RI#FROODERUDWLRQ#
IHDWXUHV1#

„

$FFHVV#WR#([FKDQJH#5333#'DWD

„

0LFURVRIW#2XWORRN#:HE#$FFHVV

„

(YHQW#6XSSRUW#LQ#([FKDQJH#5333

„

5HDO07LPH#&ROODERUDWLRQ

Exchange 2000 provides a variety of functions and features that support
collaboration efforts. These functions provide support to developers working on
collaboration applications in addition to users who need seamless solutions to
sharing data and communicating with other users.


53#

#

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

7KH#:HE#6WRUH#
6OLGH#2EMHFWLYH#

7R#GHILQH#DQG#GHVFULEH#WKH#
HOHPHQWV#WKDW#PDNH#XS#WKH#
:HE#6WRUH1#

„

,QIRUPDWLRQ#6WRUH#3URYLGHV#6LQJOH#6WRUDJH#/RFDWLRQ#IRU#
'RFXPHQWV#DQG#$SSOLFDWLRQV

„

)LOH#6\VWHP#6HUYLFHV

„

'DWDEDVH#6HUYLFHV

„

&ROODERUDWLRQ#6HUYLFHV

/HDG0LQ#

7KH#:HE#6WRUH#SURYLGHV#D#
VLQJOH#UHSRVLWRU\#IRU#
PDQDJLQJ#PXOWLSOH#W\SHV#RI#
LQIRUPDWLRQ#ZLWKLQ#RQH#
LQIUDVWUXFWXUH1#

The Web Store is a storage platform that provides a single repository for
managing multiple types of information within one infrastructure. The Web
Store combines the features and functionality of a file system, the Web, and
Exchange 2000 to access and manage information through a single, URL
addressable location. Key components include the following:
„#

Exchange File System. The Exchange file system allows clients, such as
Microsoft Office to read and write documents, in addition to storing
streaming data, such as audio and video. The Exchange file system uses a
data model that supports both hierarchical collections (folders) and
heterogeneous collections (folders that accept any file type).

„#

Native Content Store. The native content store stores data from non-MAPI
clients in native Multipurpose Internet Mail Extensions (MIME) format. No
conversion is performed unless a MAPI client accesses the data.

„#

URL Addressability. Exchange folders and mailbox objects can be accessed
using simple URL addresses, based on the folder name. For example,
http://servername/exchange/john/Inbox displays John’s inbox folder in your
Web browser.

„#

Web-DAV. Web-DAV is an extension of the HTTP protocol that makes
Web sites writable, with support for multiple authors. That is, pages are
protected from multiple authors making changes at the same time.

„#

Web Folders. Web-DAV allows the implementation of web folders so that
files can be opened and saved using Port 80.


#

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

#

54#

0LFURVRIW#2XWORRN#:HE#$FFHVV#
6OLGH#2EMHFWLYH#

7R#JLYH#DQ#RYHUYLHZ#RI#WKH#
FKDQJHV#WR#2XWORRN#:HE#
$FFHVV#LQ#([FKDQJH#53331#

„

(QKDQFHG#,QWHUQHW#([SORUHU#8#6XSSRUW

/HDG0LQ#

„

6XSSRUWV#0HVVDJHV#7KDW#&RQWDLQ#(PEHGGHG#,WHPV#DQG#
0LFURVRIW##$FWLYH;#2EMHFWV

„

6XSSRUWV#3XEOLF#)ROGHUV#7KDW#&RQWDLQ#&RQWDFW#DQG#
&DOHQGDU#,WHPV

„

6XSSRUWV#0XOWLPHGLD#0HVVDJHV

„

8VHV#1DPHG#85/V#WR#5HIHUHQFH#,WHPV

2XWORRN#:HE#$FFHVV#KDV#
LPSURYHG#SHUIRUPDQFH#DQG#
DGGLWLRQDO#IHDWXUHV#LQ#
([FKDQJH#53331#

Outlook Web Access provides a secure environment for users to access
Exchange 2000 data by using an Internet browser, such as Microsoft Internet
Explorer. From a UNIX, Macintosh, or Microsoft Windows-based computer
connected to the server, a user with the correct permissions can view and work
with any public folder, mailbox, global address list (GAL), or calendar.
Exchange 2000 contains a newly designed version of Outlook Web Access for
increased performance and scalability. Client and server performance has been
improved, and the following features have been added:
„#

Enhanced support for Microsoft Internet Explorer version 5. Internet
Explorer 5 users benefit from an interface that is closer in function to
Outlook. Outlook Web Access is also more efficient for Internet Explorer 5
users because Internet Explorer 5 does not require communication to the
Outlook Web Access server for every mouse click in the interface, as it does
with other clients.

„#

Support for messages that contain embedded items (messages,
appointments, contacts, and so on) and Microsoft ActiveX® objects. An
ActiveX object such as an image control is rendered and displayed when the

message containing it is opened. However, the object and its data cannot be
manipulated.

„#

Support for public folders that contain contact and calendar items. Users
can now view and read messages in public folders that contain contact and
calendar information.

„#

Support for multimedia messages. Outlook Web Access enables you to
easily add audio and video clips directly into a message and send it.

„#

Named URLs to reference items. While previous versions of Outlook Web
Access used globally unique identifiers (GUIDs) to reference items in the
information store, items (messages, folders, and so on) are now accessed
using a plain text address, such as http://server/exchange/mailbox/inbox.