0989701

Module 1: Installing and
Upgrading to Exchange
Server 2003
Contents
Overview 1
Lesson: Installing Exchange Server 2003 2
Lesson: Installing Exchange Server 2003
in a Clustered Environment 23
Lesson: Installing and Using Exchange
Management Tools and Utilities 37
Lesson: Upgrading from Exchange 2000
Server to Exchange Server 2003 52
Discussion: Installing and Upgrading to
Exchange Server 2003 61
Information in this document, including URL and other Internet Web site references, is subject to
change without notice. Unless otherwise noted, the example companies, organizations, products,
domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious,
and no association with any real company, organization, product, domain name, e-mail address,
logo, person, place or event is intended or should be inferred. Complying with all applicable
copyright laws is the responsibility of the user. Without limiting the rights under copyright, no
part of this document may be reproduced, stored in or introduced into a retrieval system, or
transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or
otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
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.
 2003 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, Windows, Windows NT, Windows Server, ActiveSync, ActiveX, Active
Directory, Hotmail, MSDN, MSN, Outlook, PowerPoint, Visual Basic, and Windows Media are
either registered trademarks or trademarks of Microsoft Corporation in the United States and/or
other countries.
The names of actual companies and products mentioned herein may be the trademarks of their
respective owners.
Module 1: Installing and Upgrading to Exchange Server 2003 iii
Instructor Notes
Presentation: This module provides students with the knowledge and skills that are needed to
105 minutes perform an installation of Microsoft® Exchange Server 2003 on new hardware,
install Exchange Server 2003 in a clustered environment, install and use
Practices: management tools, and upgrade from Exchange 2000 Server to Exchange
65 minutes Server 2003.
After completing this module, students will be able to:
! Install Exchange Server 2003.
! Install Exchange Server 2003 in a clustered environment.
! Install and use Exchange management utilities.
! Upgrade from Exchange 2000 Server to Exchange Server 2003.
Required materials To teach this module, you need the following materials:
! Microsoft PowerPoint® file 2400B_01.ppt
! Video file 2400B_01_v05.wmv
! Module 1 animation, How Exchange Server 2003 Uses Windows Clustering,
2400B_01A_005.swf
! Module 1 demonstrations:
• How to Run ForestPrep and DomainPrep, 2400B_01_D05.wmv and
2400B_01_D10.wmv
• How to Install Exchange Server 2003, 2400B_01_D15.wmv
• How Exchange Server 2003 Is Installed in a Clustered Environment,
2400B_01_D20.wmv
• How to Install Exchange System Manager, 2400B_01_D25.wmv
• How to Upgrade from Exchange 2000 to Exchange 2003,
2400B_01_D30.wmv
! The job aid Joint Development Program (JDP) - Technical Reference
Guide, 2400B_JA1.chm on the Student Materials compact disc
Important It is recommended that you use PowerPoint 2002 or later to display

the slides for this course. If you use PowerPoint Viewer or an earlier version of
PowerPoint, all the features of the slides may not be displayed correctly.
iv Module 1: Installing and Upgrading to Exchange Server 2003
Preparation tasks To prepare for this module:

! Read all of the materials for this module, including the job aid.
! Complete the practices, and review the discussions and assessment
questions. Where possible, anticipate alternative answers that students may
suggest and prepare responses to those answers.
! Review the animations and demonstrations.
! Complete the demonstration regarding how to use Connectix Virtual PC,
which is in the Introduction module of this course. Students must watch you
perform this demonstration. It is crucial that students become familiar with
the virtual environment that is used in the practices before they attempt to
complete the first practice in this module on their own.
! Review the links and suggested additional readings for this module.
Document your own suggested additional readings to share with the class.
Classroom setup The classroom should be set up to use Connectix Virtual PC software, as
discussed in the Manual Classroom Setup Guide. No additional classroom setup
is needed.
Module 1: Installing and Upgrading to Exchange Server 2003 v
How to Teach This Module

This section contains information that will help you to teach this module.
A few terms in this module are mentioned and defined briefly as part of
learning how to install and upgrade to Exchange Server 2003. However, these
terms are not defined in detail until later modules. If students ask questions
about these terms, briefly answer the student’s questions, and tell them that that
later modules will discuss the terms in much greater detail.
If no student practice is included in a How-to topic, consider demonstrating the
task for students.
How to start Discuss the tasks on the module overview slide and then click the projector
button to show the brief video from a Northwind Trader’s employee before you
continue with the module. In this video, students will be given overall
instructions for tasks from their team lead or co-worker at Northwind Traders.
You can play this video again at the beginning of the first practice in the
module if you think it will help motivate students.
Time to teach this We anticipate that your total presentation time will be about 105 minutes. The
module majority of the time spent on this module should be time that students get to
complete hands-on practice activities, view the multimedia presentation, and
participate in class discussions. In addition to your presentation time, we
anticipate that hands-on time for students will be about 65 minutes.
Tip When this icon appears on the lower-right corner of a slide, it indicates
that students must complete an inline practice before you move on to the next
slide:
Practices Some practices in this module require initial startup time. Consider having
students perform the initial step in these practices before you begin the lecture
on the related content. If a practice begins with a procedure titled “To prepare
for this practice,” then it requires initial startup time.

Hardware and System Emphasize to the students that the minimum hardware requirements will only
Requirements for allow them to complete the installation of Exchange Server 2003 and that to be
Exchange Server 2003 able to accurately scale the hardware for their servers, they must take into
considerations the workload that will be placed on the server.
Environment This topic and the rest of the requirements topics in this module have been
Requirements converted into learner-centered checklists of tasks to accomplish when students
Checklist for Exchange perform these tasks at work.
Server 2003
Emphasize the importance of Exchange 2003’s dependency on the Microsoft
Active Directory® directory service and Domain Name System (DNS). Tell
your students that for Exchange Setup to successfully complete, Active
Directory and DNS must be installed and functioning properly.
vi Module 1: Installing and Upgrading to Exchange Server 2003
Consider asking students to describe the order that works best for them when
deploying a new environment. Possible answers would be: to install their
hardware, prepare their environmental requirements and then perform their
installations or, to purchase their hardware, prepare their environmental
requirements, install their hardware, and then install Exchange.
Ask your students if their environment will co-exist with other messaging
systems. If so, tell them that to install the first Novell GroupWise or Lotus
Notes connector, they will require Exchange Full Administrator at the
organization level.
Demonstration: How to Because of the Virtual PC classroom environment, you will not be able to
Run ForestPrep and demonstrate this module’s installation and upgrade tasks on your computer;
DomainPrep therefore, we have created the demonstration for you. You can launch this
demonstration by clicking the appropriate projector button on the slide. When
the demonstration is finished, answer any questions that the students have
before you continue. Also mention that students can watch this demonstration
on their own as it is included on the Web page on the Student Materials
compact disc.
Tell students that if they are not using the Exchange Server 2003 compact disc,
they will need to provide the drive letter and the path to the setup files. Also tell
the students that if no components are selected on the Component Selection
page, they do not have sufficient permissions in Active Directory to perform the
installation.
Emphasize to your students the importance of the note on documenting any
changes before updating their environment.
Components That Can Use this slide to discuss the components that students can install, remove, or
Be Configured During change during Setup before they install Exchange.
Setup
Demonstration: How You can launch this demonstration by clicking the projector button on the slide.
to Install Exchange When the demonstration is finished, answer any questions that the students
Server 2003 have before you continue. Also mention that students can watch this
demonstration on their own as it is included on the Web page on the Student
Materials compact disc.
What Is an Unattended Use these two slides to discuss unattended installation—for example, when it
Installation? can be used, and how to do it.
How to Perform an Use this slide to discuss the high-level steps for performing an unattended
Unattended Installation installation, and the options that students can use when performing an
of Exchange Server 2003 unattended installation.
How to Verify That Use this slide to discuss the high-level steps for verifying that installation of
Installation of Exchange Exchange Server 2003 was successful. For a list of folders and services created
Server 2003 Was during the installation process, refer students to the Default File Locations and
Successful Services white paper on the Student Materials compact disc.
Module 1: Installing and Upgrading to Exchange Server 2003 vii
Practice: Installing Show students where the job aid Joint Development Program (JDP) - Technical
Exchange Server 2003 Reference Guide resides on the Student Materials compact disc. Have students
complete the practice in the topic, and then answer any questions that they have.
Ask the students to read the four scenarios and, working with a partner, use the
job aid to determine the possible solution. Be prepared to help guide the
students in where to find the information in the job aid because the job aid
contains additional useful reference material beyond the scope of the four
scenarios. This job aid contains tips, common support issues, dependencies, and
in-depth explanations for installing Exchange Server 2003. When each partner
group in the class have agreed on solutions to the scenarios, discuss their
solutions with the rest of the class.
Lesson: Installing Exchange Server 2003 in a Clustered

Environment
Multimedia: How You can launch this multimedia by clicking the projector button on the slide.
Exchange Server 2003 When you are finished showing the multimedia, facilitate a discussion and
Uses Windows answer any questions that the students may have.
Clustering
Explain to your students that the module covers some of the topics that are in
the multimedia in more detail. To verify that your students understand some
basic concepts presented in the video, ask them to explain their understanding
of the following concepts:
! Exchange Virtual Server. An Exchange Virtual Server is a virtual computer
(a collection of resources) that can be passed between nodes.
! Public and private network communication. The private network is used for
node to node communication while the public network is used for client to
server communication.
! Failover and failback. Failover is when control of a resource is moved to a
different node and failback is when control is returned to the original node.
Mention that students can watch this animation again later on their own. To find
the animation, students can open the Web page on the Student Materials
compact disc, click Multimedia, and then click How Exchange Server 2003
Uses Windows Clustering.
Hardware Requirements When you finish discussing the hardware requirements for an Exchange cluster,
Checklist for an ask students if they have an experience with cluster hardware that they would
Exchange Server 2003 like to share.
Cluster
Types of Exchange 2003 Tell students that while Exchange Server 2003 does support active/active
Cluster Configurations clustering, the preferred cluster configuration is active/passive.
Recommended Use this slide to explain why Microsoft recommends active/passive cluster
Exchange Server 2003 configurations. Refer students to the white paper Deploying Exchange 2000
Cluster Configuration Server Clusters on the Exchange page of the Microsoft Web site at
www.microsoft.com/exchange/techinfo/deployment/2000/ for detailed
information about Exchange Clustering. Tell the students that while this white
paper was updated for Exchange 2000 SP3, most of the content in the paper is
also applicable when deploying Exchange Server 2003 clusters.
viii Module 1: Installing and Upgrading to Exchange Server 2003
Considerations for Use this slide to discuss the considerations for using the active/passive and
Using Clustering active/active cluster configurations. If students want information about how to
monitor virtual memory performance, refer them to Module 13, “Performing
Preventive Maintenance,” in Course 2400, Implementing and Managing
Microsoft Exchange Server 2003.
How Failover Occurs on Use the animated slide to demonstrate how a failover occurs on an active/active
an Active/Active Cluster cluster and then how it occurs on an active/passive cluster. The animated slide
vs. an Active/Passive first presents the active/active cluster failover, and second, presents the
Cluster active/passive failover. You will have to click manually for the animated slide
to display correctly. A text box appears during each click explaining what is
occurring. Use the information in the text box to explain to the students how
failover occurs in each scenario.
Permissions Required to Use the table in this slide to discuss the permissions that students must have to
Install and Configure an create, modify, and delete an Exchange Virtual Server.
Exchange Virtual Server
Exchange Server 2003 Is When the demonstration is finished, answer any questions that the students
Installed in a Clustered have before you continue. Also mention that students can watch this
Environment demonstration on their own as it is included on the Web page on the Student
Practice: Installing Pair up students so that they can do this practice with a partner. The practice
Exchange Server 2003 in presents six scenarios that build on each other. When all of the pairs of students
a Clustered Environment have completed the scenarios, lead a discussion and answer any questions that
the students have.
Lesson: Installing and Using Exchange Management Tools and

Utilities
Management Tools and Use the chart on this slide to discuss the Microsoft Windows®, Active
Utilities for Directory, and Exchange tools and utilities that students can use to fully
Administering Exchange administer Exchange.
Platforms from Which This animated slide has two parts. The first part simply presents the three
You Can Administer platforms. When you finish talking about the platforms, use the second part of
Exchange the animated slide to discuss the extra steps that students must take if they
decide to administer Exchange by using Windows XP.
Permissions Required to Use the table on this slide to discuss the three permissions that Exchange
Access Objects in supports for administration. Tell the students that they can simplify the
Exchange System assigning of these permissions by using the Exchange Administration
Manager Delegation Wizard in Exchange System Manager.
Demonstration: How to You can launch this demonstration by clicking the projector button on the slide.
Install Exchange System When the demonstration is finished, answer any questions that the students
Manager have before you continue. Also mention that students can watch this
demonstration on their own as it is included on the Web page on the Student
How to Install and Run Use this slide to briefly discuss how to install and run Windows support tools.
the Windows Support Then, have the students complete the inline practice and answer any questions
Tools that they have.
Module 1: Installing and Upgrading to Exchange Server 2003 ix
How to Create a Custom Use this slide to briefly discuss the high-level steps for creating a custom
MMC for Exchange Microsoft Management Console (MMC). Then, have the students complete the
Administration inline practice and answer any questions that they have.
Practice: Choosing You can have students do this practice on their own and then discuss the
Exchange Management answers as a class, or you can do the practice as a class and discuss each answer
Tools after the students have completed the practice. Let students know that they will
be using many of these tools later in different modules throughout the course. In
addition, let the students know that there are other tools that may be used that
are not listed in the lesson and that the answers provided are based on tools that
were covered in the lesson. For example: for Scenario 1, students may list
Nslookup.exe as the correct tool because Nslookup.exe is always installed on
the computer, but the DNS snap-in may not be installed.
Lesson: Upgrading from Exchange 2000 Server to

Exchange Server 2003
The Differences The slide presents a high-level review of what is new in Exchange 2003 and
Between Exchange 2000 what has been removed. The details are included in the student workbooks.
Server and Exchange
Server 2003
Requirements Checklist Make certain that you point out to your students that all the requirements listed
for Upgrading to for installing Exchange 2003 apply and that the table contains the additional
Exchange Server 2003 requirements that need to be met to upgrade to Exchange Server 2003.
to Upgrade from When the demonstration is finished, answer any questions that the students
Exchange 2000 Server to have before you continue. Also mention that students can watch this
Exchange Server 2003 demonstration on their own as it is included on the Web page on the Student
Discussion: Installing and Upgrading to Exchange Server 2003

The scenarios in this discussion were designed to allow students to reflect on
what they did in the module and to give them an opportunity to ask any
remaining questions that they have. Use the discussion scenarios to provide a
summary of the module content. You can also return to the Module overview
slide and use it to help summarize the lessons covered in this module.
You can work through the scenarios with the entire class. Or, if you have time,
have students work in small groups to devise solutions to the problems in the
scenarios and then allow them to present and discuss their ideas with the class.
Before taking part in the discussion, students should have completed all of the
practices. Students who have not completed the practices may have difficulty
taking part in the discussion.
x Module 1: Installing and Upgrading to Exchange Server 2003
Assessment
Assessment questions for this module are located on the Student Materials
compact disc. You can use the assessment questions in whatever way you think
is best for your students. For example, you can use them as pre-assessments to
help students identify areas of difficulty, or you can use them as post-
assessments to validate learning. Consider using the questions to reinforce
learning at the end of the day or at the beginning of the next day. If you choose
not to use the assessment questions during class, show students where they are
located so that they can use them to assess their own learning outside of class.
Module 1: Installing and Upgrading to Exchange Server 2003 1
Overview
*****************************ILLEGAL FOR NON-TRAINER USE******************************

Introduction Messaging administrators must be able to install Microsoft®
Exchange Server 2003 on new hardware, install and use management tools and
utilities, and upgrade to Exchange Server 2003 from earlier versions of
Exchange. Messaging administrators may also need to install Exchange in a
clustered environment to provide the high availability that their companies
require. This module teaches you how to perform these four tasks and explains
the impact of these tasks on your environment.
Important Although installing Exchange Server 2003 results in a functioning

server, the server must still be configured and secured to meet the
requirements of your company. The tasks for configuring and securing
Exchange Server 2003 are described in Module 2, “Configuring and Managing
Exchange Server 2003,” and Module 3, “Securing Exchange Server 2003,” in
Course 2400, Implementing and Managing Microsoft Exchange Server 2003.
You must complete the tasks in Modules 1, 2, and 3 to ensure that the
performance of your Exchange servers fully meets the requirements of your
company.
Objectives After completing this module, you will be able to:

! Install Exchange Server 2003.
! Install Exchange Server 2003 in a clustered environment.
! Install and use Exchange management utilities.
! Upgrade from Exchange 2000 Server to Exchange Server 2003.
2 Module 1: Installing and Upgrading to Exchange Server 2003

Introduction This lesson describes the hardware, system, and environment requirements that
you must meet to successfully install Exchange Server 2003. The lesson then
explains how to install Exchange Server 2003.
Lesson objectives After completing this lesson, you will be able to:
! Describe the hardware and system requirements for Exchange Server 2003.
! Describe environment requirements for Exchange Server 2003.
! Describe how to run ForestPrep and DomainPrep.
! Describe the components that can be configured during Setup.
! Describe how to install Exchange Server 2003.
! Describe what an unattended installation is.
! Describe how to perform an unattended installation of
Exchange Server 2003.
! Verify that the installation of Exchange Server 2003 was successful.
Hardware and System Requirements for Exchange Server 2003

Exchange Server 2003 will install on operating systems and hardware that meet
the minimum requirements that are listed in the following table. However, you
will get better server performance if you use the hardware recommended by
Microsoft and by scaling your hardware to support your environment.
Minimum hardware and The minimum hardware and system requirements for computers that run
system requirements Exchange Server 2003 are listed in the following table.
Category Minimum requirement
Processor Intel Pentium or compatible 233 megahertz (MHz) or faster

processor
Memory 256 megabytes (MB) of random access memory (RAM)
recommended minimum; 128 MB supported minimum
Storage • 500 MB of available disk space on the drive on which you
install Exchange
• 200 MB of available disk space on the system drive
• All Exchange-related disk partitions formatted for the NTFS
file system
• CD-ROM drive
Operating system • Microsoft Windows® 2000 Server, Service Pack 3 (SP3) or
later
- or -
• Microsoft Windows Server™ 2003 family, except for
Windows Server 2003, Web Edition
Note Exchange Server 2003 is not supported on Windows Server 2003, Web
Edition.
Recommended It is recommended that you use the best hardware that your company is able and
hardware and system willing to purchase. To receive top performance from Exchange Server 2003,
requirements Microsoft recommends that you use the hardware and system components
described in the following table.
Category Recommended hardware or system component
Processor Intel Pentium or compatible 1.6 gigahertz (GHz) or better

processor, and Exchange 2003 running on multiple (eight or
fewer) processors
Memory 3 to 4 gigabytes (GB) of physical RAM
Storage Additional disk drives to accommodate database and transaction
log files
Operating system Microsoft Windows Server 2003, Enterprise Edition
Scaling your Exchange Microsoft provides information about the capacity planning and topology
servers calculator to help you understand and plan for scaling your Exchange servers.
You specify information about your existing or planned Exchange installation;
including:
! Topology information such as front-end and back-end configuration.
Exchange provides users with simplified access to messages by enabling
you to configure a unified namespace for front-end and back-end servers.
With front-end and back-end servers, the client connects to front-end
servers, while back-end servers store messages and collaboration data.
! Server resources such as number of processors and speed.
! Estimated total number of users and what protocols they will use to access
their e-mail.
Based on the information provided, the calculator provides an estimated

number of servers that are required for your environment.
Note For more information about scaling your Exchange servers to support the
number of mailboxes in your environment, see the Capacity Planning and
Topology Calculator page on the Microsoft Web site at
http://www.microsoft.com/exchange/techinfo/planning/2000/.
Environment Requirements Checklist for Exchange Server 2003

After you have your hardware and system in place, use the following checklist
to verify that your environment is ready for Exchange Server 2003 to be
installed, especially with regard to the Microsoft Active Directory® directory
service:
! Verify that Active Directory and DNS are installed and configured.
Exchange depends on Active Directory and Domain Name System (DNS)
being installed and functioning correctly before Exchange Setup can be run.
You can use the Domain Controller Diagnostics (DCDiag) utility to test
network connectivity and DNS resolution for domain controllers and the
Network Connectivity Tester (NetDiag) utility to test DNS functionality.
! Verify that you have the appropriate Active Directory permissions to run
setup. To perform setup tasks you must be an administrator of a local
computer. Additional permission requirements that are required before
running setup tasks are described in the following table.
Task Required permissions or roles
Run ForestPrep for the first time in the Member of Enterprise Admin group
forest (updates the schema). and Schema Admin group
Run DomainPrep to create groups and Domain Administrator
permissions for Exchange servers.
Install the first server in a domain. Exchange Full Administrator at the
organization level
Domain Administrator
Install additional servers in the domain. Exchange Full Administrator at the
administrative group level
Install a server with Site Replication Exchange Full Administrator at the
Service (SRS) enabled. (SRS provides organization level
directory replication between
Exchange 2003 and Exchange 5.5.)
(continued)
Task Required permissions or roles
Run the DCDiag utility. Domain Administrator

Run the NetDiag utility. No additional permissions required
! Verify that computers running Windows 2000 and Windows Server 2003
that host Exchange 2003 are part of an Active Directory domain.
! Verify that all computers running Exchange in the same Exchange
organization are in the same Active Directory forest. An Exchange
organization is the largest administrative unit that includes all Exchange
servers in a forest. Only one Exchange organization can exist for each
Active Directory forest.
Note For more information about solutions that allow multiple Active
Directory forests to co-exist with and migrate between Exchange
organizations, see the Microsoft Metadirectory Services 2003 on the
Windows 2000 page of the Microsoft Web site at www.microsoft.com/
windows2000/technologies/directory/mms/default.asp and Module 14,
“Migrating Users from Exchange 5.5 Server to Exchange Server 2003,” in
! Verify that you install Exchange 2003 before you upgrade Windows 2000 to
Windows Server 2003. If you plan to upgrade servers running
Windows 2000 to Windows Server 2003, you must install Exchange
Server 2003 on the servers before you upgrade the operating systems. After
you upgrade a server to Exchange Server 2003 on Windows 2000, you can
further upgrade the server to Windows Server 2003. By following this
upgrade sequence, you take advantage of the logic built into Exchange
Server 2003 to manage the underlying operating system upgrade.
! Verify that domain controllers and global catalog servers are running
Windows 2000 Service Pack (SP)3 or Windows Server 2003 so that
Exchange can recognize them. The Exchange Server 2003 Setup program
must be able to contact at least one Active Directory server running
Windows 2000 SP3 or later or Windows Server 2003 in the local Active
Directory site.
! Run ForestPrep one time in the Active Directory forest in the domain where
the schema master resides. ForestPrep is an Exchange Setup switch that
extends the Active Directory schema to include Exchange-specific classes
and attributes. ForestPrep also creates the container object for the Exchange
organization in Active Directory. The schema extensions supplied with
Exchange Server 2003 are a superset of those supplied with Exchange 2000.
By default, the schema master runs on the first Windows domain controller
installed in a forest. Setup checks whether you are running ForestPrep in the
same domain as the schema master; if you are not running ForestPrep in the
correct domain, Setup tells you which domain contains the schema master.
Note It is recommended you run ForestPrep on the Active Directory

schema master so that schema updates can be made locally. Consider
running ForestPrep early in your Active Directory deployment or when
there is not much traffic on the network to reduce the impact on your
network from replication of schema updates throughout the forest.
Before you make any changes to your Active Directory schema, it is
recommended that you back up your schema so that you can return your
schema to its original configuration if any problems arise during the update.
! When you run ForestPrep, designate an account that will have Exchange
Full Administrator permissions to the organization object. This account will
have the authority to install and manage Exchange Server 2003 throughout
the forest and assign further administrators permissions after the first server
is installed.
! Create your Exchange administrative group structure before you install
your first server running Exchange 2003. If you do not create an
administrative group before the first Exchange server is installed, Setup will
automatically create an administrative group named First Administrative
Group. The first computer running Exchange that you install will be placed
in this group. After the first server has been installed, you can create
additional administrative groups into which you can install subsequent
computers running Exchange.
Caution You cannot move computers that run Exchange between

administrative groups. Therefore, it is important to install each Exchange server
in the administrative group specified in your Exchange implementation plan. To
create administrative groups before you install your first server, use the ADSI
Edit utility or Exchange System Manager discussed in “Lesson: Installing and
Using Exchange Management Tools and Utilities” in Module 1, “Upgrading
and Installing Exchange Server 2003,” in Course 2400, Implementing and
Managing Microsoft Exchange Server 2003.
! Run DomainPrep to prepare your domains for Exchange. DomainPrep is an

Exchange Setup switch that creates the groups and permissions necessary
for Exchange servers to read and modify user attributes. DomainPrep
creates these groups:
• Exchange Domain Servers. A domain global group that contains all
servers running Exchange in the domain.
• Exchange Enterprise Servers. A domain local group that contains the
Exchange Domain Servers groups from all the domains in the enterprise.
Run DomainPrep in the following domains:
• The root domain.
• All domains that will contain Exchange Server 2003 servers.
• All domains that will contain Exchange Server 2003 mailbox-enabled
accounts or mail-enabled objects (such as accounts, contacts, or groups),
even if no Exchange servers will be installed in these domains.
You must run the Exchange Server 2003 version of DomainPrep even if you
are already running Exchange 2000 in the domain. The account that you use
to run DomainPrep must be a member of the Domain Admins group in the
local domain.
! Verify that the following services are installed and enabled on the server
onto which you will install Exchange 2003:
• Microsoft .NET Framework
• Microsoft ASP.NET
• World Wide Web Publishing service
• SMTP (Simple Mail Transfer Protocol) service
• NNTP (Network News Transfer Protocol) service
Windows Server 2003 includes the.NET Framework and ASP.NET, which
provide support for mobile access. If you are installing Exchange
Server 2003 on a server running Windows 2000, Exchange Setup
automatically installs and enables the .NET Framework and ASP.NET.
Note For more information about the default service settings for
Windows Server 2003, search for the article 812519, “Services That Are
Turned Off by Default in Windows Server 2003,” on the Product Support
Services page of the Microsoft Web site at http://support.microsoft.com.
Exchange and Windows require both server licenses and client access licenses
(CALs). For information about licensing, see the Licensing page of the
Microsoft Web site at www.microsoft.com/licensing/.
To ensure that your Exchange servers are secure, you must disable any
unnecessary services after Setup is complete. For more information about
disabling services, see Module 3, “Securing Exchange Server 2003,” in
Demonstration: How to Run ForestPrep and DomainPrep

Your instructor will show a presentation that demonstrates how to run Setup by
using ForestPrep and DomainPrep.
Note Before you make any changes to your environment, you should have
thorough documentation of Active Directory and any existing Exchange
installations so that you can understand the impact of the changes and
troubleshoot any problems. Back up your existing installation if you are
upgrading Exchange, so that if you must restore your system later, you are
prepared.
Important The steps for running these switches are included for your
information. Do not attempt to do them in the classroom. If you perform these
steps in the classroom environment, you will leave your computer in an
incorrect state for upcoming practices.
To run ForestPrep The steps for running ForestPrep to prepare your Active Directory forest for
Exchange are as follows:
1. At the command prompt, type x:\setup.exe /forestprep where x is the drive
for your Exchange 2003 compact disc.
2. On the Welcome page of the Microsoft Exchange Installation Wizard, click
Next.
3. If prompted, accept the licensing agreement and then, on the Component
Selection page, click Next, and follow the steps in the wizard.
To run DomainPrep The steps for running DomainPrep to prepare your domain for Exchange are as
follows:
1. At the command prompt, type x:\setup.exe /domainprep where x is the
drive for your Exchange 2003 compact disc.
2. On the Welcome page of the Microsoft Exchange Installation Wizard, click
Next.
3. If prompted, accept the licensing agreement and then, on the Component
Selection page, click Next, and follow the steps in the wizard.
Components That Can Be Configured During Setup

After you have configured your environment to use Exchange, you are ready to
install Exchange. However, before you install Exchange, you should know
about the components that you can configure during Setup. The setup programs
for Exchange Server 2003 and Exchange Server 2003 Enterprise Edition
provide you with the ability to install, remove, or change the following
components:
! Microsoft Exchange Messaging and Collaboration Services. Select
Microsoft Exchange Messaging and Collaboration Services to install the
basic messaging components for Exchange. If you select this component,
you can also select three additional components:
• Microsoft Exchange Connector for Lotus Notes. Provides the
components necessary to share e-mail with Lotus Notes systems in
native Lotus Notes format.
• Microsoft Exchange Connector for Novell GroupWise. Provides the
components necessary to share e-mail with Novell GroupWise systems
in native GroupWise format.
• Microsoft Exchange Calendar Connector. Provides the components
necessary to share calendar information with Lotus Notes and Novell
GroupWise systems.
! Microsoft Exchange System Management Tools. Select Microsoft
Exchange System Management Tools to install the utilities that are
required for managing your Exchange server. These utilities include
Exchange System Manager (your primary utility for managing Exchange
objects) and a version of Active Directory Users and Computers that is used
to manage and mail-enable user objects. If you select this component, you
can select the following additional component:
• Microsoft Exchange 5.5 Administrator. Provides the Exchange 5.5
Administrator tool that you can use to manage Exchange 5.5 servers.
Demonstration: How to Install Exchange Server 2003

Your instructor will show a presentation that demonstrates how to install
Important The steps for installing Exchange Server 2003 are included for your
information. Do not attempt to do them in the classroom. If you perform these
steps in the classroom environment, you will leave your computer in an
incorrect state for upcoming practices.
To install Exchange The steps in the process of installing Exchange Server 2003 are as follows:
Server 2003
1. Log on to the server on which you want to install Exchange with an
account that has the appropriate permissions, and then insert the
Exchange Server 2003 CD into your CD-ROM drive.
2. Run Exchange 2003 setup from the compact disc.
3. In the Microsoft Exchange Server setup box, select Exchange
Deployment Tools, and then choose to install either the first
Exchange 2003 server or additional Exchange 2003 servers.
4. Complete all the steps in the Exchange Server Deployment Tool, and then
click Run Setup Now.
5. On the Component Selection page of the Microsoft Exchange Installation
Wizard, clear the Microsoft Exchange Messaging and Collaboration
Services check box.
6. On the Component Selection page, select Microsoft Exchange System
Management Tools.
7. On the Welcome page of the wizard, click Next.
8. On the End User License Agreement page, read the agreement. If you
agree to the terms, click I agree, and then click Next.
9. On the Product Identification page, specify your 25-digit product key, and
then click Next.
10. On the Component Selection page, select the desired action in the Action
column that corresponds with the component that you want to install, and
then click Next.
11. On the Installation Type page, select whether to create a new organization
or join an existing organization.
12. Follow the remainder of the instructions in the wizard. When the wizard
finishes, Exchange Server 2003 will be installed on your server.
What Is an Unattended Installation?

In addition to performing a standard installation of Exchange 2003, you can
also perform an unattended installation, which is an installation that proceeds
and completes without any prompting from a user. An unattended installation
uses an unattended initialization (.ini) file to provide answers to configuration
questions presented during Setup. After you create an .ini file, you can use the
file to perform any number of identical Exchange 2003 installations. Using the
unattended mode of Exchange 2003 Setup can significantly reduce the cost of
deploying Exchange servers—especially if you are deploying large numbers of
servers that will all be configured the same way.
When can you use an You can use an unattended installation when you are:
unattended installation?
! Installing the second or subsequent Exchange 2003 computers in your
organization.
! Installing Exchange 2003 System Management Tools.
! Running DomainPrep.
When can you not use You cannot use an unattended installation when you are:
an unattended
installation? ! Installing the first Exchange Server 2003 computer in an organization.
! Installing Exchange Server 2003 into a Windows cluster.
! Installing Exchange Server 2003 in an Exchange mixed-mode environment
(Exchange 5.5 and Exchange Server 2003).
! Performing any maintenance tasks—for example, when you are reinstalling
Exchange or performing a disaster recovery installation of Exchange.
How to Perform an Unattended Installation of Exchange Server 2003

Performing an unattended installation to install Exchange on a computer is
relatively simple.
To perform an The high-level steps for performing an unattended installation are as follows:
unattended installation
1. Create a predefined initialization (.ini) file.
2. Run Setup by using the .ini file.
3. Exchange is then automatically installed on the designated computers.
Options for unattended You can use the following options when performing an unattended installation:
installation
! Initialization file options:
• Run Setup by using the createunattend command-line switch to create
an initialization file. Your responses to the questions asked during Setup
will be stored in the initialization file. You can also use the initialization
file to run an unattended setup on other computers.
• Run Setup with the unattendfile command-line switch to install
Exchange 2003 by using the information provided by the initialization
file.
! Unattended Setup switch options. The most common switches that are used
for unattended installation include: /createunattend file_name.ini and
/unattendfile file_name.ini.
Note For more information about the Setup switches, see Setup Help. To
access Setup Help, type setup /? at the command prompt.
How to Verify That Installation of Exchange Server 2003 Was

Successful

After setup is complete, you should verify that installation was successful.
To verify that installation The steps to verify that installation of Exchange Server 2003 was successful are
was successful as follows:
1. Test Active Directory Users and Computers. Create a new mail-enabled user
account by using Active Directory Users and Computers.
2. Send a test message. Log on as the account that was delegated to be the
Exchange administrator during installation or the new account you just
created, create a messaging profile in Microsoft Office Outlook®, and then
send a test message.
3. Test Exchange System Manager. Log on as the account that was delegated
to be the Exchange administrator during installation. Start Exchange System
Manager. Expand the Exchange Organization object and expand all
subcontainers.
4. If any of the previous steps do not work, use the following utilities to
troubleshoot your setup.
Use this utility To do this
Services MMC Confirm that the Exchange services were created and
have started.
Event Viewer and the Identify any installation errors. The Exchange setup log
setup log file records information about the installation process. Any
failures are recorded in the log. The log file is at the root
of your installation drive and is named Exchange Server
Setup Progress.log.
Windows Explorer Confirm that the \Exchsrvr folder was created and has
the Exchange binaries and databases file in it.
Note For a list of folders and services created during the installation process,
see “Default File Locations and Services” under Additional Reading on the
Web page on the Student Materials compact disc.
Practice: Installing Exchange Server 2003

Instructions Read the following four scenarios and use the Exchange Server 2003 JDP
Technical Reference Guide job aid to determine the possible solution with a
partner. This job aid contains tips, common support issues, dependencies, and
in-depth explanations for installing Exchange Server 2003. You can browse the
content by using the Contents tab or the Search tab to help locate the
information that you need. When you and your partner have agreed on solutions
to the scenarios, discuss your solutions with the rest of the class.
If time permits at the end of this practice, browse the job aid to look for other
useful information.
Note To determine how to install Exchange Server 2003, reference the job aid
Joint Development Program (JDP) - Technical Reference Guide in the Job Aid
folder on the Student Materials compact disc.
Scenario 1 You are the messaging administrator for your company and are preparing to
deploy Exchange Server 2003. You have decided to recommend configuring
your Exchange servers on Windows Server 2003, Enterprise Edition, and need
to prepare a brief overview for upper management explaining the advantages of
your choice. What items must you include in your overview on the advantages
of deploying Exchange 2003 on Windows Server 2003, Enterprise Edition?
Windows Server 2003, Enterprise Edition, offers all the advantages of
Windows Server 2003, Standard Edition, and in addition:
• Supports 8-way PIII Xeon processors
• Supports 8-way P4 XeonMP processors (hyperthreaded)
• Support for up to 8-node clustering
• Mount point support
Note: See the Dependency Matrix section of the job aid for the advantages
of Windows Server 2003, Standard Edition and Enterprise Edition.
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
Scenario 2 You are preparing your final recommendations for your Exchange Server 2003
deployment and need to provide information on the features and differences
between Exchange Server 2003, Standard Edition and Enterprise Edition. What
features do each of these versions offer and how are they different?
Both editions support features such as:
• Database snapshot
• Microsoft Outlook Mobile Access and Microsoft ActiveSync®
• Recovery Storage Group
• Exchange Management Pack for Microsoft Operations Manager
• Server can act as a front end
The Standard Edition has the following limitations:

• 16GB database limit
• Supports only one mailbox store
• Supports only one public folder store
The Enterprise Edition supports the following additional features:

• Clustering
• Up to 20 databases per server
• X.400 connectors
Note: See the Dependency Matrix section of the job aid for a comparison of
Exchange Standard versus Enterprise editions.
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
Scenario 3 You are preparing to install your first server running Exchange Server 2003.
You start the installation process but Setup fails. To save time troubleshooting,
you decide to make a checklist of all the common dependencies that may
impact the running of Setup. What items must you include in your checklist?
Topology dependencies:
• All Active Directory Connectors (ADCs) must be upgraded to the
Exchange 2003 version before the first Exchange 2003 server can be
installed.
• The installation of the first Exchange 2003 ADC will increment all
connection agreement version numbers hosted on that ADC server.
• At least one Windows 2000 SP3 or Windows Server 2003 Global
Catalog server is available in the site.
• Exchange 2003 ForestPrep and DomainPrep.
• Front-end servers must be upgraded before back-end servers are
upgraded or installed (within the same administrative group).
Server dependencies:
• .NET Framework 1.1, Installed and Enabled
• ASP.NET Device Update 2 (DU2) Pack
• Operating system options:
• Windows 2000 SP3 or later (and 329938 if a cluster)
• Windows Server 2003
Upgrading to Exchange 2003:

• Must already be Exchange 2000 SP3 or later.
• Must already be Windows 2000 SP3 or later.
• After upgrading to Exchange 2003, you can upgrade to
Windows Server 2003 if required.
Note: See the Dependency Matrix section of the job aid for the common
dependencies for configuring Exchange 2003.
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
Scenario 4 You have just received approval to start your deployment of Exchange 2003
when one of your administrators mentions that there is one division of your
company that has deployed an Exchange 2000 server to take advantage of
Instant Messaging. You realize that there may be existing services that are
required by some of your divisions that you did not take into account in your
original Exchange 2003 design. What services have been retired and are no
longer supported by Exchange 2003?
The following components (services) featured in Exchange 2000 have been
retired in Exchange 2003:
• Instant Messaging Service
• Key Management Service (KMS)
• Chat Service
• Lotus cc:Mail Connector
• MSMail Connector
• Directory Synchronization (DXA) Connector
• Schedule+ Free/Busy Connector
Management and administration capabilities for the above components

have also been retired in Exchange 2003, which means that you cannot use
the 2003 version of the administration tools to manage these services.
Note: See the Tips section of the job aid, Tip 38, “Retirement List for
additional Exchange 2000 components that have been retired in
Exchange 2003.”
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
Lesson: Installing Exchange Server 2003 in a Clustered

Environment

Introduction Many companies need more reliability and availability than one server can
provide. Clusters are groups of server computers that work together to serve
client computers more efficiently. Clusters provide high availability to
companies that must have their Exchange Server 2003 system and services
available without interruption. This lesson introduces Exchange Server 2003
clustering concepts and explains how to install Exchange Server 2003 in a
clustered environment.
! Explain how Exchange Server 2003 uses Windows Clustering to improve
fault tolerance for your Exchange hardware.
! Describe the hardware requirements for an Exchange Server 2003 cluster.
! Describe the types of Exchange Server 2003 cluster configurations.
! Describe the recommended Exchange Server 2003 cluster configurations.
! Describe considerations for using clusters.
! Describe how failover occurs on an active/active vs. active/passive cluster.
! Describe the permissions that are required to install an Exchange virtual
server.
! Describe how Exchange Server 2003 is installed in a clustered environment.
Multimedia: How Exchange Server 2003 Uses Windows Clustering

This presentation shows how Exchange Server 2003 Enterprise Edition can use
Windows Clustering to improve fault tolerance for your Exchange hardware.
Tip To view the presentation How Exchange Server 2003 Uses Windows
Clustering outside of class, on your own, open the Web page on the Student
Materials compact disc, click Multimedia, and then click the title of the
presentation.
Important Clustering in Exchange 2003 relies on Windows Clustering. For

more information about types of Windows Server 2003 clusters, see “Clustering
Overview” under Additional Reading on the Web page on the Student
Clustering in Exchange Server 2003 is supported only by Windows 2000
Advanced Server or Datacenter Server SP4 or later; Windows Server 2003,
Enterprise Edition, and Windows Server 2003, Datacenter Edition. For more
information about Windows Clustering, see http://www.microsoft.com/
windowsserver2003/technologies/clustering/.
Hardware Requirements Checklist for an Exchange Server 2003

Cluster

To use an Exchange Server 2003 cluster, you must meet the following hardware
requirements:
! Two or more identical servers designated as the cluster nodes.
! A mass-storage controller and drives in each cluster node from which the
operating system starts on that node.
! A separate mass-storage controller (small computer system interface [SCSI]
or Fiber) that is independent of the controller that is used to start the
operating system.
! A shared disk, which is typically an external cabinet to which the mass-
storage controller is attached, and which is connected to all nodes in the
cluster.
! Two network adapters in each cluster node.
Note Adaptations of server clusters from OEMs may contain variations on

these components, may not contain all of the components, or may contain more
components than are listed. However, to receive Microsoft support, the entire
cluster must be listed in the Cluster category on the hardware compatibility list
(HCL). The most current Cluster HCL is available on the Hardware Driver
Quality page of the Microsoft Web site at http://www.microsoft.com/hwdq/hcl.
Types of Exchange Server 2003 Cluster Configurations

If your Exchange organization uses Exchange clustering, you can choose to
deploy Exchange by using either an active/active or an active/passive cluster
configuration.
The active/active cluster Exchange supports only two-node active/active clusters. In an active/active
configuration cluster, both nodes actively process requests. In a typical active/active
configuration, each node owns at least one Exchange Virtual Server (EVS). The
cluster is still considered an active/active cluster even if all the Exchange
Virtual Servers are owned by only one node in the cluster. Exchange supports
up to four Exchange Virtual Servers in a two-node active/active cluster.
Similar to active/passive clustering, when one node fails or is taken offline in
active/active clustering, the other node in the cluster takes over for the failed
node. Because the failover causes the other node to take on additional
processing, the overall performance of your Exchange cluster may be reduced.
The active/passive In an active/passive cluster, the cluster includes at least one passive node and
cluster configuration one or more active nodes. A node is active if it runs an instance of an Exchange
virtual server. A node is passive if it does not run an instance of Exchange
Virtual Server or any other application. A passive node is ready to take over the
tasks of an active node whenever a failover occurs on any active node. Whether
a node is active or passive may change over the lifetime of a node. After a
failover, the passive node that now runs the failed-over Exchange Virtual
Server becomes an active node, and the original node becomes a passive node.
In an active/passive cluster, the active node actively handles requests while the
passive node stands by waiting for another node to fail.
Recommended Exchange Server 2003 Cluster Configuration

Microsoft recommends active/passive cluster configurations because they:
! Scale as well as stand-alone Exchange servers. The virtual servers on an
active/passive cluster can host as many active mailboxes as a stand-alone
Exchange server can if the two systems have similar hardware
configurations. An active/active cluster can only host a maximum of 1,900
active mailboxes per node to ensure a reliable failover.
! Are more reliable. Exchange Virtual Server (EVSs) always fail over to a
fresh node.
! Have better failover performance. If an Exchange Virtual Server fails, a
passive node will pick up all operations and continue to service client
computers at a rate of performance that is close or equal to that of the
original node. Because a fresh passive node is available to take over for the
failed server, the performance of Exchange is minimally affected by a
failover.
! Will support clusters with up to eight nodes. Active/active configurations
will support only two nodes.
Microsoft recommends that you deploy more than one passive node in your
active/passive cluster to provide better risk management for your clustered
environment. In an eight node active/passive cluster, it is recommended that
you deploy two passive nodes and six active nodes to reduce the impact if
more than one active node in the cluster fails at the same time.
Note For detailed information about Exchange Clustering, see the white paper
Deploying Exchange 2000 Server Clusters on the Exchange page of the
Microsoft Web site at http://www.microsoft.com/exchange/techinfo/
deployment/2000/. This white paper was updated for Exchange 2000 SP3, and
most of the content in the paper is also applicable when deploying Exchange
Server 2003 clusters.
Considerations for Using Clusters

Considerations for using the active/passive and active/active cluster
configurations are as follows:
! Because you must have at least one passive node in active/passive
clustering, the maximum number of Exchange Virtual Servers will be one
less than the number of nodes in your cluster. The following table shows the
maximum number of Exchange Virtual Servers possible for each operating
system. To achieve this number, you must also have a cluster with the
maximum number of nodes for that operating system.
Maximum number of Exchange
Version or edition of Windows Virtual Servers (EVSs)
Windows 2000 Advanced Server 1 EVS / 2 nodes

Windows 2000 Datacenter 3 EVSs / 4 nodes
Windows Server 2003, Enterprise Edition or 7 EVSs / 8 nodes
Datacenter Edition
! Exchange 2003 is limited to four storage groups per server. Storage groups
are collections of mailbox and public folder stores that share the same set of
transaction log files. Exchange 2003 supports four storage groups per
server—this is a physical limitation and applies to each node of a cluster as
well. This limitation may create problems with active/active configurations.
Active/passive configurations are not affected by this limitation. The
following table illustrates this limitation.
Exchange Virtual Server State Storage group names
Node 1 Active SG1, SG2, SG3

EVS1
Node 2 Active SG1, SG2
EVS2
In the example, the Exchange cluster includes five storage groups. If EVS2
on Node 2 fails over to Node 1, Node 1 will not be able to mount one of the
storage groups from Node 2 because Node 1 will have exceeded the
limitation of four storage groups for a single cluster node. As a result, EVS2
will not come online on Node 1. If Node 2 is still available, EVS2 will fail
over back to Node 2.
Note Exchange 2003 does support a fifth storage group, the Recovery
Storage Group, for backup and recovery purposes. However, the Recovery
Storage Group cannot be used to create new user mailboxes.
! When you deploy active/active or active/passive Exchange clusters, it is

important to proactively monitor the clusters’ virtual memory performance.
If Exchange runs low on virtual memory, or if virtual memory becomes
fragmented, you may need to fail over the Exchange Virtual Servers, restart
all the services on the node, and then fail back the Exchange Virtual
Servers. Failback is the process of returning resources to their original node
after the node becomes available again.
Note For information about how to monitor virtual memory performance,

see Module 13, “Performing Preventive Maintenance,” in Course 2400,
Implementing and Managing Microsoft Exchange Server 2003.
How Failover Occurs on an Active/Active Cluster vs. an

Active/Passive Cluster

Failover happens differently in active/active clusters from the way it does in
active/passive clusters.
How failover occurs on In the configuration shown on the preceding illustration, each node of the
an active/active cluster Exchange server cluster supports an Exchange Virtual Server (EVS). When one
of the nodes fails, the surviving node takes over the failed Exchange Virtual
Server and continues to service client computers.
How failover occurs on In this configuration, one or more nodes of the Exchange server cluster host
an active/passive cluster active Exchange Virtual Servers while one or more nodes remain passive. The
passive node is a dedicated server that is ready to take over an Exchange Virtual
Server if a failover occurs. Active/passive clusters set the node preference list of
all resource groups to a passive node that is not the primary node for any
resource group. The node preference list identifies the passive cluster node to
which resources should be moved during first failover.
Active/passive failover typically provides the fastest failover time because the
passive node does not support a virtual server during normal operations. The
passive node remains idle, waiting to take over a virtual server if one of the
active nodes fails.
Permissions Required to Install and Configure an Exchange Virtual

Server

The following table describes the permissions that you must have to create,
modify, and delete an Exchange Virtual Server.
You must To do this
Be a member of the local administrators group on Install Exchange

each node. When you make yourself a local
administrator on the node, you automatically
become a cluster administrator on that node. Also,
to install Exchange, you must be a cluster
administrator for the cluster on which you install
Exchange.
Have Exchange Full Administrator permissions at Create the first Exchange Virtual
the organizational level. Server in the organization
Have Exchange Full Administrator permissions at Create additional Exchange
the administrative group level for the administrative Virtual Servers, or modify or
group that contains the Exchange Virtual Server. delete an Exchange Virtual
Prior to installation, you must manually add the Server in an administrative
computer account to the Exchange Domain Servers group
group when you are using an account that only has
Exchange Full Administrator permissions at the
administrative group and not the organization level
or the cluster service account does not have
permissions as an Exchange Full Administrator at
the organization level.
Demonstration: How to Install Exchange Server 2003 in a Clustered

Environment

Exchange Server 2003 in a clustered environment.
Important The steps for installing Exchange Server 2003 in a clustered

environment are included for your information. Do not attempt to do them in
the classroom. If you perform these steps in the classroom environment, you
will leave your computer in an incorrect state for upcoming practices.
To install Exchange After you have created a Windows cluster, you must perform three steps to
Server 2003 in a install Exchange 2003 in either an active/passive cluster with up to eight nodes
clustered environment or in a two-node active/active cluster:
1. Prepare Active Directory for Exchange. If this is the first Exchange server
in your organization, you must extend the schema with ForestPrep. If this is
the first Exchange server in the domain, you must prepare the domain with
DomainPrep.
2. Install Exchange on each node:
• Ensure that Cluster service is running on each node. Use Cluster
Administrator to verify that Cluster service is installed and running in
each cluster node. This verification is required to successfully install the
cluster-aware version of Exchange.
• Ensure that IIS Services are running. To be able to install Exchange, you
must have the World Wide Web Publishing, NNTP, and SMTP services
installed and running on your server. By default, the World Wide Web
Publishing Service is installed in Windows 2000. By default, none of the
services are installed in Windows Server 2003.
• Install Microsoft Distributed Transaction Coordinator (MS DTC).

Before installing Exchange, you must first install MS DTC on the
cluster. MS DTC coordinates transactions that span multiple resources.
• Run Exchange Setup. You are installing the cluster-aware version of
Exchange on each node. Before installing Exchange on a node, it is
recommended that you move all cluster resources owned by the node to
another node.
Note Install Exchange completely on one node before you install it on

another node.
3. Create the Exchange Virtual Servers. The final step in configuring

Exchange on a Windows cluster is to create the Exchange Virtual Servers.
You need to repeat each task for each Exchange Virtual Server that you
want to add to your cluster. To create an Exchange Virtual Server, you must
create a static IP address, a unique network name, a shared physical disk,
and a Microsoft Exchange System Attendant resource:
a. Create an IP address resource. Use the New Resource Wizard to enter
the static IP address of the Exchange Virtual Server.
b. Create a network name resource. Use the New Resource Wizard to
create a network name and add the IP address resource for this Exchange
Virtual Server.
c. Add a disk resource to the Exchange Virtual Server. Use Cluster
Administrator to move existing disk resources or to create a new disk
resource that you want to associate with the Exchange Virtual Server.
Several disk resources should be used for each storage group’s
transaction logs and databases.
d. Create an Exchange System Attendant resource. Use the New Resource
Wizard to create a System Attendant resource for your Exchange Virtual
Server. Select Microsoft Exchange System Attendant, add both the
Network Name and Physical Disk resources for this Exchange Virtual
Server, and verify that the path to the shared physical disk resources is
correct.
Practice: Installing Exchange Server 2003 in a Clustered

Environment

Instructions Read the following five scenarios and discuss possible solutions with a partner.
When you and your partner have agreed on solutions to the scenarios, discuss
your solutions with the rest of the class.
Scenario 1 You are the messaging administrator for your company and have been asked to
prepare your departmental budget for the next budget year. You would like to
be able to cluster your Exchange servers to provide high availability to your
messaging environment. Before you present your budget requirements for the
next year, you must first identify the hardware components that you will need to
be able to cluster your Exchange servers. What hardware components must be
on your list?
To create a clustered solution for your Exchange messaging system, you
must have the following minimum hardware:
• Two or more identical servers that are listed on the Cluster HCL
designated as the cluster nodes.
• A mass-storage controller and drives for each cluster node from which
the operating system starts.
• A separate mass-storage controller (SCSI or Fiber) that is independent
of the controller that is used to start the operating system.
• A shared disk.
• Two network adapters in each cluster node.
________________________________________________________________
________________________________________________________________
Scenario 2 As part of your plan for clustering your Exchange servers, you must make a
presentation to upper management that provides them with enough information
to justify your choice for the clustering model that you have chosen. Before you
create your presentation, you must identify the basic clustering configurations
that are available for Exchange Server 2003. What types of cluster
configurations can be used with Exchange 2003? How are they different?
Exchange clusters can be configured as active/active or active/passive
clusters:
• Exchange is supported on a two-node active/active cluster where both
nodes own Exchange virtual servers.
• Exchange is also supported on an active/passive cluster with up to eight
nodes, in which at least one node does not have any Exchange virtual
servers running and is ready to take over if another node fails.
_______________________________________________________________
_______________________________________________________________
Scenario 3 Now that you have identified which type of cluster configurations are supported
by Exchange, you must prepare to recommend which configuration you will use
for your company. You have decided that you want to recommend an
active/passive cluster. When you present this recommendation to upper
management, you know that they will want answers to the following questions:
! Why should they spend money on clustering at all?
! Why would they need to buy more expensive hardware for an active/active
configuration?
! Why choose active/passive clustering?
! Why would they want to spend money on servers that will not be used all
the time for an active/passive configuration?
What must you explain to upper management to justify your recommendations?

Explain to upper management that:
• Clustering will provide high availability to your Exchange
environment. If an Exchange server fails, Exchange resources can be
failed over to another node in the cluster to process employee requests.
• If you configure an active/active cluster, you will need more expensive
hardware on each node so that if an Exchange virtual server fails over
from one active node to the other, the level of performance on the
computers used by employees will remain the same.
• Active/passive is the recommended configuration for Exchange clusters
because they scale better, are more reliable, and will support clusters
with up to eight nodes on Exchange Server 2003 and
Windows Server 2003.
• If you choose an active/passive cluster configuration, no other resources
will be running on the passive node, so the level of performance when
an Exchange Virtual Server fails over will remain the same on the
computers used by employees.
_______________________________________________________________
_______________________________________________________________
Scenario 4 Your budget has been approved and you have hired contract employees to
install and configure your Exchange clusters. To install Exchange on your
cluster, you have decided to create a Cluster Installers group that has the
appropriate permissions to perform the installation. What permissions must be
granted to the Cluster Installers group so they can install Exchange, assuming
that ForestPrep and DomainPrep have already been performed?
To have the members of the Cluster Installers group that you create be
able to install your Exchange cluster, the cluster service account requires
Exchange Full Administrator permissions at the organization level and the
Cluster Installers group must:
• Be a member of the local administrators group on each of the cluster
nodes, which will automatically make them a cluster administrator for
that node.
• Have Exchange Full Administrator permissions at the organization
level to create the first Exchange virtual server in the organization.
• Have Exchange Full Administrator permissions for the administrative
groups that will contain the Exchange virtual servers they will be
installing. Remember to add the computer accounts to the Exchange
Domain Servers group prior to running the setup in this case.
________________________________________________________________
________________________________________________________________
Scenario 5 You have decided that if you provide the contractors with a checklist for the
installation, they could do the installs more quickly, and it will be less likely
that they will miss something. Before you create your checklist, you must
organize your thoughts. What are the high-level tasks that the installers must
perform to install Exchange on your cluster?
To install Exchange on each node of the cluster, you must:
• Ensure that Cluster service is running on each node.
• Ensure that IIS and the required IIS components are running.
• Install MS DTC.
• Run Exchange Setup.
• Create the Exchange virtual servers by creating a static IP address, a
unique network name, a shared physical disk, and an Exchange System
Attendant resource.
________________________________________________________________
________________________________________________________________
Lesson: Installing and Using Exchange Management

Tools and Utilities

Introduction If you want to administer Exchange Server 2003 quickly and efficiently, you
must know what each of the Exchange management tools and utilities was
designed to help you do. This lesson describes the management tools and
utilities and explains how to install and use them. The lesson also explains how
to create a custom Microsoft Management Console (MMC) for Exchange
administration, so that you can save yourself even more time.
! Describe the management tools and utilities that are used for managing
Exchange.
! List the platforms from which you can administer Exchange.
! Describe the permissions required to access objects in Exchange System
Manager.
! Install Exchange System Manager.
! Install and run Windows Support Tools.
! Create a custom MMC for Exchange administration.
! Choose the correct tool or utility to perform Exchange management tasks.
Management Tools and Utilities for Administering Exchange

Exchange System Manager and Active Directory Users and Computers are the
primary utilities that you use to administer your Exchange server. However, to
be able to fully administer Exchange, you must use a combination of Windows,
Active Directory, and Exchange tools and utilities.
Tools and utilities The tools and utilities that you will use include:
! Exchange System Manager. This utility is an MMC snap-in that you can use
to manage an entire Exchange enterprise from a single console. Exchange
administrators use this utility to manage and configure Exchange objects,
such as address lists, public folders, servers, routing, and policies. Exchange
System Manager is installed as part of Exchange Setup and can be added to
an administrative workstation by running Exchange Setup and selecting the
Microsoft Exchange System Management Tools option.
! Active Directory Users and Computers. You can use Active Directory Users
and Computers to manage Active Directory users, groups, and computers.
Active Directory Users and Computers can be installed on computers
running Windows 2000 Server, Windows 2000 Professional,
Windows Server 2003, or Windows XP. To manage Exchange recipients,
however, you must also install the Exchange System Management Tools on
these computers. When you install the Exchange System Management
Tools, you also install a version of Active Directory Users and Computers
that you or other users can use to create and manage Exchange recipients,
such as creating mail-enabled users and groups.
Important You must install Exchange System Manager on any server or

workstation that you intend to use to manage Exchange recipients by using
Active Directory Users and Computers.
! Cluster Administrator. This utility is a cluster management utility that

allows you to configure, control, and monitor clusters. You can install
Cluster Administrator on a server running Windows 2000 Server,
Windows Server 2003, or Windows XP, regardless of whether it is a cluster
node. You must manage clustered Exchange services by using Cluster
Administrator and not by using the Services MMC snap-in. You can use
Cluster Administrator to manage cluster objects, establish groups, initiate
failover, handle maintenance, and monitor cluster activity. You can install a
copy of the Cluster Administrator on your computer by installing the
Microsoft Windows Server 2003 Administration Tools Pack, which is a
collection of utilities that allow you to manage your servers running
Windows Server 2003.
! ADSI Edit. This utility, also called Adsiedit.exe, is an Active Directory
editor that uses Active Directory Services Interface (ADSI) to view and
modify objects in Active Directory, including the attributes and properties
of a specific user or group. You use ADSI Edit to perform administrative
tasks that cannot be performed by using Exchange System Manager or
Active Directory Users and Computers. For example, you use ADSI Edit to
specify how the full name attribute is generated. ADSI Edit is included with
Windows Support Tools for Windows 2000 and Windows Server 2003.
! LDP utility. This utility, also called the Active Directory Administration
utility or Ldp.exe, is a generic Lightweight Directory Access Protocol
(LDAP) utility that you can use to connect to an LDAP-compatible
directory. The LDP utility is similar to ADSI Edit in that it enables you to
view and modify objects in Active Directory. For example, you can view
replication information of objects, such as when the object was last
replicated. The LDP utility is included in Windows Support Tools for
Windows 2000 and Windows Server 2003.
! Active Directory Schema snap-in. This utility is an MMC snap-in that you
can use to view attribute and class configuration. It is different from ADSI
Edit and the LDP utility in that you cannot view instances of an object, such
as a specific user. You can use the Active Directory Schema snap-in to
modify or deactivate attributes and classes or change which attributes are
replicated to the Global Catalog check box. Active Directory Schema is not
available by default as an MMC snap-in; you must add it manually by
registering the Schmmgmt dynamic-link library (DLL), and then by adding
the snap-in to an MMC console.
Caution If the forest functional level is not set to Windows Server 2003,
adding a new attribute to the global catalog will cause a full synchronization
of the global catalog.
! IIS snap-in. The integration of IIS with Exchange provides additional

Internet protocols that enable Internet clients to gain access to mailbox data
in Exchange. One of those protocols, Hypertext Transfer Protocol (HTTP),
is the underlying protocol used by the World Wide Web. Exchange supports
HTTP to provide Microsoft Outlook Web Access clients with access to
Exchange data, such as public folders, mailbox information, and folder
searches. The IIS snap-in is used to manage and configure the HTTP virtual
server. A virtual server is a server that allows you to host different protocols
or protocol settings on the same physical server. The snap-in is part of the
default Windows administrative utilities.
Note For information about IIS 6.0 in Windows Server 2003, see the
Microsoft Web site at http://www.microsoft.com/windowsserver2003/iis/.
! DNS snap-in. This is the primary utility that you use to manage Domain
DNS servers. In an Exchange environment, you must ensure that your DNS
server includes resource records for your Exchange servers, including
adding mail exchanger (MX) and address (A) resource records. The DNS
snap-in is a Windows utility that is installed when DNS is installed on a
Windows server. To access the DNS snap-in, install the Microsoft
Windows Server 2003 Administration Tools Pack on your computer. Or, if
DNS is installed on your computer, click Start, point to Programs, point to
Administrative Tools, and click the DNS console.
Platforms from Which You Can Administer Exchange

Exchange System Manager can be installed and used on the following
platforms:
! Windows 2000 Server SP3
! Windows 2000 Professional SP3
! Windows Server 2003 family
! Windows XP SP1
Prerequisites for To install Exchange System Manager on Windows XP, the following
installing Exchange prerequisite software and configuration are required:
System Manager
! The Windows XP computer must belong to a domain in the Active
Directory forest where the Exchange Servers exist.
! You must be running at least Windows XP with SP1.
! The Windows Server 2003 Administration Tools Pack must be installed.
! The SMTP service in Windows XP must be installed.
It is not necessary to have the SMTP service running; the service just needs
to be installed on the local administrative workstation, and it can then be
disabled.
Note For more information about the requirements to install Exchange system
management tools on different Windows platforms, see Exchange Server
Deployment Tools on the Exchange Server 2003 compact disc.
Important If Outlook is running on the same client computer as the Exchange

Management components, Exchange System Manager will warn you that the
existing version of MAPI32 is not compatible. In this scenario, some of the
property pages in Exchange System Manager will not work correctly. You
should not install the Exchange Server 2003 management components and
Outlook on the same workstation. If you already have Outlook installed, you
can use Terminal Services to run Exchange System Manager from your
Exchange server instead of installing Exchange System Manager on your
workstation.
Permissions Required to Access Objects in Exchange System

Manager

To be able to administer Exchange by using Exchange System Manager, you
must be a member of the same Active Directory domain as the Exchange
server, and you must have permissions to access the Exchange object that you
want to manage. By default, the only account that can fully administer
Exchange is the account that is used during the initial setup of the Exchange
organization. To change accounts, you must delegate additional permissions to
other user accounts.
Permissions Exchange supports three permissions that are used for administration:
! Exchange Full Administrator. If you have this permission, you can fully
administer Exchange system information (for example, add, delete, and
rename objects) and modify permissions. Delegate this role to
administrators who need to configure and control access to your e-mail
system.
! Exchange Administrator. If you have this permission, you can fully
administer Exchange system information. However, you cannot modify
permissions. Delegate this role to users or groups responsible for the day-to-
day administration of Exchange (for example, adding, deleting, and
renaming objects).
! Exchange View Only Administrator. If you have this permission, you can
view Exchange configuration information. Delegate this role to
administrators who must view organization information but do not need to
modify it.
You can grant these roles to the Organization object or to an Administrative

Group object by using the Exchange Administration Delegation Wizard in
Exchange System Manager. This wizard simplifies delegation of Exchange
permissions.
Demonstration: How to Install Exchange System Manager

Exchange System Manager.
Important The steps for installing Exchange System Manager are included for
your information. Do not attempt to complete them in the classroom. If you
perform these steps in the classroom environment, you will leave your
computer in an incorrect state for upcoming practices.
To install Exchange To install Exchange System Manager, perform the following steps:
System Manager
1. Run Exchange 2003 setup from the compact disc.
2. In the Microsoft Exchange Server setup box, select Exchange
Deployment Tools and choose to install Exchange System Management
Tools Only.
3. Complete all steps in the Exchange Server Deployment Tool, and then click
Run Setup Now.
4. On the Component Selection page of the Microsoft Exchange Installation
Wizard, clear the Microsoft Exchange Messaging and Collaboration
Services check box.
5. On the Component Selection page, select Microsoft Exchange System
Management Tools.
How to Install and Run Windows Support Tools

Three of the tools that you will use to administer your Exchange environment
are Windows utilities: ADSI Edit, the LDP utility, and the Active Directory
Schema snap-in. To use ADSI Edit and the LDP utility, you must install
Windows Support Tools from the Windows Server 2003 CD. To use the Active
Directory Schema snap-in, you must register the DLL.
To install Windows To perform a typical installation for Windows Support Tools:
Support Tools
1. At a command prompt, type x:\support\tools\suptools.msi where x is the
location of the Support folder on a CD-ROM or local drive.
2. Follow the steps in the Windows Support Tools Setup Wizard.
To run ADSI Edit To run ADSI Edit, you can open the Adsiedit.msc console file by using
Windows Explorer or use the Add/Remove Snap-in option in MMC to add the
ADSI Edit snap-in to any .msc file. The ADSI Edit snap-in will not run unless
the Adsiedit.dll is registered. This registration will happen automatically if
support utilities are installed. However, if the support utility files are copied
instead of installed, then you must run the regsvr32 command on the
Adsiedit.dll before running the ADSI Edit snap-in.
To run the LDP utility To run the LDP utility, type Ldp.exe at the command prompt.
To install the Active To install the Active Directory Schema snap-in:
Directory Schema
snap-in 1. Register its DLL by typing Regsvr32 schmmgmt.dll at the command
prompt, and then press ENTER.
2. Add the snap-in by using the Add/Remove Snap-in menu option in MMC.
Practice: Installing In this practice, you will install Windows Support Tools for
Windows Support Tools Windows Server 2003.
! To prepare for this practice

1. Start up 2400_London-Virtual PC, if it is not already started.
2. Log on as NWTraders\LondonAdmin with a password of P@ssw0rd.
Note This procedure may take five minutes to complete before you can
continue.
! To install Windows Support Tools

1. On your desktop, click Start, click Run, type c:\Moc\2400\Practices\
Mod01\suprttools\suptools.msi and then click OK.
2. On the Welcome to the Windows Support Tools Setup Wizard page,
click Next.
3. On the End User License Agreement page, click I Agree, and then click
Next.
4. On the User Information page, type your name and organization in the
appropriate boxes, and then click Next.
5. On the Destination Directory page, click Install Now.
6. On the Completing the Windows Support Tools Setup Wizard page,
click Finish.
7. On your desktop, click Start, point to All Programs, and then verify that
Windows Support Tools is on the menu.
Why do you need to install the Windows Support Tools?

The Windows Support Tools include dozens of utilities that you will
need to manage your Exchange server. Without these utilities, you
will be unable to perform tasks such as editing advanced Active
Directory properties (ADSIEdit) and diagnosing domain controller
issues (DCdiag).
What are some of the tools not mentioned in this module that are
included with Windows Support Tools?
Answers will vary. A list of all tools is in the Support Tools Help,
launched from the Windows Support Tools group on the Start
menu.
How to Create a Custom MMC for Exchange Administration

Exchange System Manager is the main utility that you will use to manage an
Exchange organization. However, you can also create a custom MMC to save
yourself even more time. Two MMC snap-ins are available with Exchange
Server 2003 that you can add individually to a custom MMC: Exchange
Message Tracking Center, which is used to track messages in Exchange, and
Exchange System.
Types of extensions The Exchange System snap-in provides several extensions that are included in
the snap-in by default. You can disable these extensions if required. The
extensions include:
! Exchange Protocols. You can use the Exchange Protocols extension to
enable and disable the extensions for Exchange protocols.
! Exchange Servers. You can use the Exchange Servers extension to enable
and disable the extensions for Exchange components such as the Exchange
store.
! Exchange System. You can use the Exchange Systems extension to enable
and disable the extensions for Exchange components such as connectors.
To create a custom MMC The high-level steps for creating a custom MMC are as follows:
1. On your desktop, click Start, click Run, type mmc and then click OK.
2. In the Console1 window, add the Exchange System snap-in.
3. On the Extensions tab, select the snap-in from the Snap-ins that can be
extended box.
4. Set what extensions you want to include in the Available extensions box.
For example, if you want to create a console that does not allow someone to
have access to the Queue Viewer object, clear the Queue Viewer check
box in the list of extensions for Exchange System, and the Queue Viewer
object will not be displayed in the console. Or, if you want to create a
console that lets you administer Exchange objects and users, add both the
Exchange System snap-in and the Active Directory Users and Computers
snap-in to the MMC.
5. Save the console and distribute it.
Detailed steps for creating a custom MMC are included in the practice that
follows.
Practice: Creating a In this practice, you will create a custom MMC that can be used to manage
custom MMC Exchange and Windows components and services.
1. On your desktop, click Start, click Run, type mmc and then click OK.
2. In the Console1 window, on the menu, click File, and then click
Add/Remove Snap-in.
3. In the Add/Remove Snap-in dialog box, click Add.
4. In the Add Standalone Snap-in dialog box, click Active Directory Users
and Computers, and then click Add.
5. In the Add Standalone Snap-in dialog box, click Exchange System, and
then click Add.
6. In the Change Domain Controller dialog box, click OK, and in the Add
Standalone Snap-in dialog box, click Close.
7. In the Add/Remove Snap-in dialog box, verify that both Active Directory
Users and Computers and Northwind Traders (Exchange) are listed, and
then click OK.
8. In console root, verify that both Active Directory Users and Computers and
Northwind Traders (Exchange) are listed.
9. On the Console1 menu, click File, and then click Save As.
10. In the Save As dialog box, in the shortcut toolbar, click Desktop, in the File
name box, type My MMC.msc and then click Save.
11. Close My MMC, and then verify that My MMC exists on the desktop.
In an environment with multiple domain controllers, how would you
define which domain controller is used to populate your Exchange
System Manager console with information?
You would need to create a custom MMC. During creation of the
MMC, identify the domain controller that will be used to provide
the data that is displayed in Exchange System Manager.
! To prepare for the next module

1. In 2400_London-Virtual PC, on the menu, click PC, and then click Shut
Down.
2. In the Shut Down dialog box, click Save PC state and keep changes,
verify that the Commit hard drive changes now checkbox is selected, and
then click OK.
3. Restart 2400_London-Virtual PC.
Practice: Choosing Exchange Management Tools and Utilities

Instructions Read the scenarios in the left column of the table, choose which utility or tool
you would use to accomplish the task, and write it in the column on the right.
When you are finished, discuss your answers with the class.
Important Exchange management utilities include Exchange System Manager,

Active Directory Users and Computers, Cluster Administrator, ADSI Edit, the
LDP utility, the Active Directory Schema snap-in, the IIS snap-in, and the DNS
snap-in.
Scenarios Scenario Utility or tool
You are preparing to install your first Exchange server, DNS snap-in
and you must verify that resource records have been
configured for the server so that it will be able to
receive e-mail for your company. What utility can you
use to verify whether resource records exist for your
Exchange server?
You have an Exchange cluster, and you want to Cluster Administrator
configure a resource group on the cluster. What utility
can you use to configure the resource group?
You are experiencing problems with Active Directory The LDP utility
replication and want to find the last time an object was
replicated. What utility can you use to view replication
information about an Active Directory object?
You have just completed your installation of Exchange System Manager
Exchange. You must start configuring your Exchange
server to meet your company’s requirements. What
utility can you use to configure components of
Exchange?
(continued)
Scenario Utility or tool
You just installed Exchange. You notice that when you ADSI Edit
create a new user, the full name for the user is not
displayed the way you want it to appear. What utility
can you use to change how the full name is generated?
Active Directory was deployed in your company long Active Directory Users and
before you deployed Exchange. You are not going to Computers
move any e-mail from your existing mail system, but
you want to be able to create Exchange mailboxes for
all of your existing users. What utility can you use to
create mailboxes for your existing users?
Your company has decided to use Outlook Web IIS snap-in
Access, and you have been told that you must be able
to capture as much information as possible for the
HTTP protocol that Outlook Web Access uses. What
utility can you use to enable and configure protocol
logging for HTTP?
You just installed Exchange and are using Active Active Directory Schema
Directory Users and Computers to look at a mail- snap-in
enabled user. You notice that there is an option called
custom attributes. You are concerned that this
information may not be replicated to the global
catalog. What utility can you use to view whether the
attribute in Active Directory is replicated to the global
catalog?
Lesson: Upgrading from Exchange 2000 Server to


Introduction If your company is already using Exchange 2000 Server, and you want to move
to Exchange Server 2003, you must know how to upgrade your Exchange
organization. This lesson compares the features of Exchange 2000 Server and
Exchange Server 2003 to help you understand why Exchange 2003 might be the
best server for your company. The lesson then explains the requirements and
the procedure for upgrading to Exchange Server 2003.
! Describe the differences between Exchange 2000 and Exchange 2003.
! Explain the requirements for upgrading to Exchange 2003.
! Describe how to upgrade from Exchange 2000 to Exchange 2003.
The Differences Between Exchange 2000 Server and


Exchange Server 2003 is a minor upgrade from Exchange 2000. This topic
describes what is new in Exchange 2003 and what has been removed since
Exchange 2000.
What is new in The following table lists the new features and performance improvements that
Exchange 2003? have been added to Exchange Server 2003.
Category Specific feature or improvement
Improved client access • Exchange 2003 running on Windows Server 2003

can be configured to enable Outlook 2003 to connect
to Exchange by using RPC over HTTP.
• Configuration of Mobile Services enables users with
mobile devices to connect to Exchange.
Improved security • Helps control unsolicited commercial e-mail,
commonly called junk e-mail or spam, by using
filters and by providing the ability to use block list
services. Block lists are lists of known senders of
unsolicited commercial e-mail.
• Supports Internet Protocol security (IPSec) for
securing communication between Exchange front-
end and back-end cluster servers when
Exchange 2003 is running on Windows Server 2003.
(continued)
Category Specific feature or improvement
Improved management • Supports the Windows Server 2003 Volume Shadow

Copy service to allow administrators to perform
snap-shot backups of their Exchange servers.
• Has built-in support for Microsoft Operations
Manager, which allows administrators to automate
the monitoring of their Exchange servers.
• Supports up to 8-node clustering when
Exchange 2003 is running on Windows Server 2003,
Enterprise Edition or Datacenter Edition.
New deployment and Exchange Server Deployment Tools (ExDeploy) is a
upgrade utilities new group of utilities and documentation that help you
prepare your environment and deploy Exchange.
Improved Active Directory The Active Directory Connector management console
Connector utilities now contains an ADC Tools option. ADC Tools is a
collection of wizards and utilities that you can use to set
up connection agreements between your current Active
Directory and Exchange 5.5 Directory.
New public folder migration You can use this new utility, called Microsoft Exchange
utility Public Folder Migration Tool (pfMigrate), to migrate
and replicate system folders and public folders to a new
server.
What has been The following table lists the four Exchange 2000 features that have been
removed? discontinued or moved to other product lines.
Feature Description and reason
Support for real-time Support for real-time collaboration features such as

collaboration features chat, Instant Messaging, conferencing (by using
Exchange Conferencing Server), and multimedia
messaging (also known as unified messaging) is not
included in Exchange Server 2003. Instant messaging
(IM) will be provided by a new dedicated real-time
communication and collaboration server called
Microsoft Office Real-Time Communications
Server 2003.
Support for MS Mail and Support for exchanging messages in native format with
Lotus cc:Mail connectors MS Mail and Lotus cc:Mail has been removed.
Drive M mapping The Exchange store used to be mapped to drive M on an
Exchange server to provide file system access to the
Exchange store. Drive M mapping is disabled by default
in Exchange Server 2003, because in some cases the
mailbox store would become corrupted by operations
such as running a file-level virus scanner on drive M.
Key Management Service This service works with Windows 2000 Certificate
Services to create a public key infrastructure (PKI) for
performing secure messaging. Exchange Server 2003
uses the PKI included with Windows Server 2003.
Note For more information about the drive M mapping, search for article
821836, “Drive M Mapping to IFS Is Not Present by Default in Exchange
Server 2003” on the Product Support Services page of the Microsoft Web site at
http://support.microsoft.com.
For additional information about new features in Exchange 2003, see the
Exchange page of the Microsoft Web site at http://www.microsoft.com/
exchange.
Requirements Checklist for Upgrading to Exchange Server 2003

To upgrade to Exchange Server 2003, you must meet all of the clean
installation requirements. You can use the Exchange Server Deployment Tools
to guide you through the process of meeting all the requirements for
installation.
Note Clean installation requirements are listed in “Lesson: Installing

Exchange Server 2003,” in Module 1, “Installing and Upgrading to Exchange
Server 2003” in Course 2400, Implementing and Managing Microsoft
You must also meet the following additional requirements:

! You must have performed the setup tasks while logged on with an account
that has the appropriate permissions.
! Setup must be able to contact a domain controller running Windows 2000
SP3 or later, or Windows Server 2003.
! You must upgrade all front-end servers in an administrative group before
you can upgrade or install Exchange Server 2003 on any other servers in
the administrative group. Setup ensures that front-end servers are upgraded
before back-end servers. Otherwise, Setup stops.
Note Exchange Server 2003 servers are compatible with Exchange 2000.
Therefore, users can access information that is located on Exchange 2000
servers by using an Exchange Server 2003 front-end server. For more
information about accessing information by using front-end servers, see
Module 7, “Implementing and Managing Client Access with Internet
Protocols,” in Course 2400, Implementing and Managing Microsoft
! Disable any unnecessary services after Setup is complete. If the following

services are disabled before you upgrade, Exchange 2003 Setup will enable
them automatically:
• Microsoft Exchange MTA Stacks (MSExchangeMTA)
• Microsoft Exchange Information Store (MSExchangeIS)
After Setup is complete, disable whatever services you don’t need.
! You must upgrade all versions of Active Directory Connector in the
organization to the version provided with Exchange Server 2003. The
Active Directory Connector synchronizes directory information from
Microsoft Exchange Server 5.5 directories to Active Directory. Setup
retrieves information about the versions of Active Directory Connector that
are running in the organization. If all Active Directory Connector versions
have been upgraded to the Exchange Server 2003 version, Setup will
proceed. However, if older versions of Active Directory Connector exist,
Setup will stop and identify the servers that are running older versions.
Note For more information about Active Directory Connector, see

Module 14, “Migrating Users from Exchange Server 5.5 to Exchange
Server 2003,” in Course 2400, Implementing and Managing Microsoft
! If the Microsoft Mobile Information Server (MMIS) Exchange Event Sink

component was installed on an Exchange 2000 server, you must remove the
component before you can upgrade that server to Exchange Server 2003.
Mobile Information Server 2002 extends the reach of Exchange to mobile
users to allow them to browse and synchronize their Inbox information.
These event sinks, which are pieces of code that activate upon a defined
trigger, are no longer required because Exchange 2003 contains Outlook
Mobile Access that supports browse and synchronization components.
Note For more information about MMIS, see the Microsoft Mobile
Information Server page of the Microsoft Web site at
http://www.microsoft.com/miserver/.
! You must remove Instant Messaging, Chat, Key Management Service and
MS Mail or Lotus cc:Mail connectors. The Instant Messaging Service, Chat,
Key Management Service, MS Mail connector and Lotus cc:Mail connector
components are not supplied with Exchange Server 2003. If you want to
upgrade an existing Exchange 2000 server to Exchange Server 2003, and
one or more of these components is installed, you must remove the
components by using the Exchange 2000 Setup program before upgrading.
Note If you want to retain these services in your organization, do not

upgrade the Exchange 2000 servers that are running these components.
Instead, install Exchange Server 2003 on other servers in your organization.
For more information about Instant Messaging, Chat, and Key Management
Service, see Chapter 19, “Chat and Instant Messaging Services,” and
Chapter 24, “Security Sensitive Environments” in the Exchange 2000
Server Resource Kit on the TechNet page of the Microsoft Web site at
http://www.microsoft.com/technet.
! Third-party applications must be upgraded to support Exchange—for

example, backup software, antivirus software, and filtering software. As
part of your planning, ensure that all third-party software that you want to
use is compatible with Exchange Server 2003. In particular, determine if
any compatibility issues could result from the following new Exchange
Server 2003 features:
• Exchange-aware antivirus software. New features have been added to
the Virus Scanning Application Programming Interface (VSAPI) in
• Exchange-aware backup and restore software. New features have been
added in Exchange Server 2003, such as the Recovery Storage Group
and support for the Windows Volume Shadow Copy service.
• Exchange-aware enterprise management. New features and Windows
Management Instrumentation (WMI) providers have been added in
Exchange Server 2003. WMI consists of the interfaces through which
almost all Windows resources can be accessed, configured, managed,
and monitored.
Demonstration: How to Upgrade from Exchange 2000 Server to


The process of upgrading from Exchange 2000 Server to Exchange Server 2003
is relatively simple, but Exchange Server Deployment Tools (ExDeploy) makes
it even easier. ExDeploy consists of utilities and documentation that lead you
through the entire upgrade process, including running ForestPrep and
DomainPrep and installing Exchange Server 2003.
Your instructor will show a presentation that demonstrates how to use
ExDeploy to upgrade from Exchange 2000 Server to Exchange Server 2003 and
how to upgrade a cluster.
Important The steps for upgrading from Exchange 2000 to Exchange 2003 are
included for your information. Do not attempt to do them in the classroom. If
you perform these steps in the classroom environment, you will leave your
computer in an incorrect state for upcoming practices.
To start ExDeploy and To start ExDeploy and upgrade from Exchange 2000 Server to Exchange
upgrade to Exchange Server 2003, complete the following steps:
Server 2003
1. Insert the Exchange Server 2003 CD-ROM into your CD-ROM drive.
2. Open the Support\Exdeploy folder.
3. Double-click the ExDeploy.hta file.
4. Follow the step-by-step instructions in the Exchange Server Deployment
Tools documentation to upgrade from Exchange 2000 to Exchange 2003.
To upgrade a cluster If you upgrade an Exchange 2000 cluster to Exchange Server 2003, you must
upgrade each of the Exchange virtual servers and cluster nodes in your cluster
group to Exchange Server 2003, and you must upgrade each of the Exchange
Virtual Servers and each of the cluster nodes in your cluster one at a time.
Additionally, the servers that you upgrade to Exchange Server 2003 must be
running Exchange 2000 SP3. The following procedure shows an example of
how to upgrade an Exchange 2000 SP3 cluster with two nodes (Node 1 and
Node 2) and two Exchange Virtual Servers (EVS1 and EVS2). If your cluster
includes more than two nodes, modify the procedure as necessary: The steps for
upgrading a cluster are as follows:
1. Move any Exchange Virtual Servers to Node 2. You must do this to ensure
there are no Exchange Virtual Servers running on Node 1.
2. Upgrade Node 1 to Exchange Server 2003 again. Node 1 must have
Exchange 2000 SP3 or later installed on it. If Node 1 does not restart
automatically after you upgrade it to Exchange Server 2003, restart it
manually.
Note If the server that you are upgrading is not restarted, the server will be
using the old Exres.dll, and errors may occur. These errors may occur
because the Cluster service running on that node holds Exres.dll open
during the upgrade, so Exchange Setup cannot replace it during the upgrade.
3. Using Cluster Administrator, bring EVS 1 offline.

4. Using Cluster Administrator, move EVS 1 to Node 1.
5. Open Cluster Administrator on Node 1 (the node that you just upgraded to
Exchange Server 2003), right-click a group or System Attendant resource,
and select Upgrade Exchange Virtual Server.
6. Bring the cluster group online.
7. Repeat Steps 3 through 6 for EVS 2.
8. Upgrade Node 2 to Exchange Server 2003.
Note For information about upgrading from Exchange 5.5 to

Exchange 2003, see Module 14, “Migrating Users from Exchange
Server 5.5 to Exchange Server 2003,” in Course 2400, Implementing and
Managing Microsoft Exchange Server 2003.
Important Exchange 2003 modifies the Active Directory schema. Although

changes to the schema can be suppressed, they cannot be removed.
Therefore, to be able to restore your original schema, you must have backed
up the schema before you installed Exchange 2003. To restore an
Exchange 2003 server back to its original configuration in Exchange 2000,
you must have backed up your server before the upgrade.
Discussion: Installing and Upgrading to


Instructions Read the following five scenarios and discuss possible solutions with the class.
Scenario 1 You must install the first Exchange Server 2003 server in your organization.
You know that you need to prepare your forest and domain for the installation.
You have all required permissions to accomplish this task. What steps must you
take to prepare your forest and domain?
To prepare the forest, you must run ForestPrep one time in the Active
Directory forest in the domain where the schema master resides.
ForestPrep is an Exchange Setup switch that extends the Active Directory
schema to include Exchange-specific classes and attributes. ForestPrep also
creates the container object for the Exchange organization in Active
Directory.
To prepare your domains, you must run DomainPrep in the following
domains:
• The root domain
• All domains that will contain Exchange Server 2003 servers
• All domains that will contain Exchange Server 2003 mailbox-enabled
accounts or mail-enabled objects (such as accounts, contacts or groups),
even if no Exchange servers will be installed in these domains.
DomainPrep is an Exchange Setup switch that creates the groups and
permissions that are necessary for Exchange servers to read and modify
user attributes.
_______________________________________________________________
_______________________________________________________________
Scenario 2 You have just finished installing Exchange Server 2003, and you must verify
that everything is working correctly. What should you do to verify that the
Exchange installation was successful?
First, you should create a new mailbox and then verify that e-mail is
functioning by sending a test message. This verifies that your server’s
mailbox store is up and running and that routing and name resolution are
functioning correctly. You should then open Exchange System Manager
and verify that the objects that you expect to see listed do exist. If any of
these steps fail, you should:
• Verify that the Exchange services started correctly.
• Use the setup log and the event viewer to identify installation errors.
• Verify that the folder structure was created correctly.
________________________________________________________________
________________________________________________________________
Scenario 3 You are attempting to install Exchange 2003 on your cluster, but an error
message says you have insufficient permissions. This is not the first
Exchange 2003 server in your organization. What permission must you have to
install Exchange 2003 on the cluster?
To install Exchange, you must be a member of the local administrators
group on each of the cluster nodes. When you make yourself a local
administrator on the node, you automatically become a cluster
administrator on that node. Because you are adding an Exchange virtual
server to an existing organization, you must also have Exchange Full
Administrator permissions at the administrative group level for the
administrative group that contains the Exchange virtual server if you do
not have Exchange Full Administrator permissions at the organization
level.
________________________________________________________________
________________________________________________________________
Scenario 4 You must configure your computer to allow you to administer your
Exchange 2003 server. You know that your computer will support the
installation of Exchange System Manager, Windows Support Tools, and the
Active Directory Schema snap-in, and all you need to do is install them. How
can you accomplish this?
Use the Setup program on the Exchange 2003 installation CD to install
Exchange System Manager. Run the Support\Tools\Suptools.msi file on the
Windows Server 2003 installation CD to install Windows Support Tools.
To use the Active Directory Schema snap-in, register the DLL by typing
Regsvr32 schmmgmt.dll at the command prompt.
_______________________________________________________________
_______________________________________________________________
Scenario 5 Your company is currently running Exchange 2000 and is evaluating whether to
deploy Exchange 2003. You have the following business needs:
1. Clients running Outlook must be able to access their mailboxes over the
Internet.
2. Clients must be able to receive e-mail by using mobile devices, such as
Smartphones.
3. Administrators must be able to control the inflow of unsolicited commercial
e-mail.
4. Administrators would like to be able to take advantage of the snapshot
backup capability of the backup software in use at the company.
5. Digital signatures and message encryption are critical to company data
security.
Which of these business needs are addressed in Exchange 2003?

Answer: 1, 2, 3, and 4.
Exchange 2003 running on Windows Server 2003 can be configured to
enable Outlook 2003 to connect to Exchange by using RPC over HTTP.
Configuration of Mobile Services in Exchange enables users with mobile
devices to connect to Exchange.
Exchange 2003 supports features that control unsolicited commercial
e-mail, commonly called junk e-mail or spam, by using filters and the
ability to configure Exchange to use block list services.
Exchange 2003 supports the Windows Server 2003 Volume Shadow Copy
service to allow administrators to perform snapshot backups of their
Exchange servers.
Exchange Server 2003 no longer includes the Key Management Service.
The public key infrastructure (PKI) included with Windows Server 2003
now handles the key archival and recovery tasks that were performed by
the Key Management Service in Exchange 2000.
_______________________________________________________________
_______________________________________________________________
THIS PAGE INTENTIONALLY LEFT BLANK

0989701

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

0989701

Hochgeladen von

Copyright:

Verfügbare Formate

Module 1: Installing and

 2003 Microsoft Corporation. All rights reserved.

Important It is recommended that you use PowerPoint 2002 or later to display

Preparation tasks To prepare for this module:

How to Teach This Module

Lesson: Installing Exchange Server 2003

Lesson: Installing Exchange Server 2003 in a Clustered

Lesson: Installing and Using Exchange Management Tools and

Lesson: Upgrading from Exchange 2000 Server to

Discussion: Installing and Upgrading to Exchange Server 2003

*****************************ILLEGAL FOR NON-TRAINER USE******************************

Important Although installing Exchange Server 2003 results in a functioning

Objectives After completing this module, you will be able to:

Lesson: Installing Exchange Server 2003

*****************************ILLEGAL FOR NON-TRAINER USE******************************

Hardware and System Requirements for Exchange Server 2003

*****************************ILLEGAL FOR NON-TRAINER USE******************************

Processor Intel Pentium or compatible 233 megahertz (MHz) or faster

Processor Intel Pentium or compatible 1.6 gigahertz (GHz) or better

Based on the information provided, the calculator provides an estimated

Environment Requirements Checklist for Exchange Server 2003

*****************************ILLEGAL FOR NON-TRAINER USE******************************

Run the DCDiag utility. Domain Administrator

Note It is recommended you run ForestPrep on the Active Directory

Caution You cannot move computers that run Exchange between

! Run DomainPrep to prepare your domains for Exchange. DomainPrep is an

Demonstration: How to Run ForestPrep and DomainPrep

*****************************ILLEGAL FOR NON-TRAINER USE******************************

Components That Can Be Configured During Setup

*****************************ILLEGAL FOR NON-TRAINER USE******************************

Demonstration: How to Install Exchange Server 2003

*****************************ILLEGAL FOR NON-TRAINER USE******************************

What Is an Unattended Installation?

*****************************ILLEGAL FOR NON-TRAINER USE******************************

How to Perform an Unattended Installation of Exchange Server 2003

*****************************ILLEGAL FOR NON-TRAINER USE******************************

How to Verify That Installation of Exchange Server 2003 Was

*****************************ILLEGAL FOR NON-TRAINER USE******************************

Practice: Installing Exchange Server 2003

*****************************ILLEGAL FOR NON-TRAINER USE******************************

The Standard Edition has the following limitations:

The Enterprise Edition supports the following additional features:

Upgrading to Exchange 2003:

Management and administration capabilities for the above components

Lesson: Installing Exchange Server 2003 in a Clustered

*****************************ILLEGAL FOR NON-TRAINER USE******************************

Multimedia: How Exchange Server 2003 Uses Windows Clustering

*****************************ILLEGAL FOR NON-TRAINER USE******************************

Important Clustering in Exchange 2003 relies on Windows Clustering. For

Hardware Requirements Checklist for an Exchange Server 2003

*****************************ILLEGAL FOR NON-TRAINER USE******************************

Note Adaptations of server clusters from OEMs may contain variations on

Types of Exchange Server 2003 Cluster Configurations

*****************************ILLEGAL FOR NON-TRAINER USE******************************

Recommended Exchange Server 2003 Cluster Configuration

*****************************ILLEGAL FOR NON-TRAINER USE******************************

Considerations for Using Clusters

*****************************ILLEGAL FOR NON-TRAINER USE******************************

Windows 2000 Advanced Server 1 EVS / 2 nodes

Node 1 Active SG1, SG2, SG3

! When you deploy active/active or active/passive Exchange clusters, it is

Note For information about how to monitor virtual memory performance,

How Failover Occurs on an Active/Active Cluster vs. an

*****************************ILLEGAL FOR NON-TRAINER USE******************************

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**

*ILLEGAL FOR NON-TRAINER USE**