&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#
#
Module 1: Introduction
to Microsoft
Exchange 2000 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

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


Read all of the materials for this module.

3UHVHQWDWLRQ=##
93#0LQXWHV#
#
/DE=##
33#0LQXWHV#
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

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.

6OLGH#2EMHFWLYH#
7R#SURYLGH#DQ#RYHUYLHZ#RI#
WKH#PRGXOH#WRSLFV#DQG#
REMHFWLYHV1#
/HDG0LQ#
,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#
5# # 0RGXOH#4=#,QWURGXFWLRQ#WR#0LFURVRIW#([FKDQJH#5333#


independent of connectivity.
6OLGH#2EMHFWLYH#
7R#OLVW#DQG#EULHIO\#GLVFXVV#
WKH#PDLQ#([FKDQJH#5333#
SURGXFW#JRDOV1#
/HDG0LQ#
([FKDQJH#5333#LV#GHVLJQHG#
DV#D#UHOLDEOH/#VFDODEOH/#DQG#
VHFXUH#SODWIRUP#WKDW#LV#
LQWHJUDWHG#ZLWK#
:LQGRZV#53331#
# 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

6OLGH#2EMHFWLYH#
7R#JLYH#DQ#RYHUYLHZ#RI#WKLV#
WRSLF1#
/HDG0LQ#
([FKDQJH#5333#UHOLHV#
FRPSOHWHO\#RQ#$FWLYH#
'LUHFWRU\1#
# 0RGXOH#4=#,QWURGXFWLRQ#WR#0LFURVRIW#([FKDQJH#5333# # 8#
,QWHJUDWLRQ#ZLWK#$FWLYH#'LUHFWRU\#
Exchange 2000
Exchange 2000
Exchange 2000
Information Store
MTA
System Attendant
Information Store
MTA
System Attendant
Exchange 5.
x
Exchange 5.
Exchange 5.
x
x
Directory Service
Information Store
MTA

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.

6OLGH#2EMHFWLYH#
7R#JLYH#D#EULHI#RYHUYLHZ#RI#
WKH#VFRSH#RI#LQWHJUDWLRQ#ZLWK#
$FWLYH#'LUHFWRU\1#
/HDG0LQ#
2QH#RI#WKH#PRVW#IDU0
UHDFKLQJ#QHZ#IHDWXUHV#LQ#
([FKDQJH#5333#LV#WKH#XVH#RI#
$FWLYH#'LUHFWRU\#WR#UHSODFH#
WKH#([FKDQJH#GLUHFWRU\1#
'HOLYHU\#7LS#
7KLV#LQIRUPDWLRQ#LV#
GLVFXVVHG#LQ#JUHDWHU#GHWDLO#LQ#
VHYHUDO#PRGXOHV#WKURXJKRXW#
WKH#FRXUVH1#
9# # 0RGXOH#4=#,QWURGXFWLRQ#WR#0LFURVRIW#([FKDQJH#5333#
,QWHJUDWLRQ#ZLWK#,QWHUQHW#,QIRUPDWLRQ#6HUYLFHV#
Exchange 2000
Exchange 2000

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.”

6OLGH#2EMHFWLYH#
7R#JLYH#DQ#RYHUYLHZ#RI#KRZ#
SURWRFROV#DUH#LPSOHPHQWHG#
LQ#([FKDQJH#53331#
/HDG0LQ#
$QRWKHU#LQFUHDVH#LQ#ERWK#
UHOLDELOLW\#DQG#VFDODELOLW\#LQ#
([FKDQJH#5333#LV#GXH#WR#
PRYLQJ#SURWRFROV#RXW#RI#WKH#
,QIRUPDWLRQ#6WRUH#VHUYLFH1#
)RU#<RXU#,QIRUPDWLRQ#
7KLV#LQIRUPDWLRQ#LV#FRYHUHG#
LQ#JUHDWHU#GHWDLO#LQ#PRGXOH#7/#
³([FKDQJH#5333#
$UFKLWHFWXUH/´#DQG#PRGXOH#;/#
³0DQDJLQJ#9LUWXDO#6HUYHUV#

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.
6OLGH#2EMHFWLYH#
7R#JLYH#D#EULHI#RYHUYLHZ#RI#
0LFURVRIW#0DQDJHPHQW#
&RQVROH#+00&,1#
/HDG0LQ#
0LFURVRIW#0DQDJHPHQW#
&RQVROH#SURYLGHV#D#VLQJOH#
ORFDWLRQ#IRU#DGPLQLVWUDWRUV#WR#
SHUIRUP#DGPLQLVWUDWLYH#WDVNV#
RQ#DOO#0LFURVRIW#%DFN2IILFH#
SURGXFWV1#
'HOLYHU\#7LS#
7KLV#LQIRUPDWLRQ#LV#
GLVFXVVHG#LQ#JUHDWHU#GHWDLO#LQ#
PRGXOH#:/#³0DQDJLQJ#6HUYHU#
2EMHFWV#LQ#([FKDQJH#53331´#
;# # 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 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
PoliciesThe 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.

43# # 0RGXOH#4=#,QWURGXFWLRQ#WR#0LFURVRIW#([FKDQJH#5333#
([FKDQJH#5333#0HVVDJH#5RXWLQJ#
86$
5RXWLQJ
*URXS
/RQGRQ
5RXWLQJ#*URXS
5RPH
5RXWLQJ#*URXS
7RN\R
5RXWLQJ#*URXSA 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


$GPLQLVWUDWLYH#*URXSV#
6HDWWOH
0LDPL
/RQGRQ
7RN\R
5RPH
3ROLF\#$GPLQLVWUDWLYH#*URXS
86#$GPLQLVWUDWLYH#*URXS
(XURSHDQ#$GPLQLVWUDWLYH#*URXSAn 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.”

6OLGH#2EMHFWLYH#
7R#GHILQH#DQG#H[SODLQ#WKH#
SXUSRVH#RI#DGPLQLVWUDWLYH#

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.”

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#
)RU#<RXU#,QIRUPDWLRQ#
7KLV#LQIRUPDWLRQ#LV#
GLVFXVVHG#LQ#JUHDWHU#GHWDLO#LQ##
PRGXOH#:/#³0DQDJLQJ#6HUYHU#
2EMHFWV#LQ#([FKDQJH#5333´#

UHOLDEOH#DQG#VFDODEOH1#
47# # 0RGXOH#4=#,QWURGXFWLRQ#WR#0LFURVRIW#([FKDQJH#5333#
7KH#,QIRUPDWLRQ#6WRUH#
„
6WRUH#&DQ#'\QDPLFDOO\#0RXQW#0XOWLSOH#3K\VLFDO#
'DWDEDVHV
ESE
ESE
Transaction Log
Transaction Log
Store
Store
Store
Store
Store
Store
Store
Store
Store
Store
Store
Store
Storage Group A Storage Group B
Transaction Log
Transaction Log
Store
Store

your stores fails, only that store is affected during repair, while any stores
contained on different drives continue to serve their e-mail users.
6OLGH#2EMHFWLYH#
7R#JLYH#D#EULHI#RYHUYLHZ#RI#
FKDQJHV#WR#WKH#LQIRUPDWLRQ#
VWRUH#WKDW#HQKDQFH#UHOLDELOLW\#
DQG#VFDODELOLW\1#
/HDG0LQ#
7KH#LQIRUPDWLRQ#VWRUH#KDV#
PDLQWDLQHG#LWV#YHU\#UHOLDEOH#
SURFHVVHV/#EXW#QRZ#KDV#WKH#
FDSDELOLW\#WR#VXSSRUW#YHU\#
ODUJH#HQWHUSULVHV#LQ#RQH#
RUJDQL]DWLRQ1#
)RU#<RXU#,QIRUPDWLRQ#
7KLV#LQIRUPDWLRQ#LV#FRYHUHG#
LQ#JUHDWHU#GHWDLO#LQ#PRGXOH#
43/#³0DQDJLQJ#WKH#
([FKDQJH#5333#,QIRUPDWLRQ#
6WRUH1´#
# 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.

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

Public Folders
Business
Sales
Marketing
Public Folders
BusinessExchange 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

Server 3
9LUWXDO
6HUYHU#$
9LUWXDO
6HUYHU#$
9LUWXDO#
6HUYHU#%
9LUWXDO#
6HUYHU#%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.

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.

Clustering is only supported with Windows 2000 Advanced Server.

6OLGH#2EMHFWLYH#
7R#JLYH#D#EULHI#RYHUYLHZ#RI#
KRZ#FOXVWHULQJ#EHQHILWV#
UHOLDELOLW\1#
/HDG0LQ#
([FKDQJH#5333#VXSSRUWV#
DFWLYH0DFWLYH#FOXVWHULQJ/#
ZKLFK#LQFUHDVHV#WKH#
UHOLDELOLW\#WR#XVHUV1#
7KH#:HE#6WRUH#
„
,QIRUPDWLRQ#6WRUH#3URYLGHV#6LQJOH#6WRUDJH#/RFDWLRQ#IRU#
'RFXPHQWV#DQG#$SSOLFDWLRQV
„
)LOH#6\VWHP#6HUYLFHV
„
'DWDEDVH#6HUYLFHV
„
&ROODERUDWLRQ#6HUYLFHVThe 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

„
6XSSRUWV#0XOWLPHGLD#0HVVDJHV
„
8VHV#1DPHG#85/V#WR #5HIHUHQFH#,WHPVOutlook 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.