0989702

Module 2: Configuring
and Managing
Exchange Server 2003
Contents
Overview 1
Lesson: Creating and Applying Exchange
Policies 2
Lesson: Configuring Exchange Server 2003
for Proactive Management 20
Lesson: Adding, Removing, and Updating
Exchange Servers 47
Lesson: Managing Exchange Server 2003
in a Mixed Environment 56
Discussion: Configuring and Managing
Exchange Server 2003 59
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 2: Configuring and Managing Exchange Server 2003 iii
Instructor Notes
Presentation: This module teaches students how to configure and manage a newly installed
65 minutes computer running Microsoft® Exchange Server 2003 by using the tools in
Exchange Server 2003 and in the Microsoft Windows Server™ 2003 family.
Practices:
95 minutes After completing this module, students will be able to:
! Create and apply Exchange policies to simplify administration.
! Configure Exchange Server 2003 to proactively manage server
performance.
! Add, remove, and update Exchange servers.
! Manage Exchange Server 2003 in a mixed environment.
Required materials To teach this module, you need the following materials:
! Microsoft PowerPoint® file 2400B_02.ppt
! Module 2 video file 2400B_02_v05.wmv
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.
Preparation tasks To prepare for this module:

! Read all of the materials for this module.
! 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.
! Complete the demonstration that shows students how to use Connectix
Virtual PC, which is in the Introduction module of this course. All 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.
iv Module 2: Configuring and Managing Exchange Server 2003
How to Teach This Module

This section contains information that will help you to teach this module.
Instructor notes have been written only for the topics that required them.
If no student practice is included in a How-to topic, consider demonstrating the
task for students.
How to start Start this module by reminding students that Modules 1, 2, and 3 are steps in a
process. Module 1 discussed installing Exchange 2003. However, although
installing the server results in a functioning server, the server must still be
configured and secured to meet the requirements of a company. Module 2 is the
second step in this process—configuring and managing the Exchange 2003
server to run in your environment. Students get to perform many of these tasks
in the hands-on practices. Module 3 covers securing the Exchange server.
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 Students should use the majority of the time in this module completing the
module hands-on practices and discussions. We anticipate that total hands-on time for
the students will be about 1 hour and 35 minutes. Total time for your
presentation should be no more than 1 hour and 5 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.
Lesson: Creating and Applying Exchange Policies

This section describes the instructional methods for teaching this lesson.
What Is an Exchange Use this animated slide to explain why Exchange policies are useful and to
Policy? show a policy being applied to servers running Exchange.
Requirements for Use this slide to explain the requirements for creating and applying Exchange
Creating and Applying system policies. Discuss the high-level steps of the task. Then have the students
Exchange System complete the inline practice and answer any questions that they have.
Policies
Module 2: Configuring and Managing Exchange Server 2003 v
How to Create and Apply Use this slide to discuss the high-level steps of the task. Then have the students
System Policies complete the inline practice and answer any questions that they have.
Students will not create a server policy at this time. A server policy will be
created later in this module in the How to Enable Message Tracking topic.
How to Remove and Explain when it is necessary to perform these tasks. Then use this slide to
Override System discuss the high-level steps of the task. Have the students complete the inline
Policies practice and answer any questions that they have.
Recipient Policy Discuss multiple policies and their priority. Then discuss query and search
Priorities and Search criteria. Use the animated slide to show an example of what happens to the
Criteria default policy when an additional policy is applied to users in one office
location.
How to Create and Use this slide to discuss the high-level steps of the task. Then have the students
Configure Recipient complete the inline practice and answer any questions that they have.
Policies
Lesson: Configuring Exchange Server 2003 for Proactive

Management
Guidelines for Creating Start by confirming that all of your students understand what a store is and what
Stores and Storage storage groups are. Then discuss the high-level steps for creating a store and
Groups storage groups. Present the guidelines, provide any additional guidelines from
your own experience, and ask students if they have any more guidelines to add.
You may want to mention that consolidating servers can result in a performance
impact if Network News Transfer Protocol (NNTP) or public folders are also on
the same system. If students are interested, direct them to the “Exchange 2000
and Server Consolidation” white paper on the TechNet page of the Microsoft
Web site at http://www.microsoft.com/technet for more information about how
to scale their servers for multiple functions. Additionally, you may want to
mention that students should consider having public folders in their own storage
group, with no other stores, to keep transaction logs separate from mailbox
store transaction logs.
Finally, have the students complete the inline practice and answer any questions
that they have.
How to Configure Use this animated slide to discuss how to configure mailbox stores.
Mailbox Stores for
Preventive Maintenance
How to Configure Public Use this animated slide to discuss how to configure public folder stores.
Folder Stores for
Preventive Maintenance
How to Configure Discuss why it is important to configure service and resource monitoring.
Service and Resource Mention the Exchange services that are monitored by default. Discuss the
Monitoring guidelines for setting thresholds for additional services and resources that
Exchange monitors, including the fact that you need to run DiskPerf at a
command prompt to monitor free disk space. Discuss the high-level steps of the
task and then have the students complete the inline practice. Answer any
questions that they have.
vi Module 2: Configuring and Managing Exchange Server 2003
How to Configure Use this animated slide to help explain what notifications are and to discuss the
Notifications high-level steps of the task. Then have the students complete the inline practice
and answer any questions that they have.
How to Configure Describe the performance console snap-ins. Use the slide to discuss the high-
Performance Monitoring level steps of the task. Then have the students complete the inline practice and
Using the Performance answer any questions that they have.
Console
How to Configure Alerts Use this animated slide to help explain what alerts are and to discuss the high-
Using Performance Logs level steps of the task. The slide shows a message queue growing. When the
and Alerts message queue reaches the threshold configured for the alert, which is 25
messages in this scenario, an alert is automatically generated and sent to the
administrator.
Have the students complete the inline practice and answer any questions that
they have.
How to Enable Message Explain when this task is necessary. Use this animated slide to show what
Tracking message tracking is, what message tracking logs are, and to discuss the high-
level steps of the task. The animated slide shows a message being sent, which
causes the message tracking log file to be updated with information as
displayed in the tracking log graphic.
they have. If the students are interested, you may want to discuss how message
tracking is performed in Exchange 2003. For information about how message
tracking is performed, see the Exchange 2003 online Help documentation.
How to Configure Use this animated slide to explain what protocol logging is, what protocols are
Protocol Logging supported by Exchange, and to discuss the high-level steps of the task. The
animated slide shows what happens when Simple Mail Transfer Protocol
(SMTP) logging is enabled. In the animated slide, a user establishes an SMTP
session with their Exchange server. This causes the SMTP protocol log to be
updated with information as indicated in the log file graphic. The animated
slide then displays what protocols can be logged to a file, and finishes with the
high-level steps for enabling protocol logging on a virtual server.
they have.
Module 2: Configuring and Managing Exchange Server 2003 vii
Lesson: Adding, Removing, and Updating Exchange Servers

How to Add Virtual Use this animated slide to explain when it is necessary to implement multiple
Servers virtual servers and to discuss the high-level steps of the task. The animated slide
shows an environment with two SMTP virtual servers. The remote client
connects to a secure SMTP virtual server while the local client connects by
using unencrypted SMTP to the default virtual server. The animated slide then
shows that you may want to use additional virtual servers to segregate traffic
across ports. The slide finishes with the high-level steps for adding virtual
servers.
Be sure to mention that protocol virtual servers are not the same as clustered
virtual servers and that only a single instance of Exchange 2003 can run on a
single computer. Then have the students complete the inline practice and
answer any questions that they have.
How to Remove Servers Use this slide to show how to remove an Exchange server and to discuss the
high-level steps of the task.
How to Remove the First Use this slide to walk through the steps of the task. You may want to mention
Exchange Server in a that removing the last server in an organization should include removing
Routing Group Exchange information from Active Directory. For more information, search for
article 273478, “XADM: How to Completely Remove Exchange 2000 from
Active Directory” on the Product Support Services page of the Microsoft Web
site at http://support.microsoft.com/.
Best Practices for Use this topic to discuss types of updates and to show students where they can
Applying Product go to find updates and learn best practices for applying product updates. Have
Updates students complete the inline practice and answer any questions that they have.
Lesson: Managing Exchange Server 2003 in a Mixed Environment

This lesson should just be a quick summary of what components are no longer
included in Exchange Server 2003 and what the Exchange 2003 and
Exchange 2000 tools can be used for. Answer questions that students have and
then move on to the module summary discussion.
viii Module 2: Configuring and Managing Exchange Server 2003
Discussion: Configuring and Managing 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 do this activity with the entire class. Or, if you have time, have
students work in small groups to come up with solutions to the problems in the
scenarios and then 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.
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 the
questions are located so that they can use them to assess their own learning
outside of class.
Module 2: Configuring and Managing Exchange Server 2003 1
Overview
*****************************ILLEGAL FOR NON-TRAINER USE******************************

Introduction After you install Microsoft® Exchange Server 2003, you must configure the
server to run in your environment. Configuration tasks include setting up
Exchange policies to simplify administration and configuring Exchange server
so that you can proactively manage server performance. If you have both
Exchange Server 2003 and Microsoft Exchange 2000 Server in your messaging
system, you must also effectively manage this mixed environment.
Note This module describes how to configure and manage a newly installed
computer running Exchange Server 2003 by using the tools in Exchange
Server 2003 and in the Microsoft Windows Server™ 2003 family. For
information about the final tasks to perform to set up a new Exchange server in
your organization, see Module 3, “Securing Exchange Server 2003,” in
Course 2400, Implementing and Managing Microsoft Exchange Server 2003.
Objectives After completing this module, you will be able to:

! Create and apply Exchange policies to simplify administration.
! Configure Exchange Server 2003 to proactively manage server
performance.
! Add, remove, and update Exchange servers.
! Manage Exchange Server 2003 in a mixed environment.
2 Module 2: Configuring and Managing Exchange Server 2003
Lesson: Creating and Applying Exchange Policies

Introduction Rather than applying configuration settings manually to each Exchange object
in your messaging environment, you can use policies to apply settings to
multiple Exchange objects simultaneously. Policies can greatly simplify
Exchange administration.
Lesson objectives After completing this lesson, you will be able to:
! Explain the purpose of an Exchange policy and how policies simplify
Exchange administration.
! Describe the types of Exchange policies.
! Explain when to use Exchange policies.
! Describe the requirements for creating and applying Exchange system
policies.
! Create and apply system policies, including mailbox store policies, public
store policies, and server policies.
! Remove and override system policies.
! Explain recipient policy priorities and search criteria.
! Create and configure recipient policies.
What Is an Exchange Policy?

An Exchange policy is a collection of configuration settings that is applied to
one or more Exchange objects of the same type. Policies were introduced in
Exchange 2000, and they are designed to enable flexible and efficient
administration of large numbers of Exchange objects. For example, you can
implement a policy that controls the configuration settings across multiple
servers in your Exchange environment. When you need to change the
configuration of the servers, you can simply edit the policy and have the
changes applied to all the servers in a single operation.
Exchange policies Exchange policies are not the same as Group Policy settings in Microsoft
versus Group Policy Windows®. In Windows 2000 and later, administrators use Group Policy to
settings in Windows enhance and control users’ desktops. Windows policy information is stored in
Group Policy objects (GPOs), which are linked to selected containers in the
Microsoft Active Directory® directory service—containers such as sites,
domains, and organizational units. You can use Exchange policies to control
Exchange server, store, and recipient objects. Exchange policy information is
stored in Exchange policy objects, which are linked to selected Exchange
server, store, and recipient objects.
Note Recipients are mail-enabled or mailbox-enabled Active Directory objects

such as user accounts, contacts, groups, and folders. For more information
about recipients, see Module 4, “Managing Recipients,” in Course 2400,
Implementing and Managing Microsoft Exchange Server 2003.
Types of Exchange Policies

There are two types of Exchange policies: system policies and recipient
policies.
What are system System policies are policies that control the configuration settings for Exchange
policies? server and information store (mailbox store and public folder store) objects.
System policies reside in the System Policies container, which is created under
the Administrative Group object in Exchange System Manager. You can create
and apply three types of system policies:
! Mailbox store policies. You can use this type of system policy to configure
the properties of multiple mailbox store objects in one application. For
example, you can use mailbox store policies to apply storage limits,
indexing updates, maintenance intervals, mappings to public folder stores,
and offline address lists on multiple mailbox stores.
! Public store policies. You can use this type of system policy to configure
the properties of multiple public folder stores in one application. For
example, you can use public store policies to configure maintenance
schedules, replication intervals, storage limits, and index updates on
multiple public folder stores.
! Server policies. You can use this type of system policy to configure the
properties of multiple server objects in one application. For example, you
can use them to enable logging, message tracking, and log file maintenance
on multiple servers in your organization.
What are recipient Recipient policies are policies that you apply to recipient objects such as users,
policies? groups, contacts, and folders. These policies can control how e-mail addresses
are configured for recipient objects as well as enforce e-mail retention settings.
Exchange includes a default recipient policy that automatically generates e-mail
addresses for mail-enabled Exchange objects, including the Simple Mail
Transfer Protocol (SMTP) address that the can be used to send e-mail to a
recipient. Recipient policies must be configured for every SMTP domain for
which Exchange will be required to accept incoming SMTP messages.
Recipient policies appear in Exchange System Manager in the Recipient
Policies container of the Recipient object.
When to Use Exchange Policies

Depending on the number of Exchange servers, mailbox stores, and public
folder stores in your organization, you may not need to use system policies.
However, any organization can use recipient policies to simplify the
administration of recipient objects.
When to use system Although system policies will not benefit you if you have only one Exchange
policies server with one mailbox store and one public folder store in your organization,
you may want to use them if you think that you may add servers in the future.
Creating and applying a system policy is not more efficient than manually
configuring a single server, mailbox store, and public folder store but will save
time in the long term if you will be adding servers or stores to your
environment.
Exchange system policies are most useful in medium to large companies that
have multiple servers, mailbox stores, and public folder stores. Changes to
operational guidelines in these companies tend to result in significant
administrative changes to the Exchange organization, thereby affecting multiple
servers or stores. As a result, it becomes more efficient to create and apply a
system policy than to manually configure each individual server and store.
When to use recipient Unlike system policies, recipient policies are not necessarily linked to servers or
policies stores. As a result, you can use recipient policies to simplify administration
regardless of the number of Exchange servers, mailbox stores, and public folder
stores that you have in your organization. There are two common uses for
recipient policies:
! Use recipient policies to apply e-mail addresses for Active Directory
recipient objects. For example, the organization Northwind Traders recently
acquired Contoso, Ltd. All users in the former Contoso, Ltd. organization
must continue to receive messages at their @contoso.msft SMTP address.
The users must also be able to receive e-mail at their new @nwtraders.msft
SMTP address. Messages that are generated by all users must display
@nwtraders.msft as the Reply To address. In this case, the administrator
would define a recipient policy for the former Contoso, Ltd. personnel that
includes a primary SMTP address of @nwtraders.msft and a secondary
SMTP address of @contoso.msft.
! Use recipient policies to apply mailbox management settings for Active
Directory mailbox-enabled user objects. For example, the organization
Northwind Traders defines its employee job titles in Active Directory. The
administrator wants to configure Exchange to purge the Deleted Items
folder of all employees that are not executives when items in the Deleted
Items folder are 30 days old. To do so, she can create a recipient policy that
queries Active Directory for users whose job title is not equal to Executive
and then configure the policy to purge deleted items that are 30 days old.
Requirements for Creating and Applying Exchange System Policies

To create and apply Exchange system policies, you must have the required
permissions, create at least one System Policies container, and avoid system
policy conflict.
To have the required To create a system policy, you must have Exchange Administrator permissions
permissions in the administrative group container or the organization container in which a
System Policies container resides. To apply a system policy to an object, you
must also have Write permission for the object to which the system policy is to
be applied.
To create System You create a system policy by using a System Policies container in Exchange
Policies containers System Manager. Because this container does not exist by default, you must
create a System Policies container in your organization. You must create the
container before you can create any system policy. You can have as many as
one System Policy container in each administrative group.
The high-level steps to create a System Policies container are as follows:
1. Use Exchange System Manager to display Administrative Groups.
2. Browse to the administrative group that will be used to manage your
policies.
3. Use the administrative group context menu to create a System Policies
container.
The detailed steps for creating a System Policies container are included in the
practice at the end of this topic.
To avoid system policy Because you can apply only one system policy tab to a server or store object at
conflicts any given time, you should configure system policies so that each system policy
controls the settings on just one tab. You can apply multiple system policies to
the same object only when there is no conflict in the tabs that these system
policies control. If conflicts occur, you must remove the original conflicting
system policy before applying the new system policy. For example, if you have
two mailbox store policies with the Limits tab configured, you can apply only
one policy to a specific mailbox store. However, if you have two mailbox store
policies—one with the Limits tab configured and the other with the Database
tab configured—both policies can be applied to the same mailbox store.
Note It is a best practice to grant and restrict permissions for policy creation by
configuring Exchange Administrator permissions on the administrative groups
in which your System Policies containers reside. This ensures that only a few
designated administrators are able to create policies. Additionally, Exchange
administrators should have two Active Directory accounts: one that is their
primary user account and a second account that is only used to perform
administrative functions. Administrative functions should be performed by
using the Run As command with the administrative account.
Practice: Creating a In this practice, you will read a message from your team lead, Samantha Smith,
System Policies and then create a System Policies container.
container
Important You must complete this practice to complete other practices in this
course.
! To prepare for this practice

1. Start 2400_London-Virtual PC, if it is not already started.
2. Log on as NWTraders\LondonAdmin with a password of P@ssw0rd.
3. Run the script entitled “2400B_02_Setup.vbs” located in the
C:\MOC\2400\practices\Mod02 folder.
4. If it is not already open, open Microsoft Outlook® Web Access by using
Microsoft Internet Explorer to open the URL http://london/exchange/
londonadmin. When prompted for credentials, use nwtraders\londonadmin
with a password of P@ssw0rd.
5. Read the message with the subject “Configuring Exchange” from your team
lead, Samantha Smith.
Note This procedure may take five minutes to complete before you can
continue.
! To create a system policies container

1. Click Start, point to All Programs, point to Microsoft Exchange, and then
click System Manager.
2. In the console tree, right-click Northwind Traders (Exchange), and then
click Properties.
3. In the Northwind Traders Properties dialog box, on the General tab,
select the Display administrative groups check box, and then click OK.
4. When prompted to restart Exchange System Manager, click OK. Note that
you do not actually have to restart Exchange System Manager.
5. In Exchange System Manager, in the console tree, expand Administrative
Groups.
6. Right-click First Administrative Group, point to New, and then click
System Policy Container.
7. In the console tree, expand First Administrative Group and verify that the
System Policies container exists.
What is the impact of not creating a System Policies container?

You are unable to create any system, mailbox store, or public folder
store policies in your Exchange organization.
How to Create and Apply System Policies

You can create and apply any system policy—whether it is a server policy, a
mailbox store policy, or a public store policy—by using similar procedures.
You can use a system policy to control only a subset of the total number of
options that are configurable on any Exchange object. This means that when
you configure a system policy, you see only the options that can be controlled
by the system policy on the tabs of the system policy.
To create a system The high-level steps for creating a system policy are as follows:
policy
1. In Exchange System Manager, browse to a System Policies container.
2. Use the context menu to create a new system policy.
3. Use the New Policy dialog box and tabs to configure the appropriate
options.
The detailed steps for creating a system policy container are included in the
To apply a system policy After you create a system policy, you must apply it to the appropriate object.
When you apply a system policy, it takes effect immediately. Users do not need
to log off for the system policy to take effect.
The high-level steps to apply a system policy are as follows:
1. In Exchange System Manager, browse to the system policy that you want to
apply.
2. Using the context menu for the policy, click Add Mailbox Store for a
mailbox store policy, click Add Public Store for a public store policy, or
click Add Server for a server policy.
3. To apply the system policy to the object, locate and select the appropriate
object name.
4. Use the Policies tab of the object to verify that a policy has been applied to
the object. The Policies tab displays which policies have been applied to the
object and which tabs are controlled by the policy.
The detailed steps to apply a system policy are included in the practice that
follows.
Practice: Creating and In this practice, you will read an e-mail message and an attachment from your
applying system policies team lead, Samantha Smith, and then create a public store policy and a mailbox
store policy. You will create a server policy later in this module.
Important To complete this practice, you must first complete the practice
entitled “Practice: Creating a System Policies container,” in Module 2,
“Configuring and Managing Exchange Server 2003,” in Course 2400,

1. If it is not already open, open Outlook Web Access by using Internet
Explorer to open the URL http://london/exchange/londonadmin.
3. Read the attachment entitled policydetail.doc.
! To create and apply a public folder store policy

1. In Exchange System Manager, in the console tree, expand First
Administrative Group, click and then right-click System Policies, point to
New, and then click Public store policy.
2. In the New Policy dialog box, select the Limits check box, and then click
OK.
3. In the Properties dialog box, on the General tab, type Public Store
Storage Limits Policy and then click the Limits (Policy) tab.
4. On the Limits (Policy) tab, in the Storage limits area, select the Issue
warning at (KB) check box, and then type 50000
5. Select the Maximum item size (KB) check box, and then type 5000
6. In the Deletion settings area, type 10 to keep deleted items for 10 days.
7. In the Age limits area, select the Age limit for all folders in this store
(days) check box, type 1095 and then click OK.
8. In the details pane for System Policies, right-click the Public Store Storage
Limits Policy item, and then click Add Public Store.
9. In the Select the items to place under the control of this policy dialog
box, in the Enter the object names to select (examples) box, type Public
Folder Store (London) and then click OK.
10. In the Exchange System Manager dialog box, click Yes.
11. In the console tree, expand Servers, expand London, expand First Storage
Group, and then expand Public Folder Store (LONDON).
12. Right-click Public Folder Store (LONDON) and then click Properties.
13. In the Public Folder Store (LONDON) Properties dialog box, click
Policies.
14. On the Policies tab, verify that the Public Store Storage Limits Policy is
applied to the store, and then click OK.
You just created a policy that limits storage for a public folder. What
would you have to do to create a policy that defines the replication
settings for a public folder store?
When creating the policy, you would need to select the Replication
check box instead of the Limits check box. This would enable you
to configure the replication properties of a public folder store
policy.
! To create and apply a mailbox store policy

1. In the console tree, right-click System Policies, point to New, and then click
Mailbox store policy.
2. In the New Policy dialog box, select the Limits check box, and then click
OK.
3. In the Properties dialog box, on the General tab, in the Name box, type
Mailbox Store Storage Limits Policy and then click the Limits (Policy)
tab.
4. On the Limits (Policy) tab, in the Storage limits area, select the Issue
warning at (KB) check box, and then type 10
5. Select the Prohibit send at (KB) check box, and then type 40000
6. Select the Prohibit send and receive at (KB) check box, and then type
50000
7. In the Deletion settings area, type 30 to keep deleted items for 30 days, and
then type 30 to keep deleted mailboxes for 30 days.
8. Select the Do not permanently delete mailboxes and items until the store
has been backed up check box, and then click OK.
9. In the details pane for System Policies, right-click Mailbox Store Storage
Limits, and then click Add Mailbox Store.
box, in the Enter the object names to select (examples) box, type Mailbox
Store (London) and then click OK.
12. In the console tree, browse to Administrative Groups\First Administrative
Group\Servers\London\First Storage Group\Mailbox Store (London), right-
click Mailbox Store (London), and then click Properties.
13. In the Mailbox Store (LONDON) Properties dialog box, click Policies.
14. On the Policies tab, verify that the Mailbox Store Storage Limits Policy is
applied to the store, and then click OK.
You set the storage limit to issue a warning at 10 KB. Is this a

reasonable limit for a mailbox limit? Why or why not?
No, because 10 KB is only enough space for about 10 text-only
e-mail messages.
How to Remove and Override System Policies

Why remove a system After a system policy is applied to an object, you can no longer use the property
policy? pages of the object to modify the settings controlled by the policy. To change
the settings on the object, you must either modify the policy itself or remove the
policy from the object.
To remove a system To remove a system policy from an object:
policy
1. Use Exchange System Manager to locate the system policy object.
2. In the details pane of the system policy object, right-click the object that you
want to remove from the system policy.
3. Remove the object.
Note Removing a system policy from an object does not remove the settings
that were applied to the object. To modify the settings of an object after
removing a policy, you must use the object’s property pages.
Why override a system Depending on their business functions, some users in your organization may
policy? require that their mailboxes to be configured differently from the rest of the
users on the same mailbox store. You may also need to configure a small
number of folders differently from the rest of the folders on the same public
folder store. In both situations, you must override the system policies.
To override a system To override a mailbox store policy, you can either override policy settings
policy manually on each mailbox or move the users to a different mailbox store that
has the correct settings applied to it. To override a public store policy, you can
override policy settings on each folder or move the folders to a different public
folder store that has the correct settings applied to it.
Recipient Policy Priorities and Search Criteria

Multiple policies and Upon installation, Exchange Server 2003 generates a default recipient policy.
their priorities This default policy automatically creates SMTP and X.400 addresses for the
recipients. In addition to the default policy, you can create multiple recipient
policies and assign priorities to each one of the policies. The default policy has
the lowest priority and is always processed first so that higher priority policies
can override it as necessary. The policy with the highest priority is processed
last.
Query and search When you create a recipient policy, you must define the search criteria that
criteria determine the recipients to which the policy is applied. You define the search
criteria by using the Find Exchange Recipients Advanced tab to build a
Lightweight Directory Access Protocol (LDAP) query. This query filters Active
Directory to identify only the set of recipients for which the search criteria is
true. For example, as shown in the animated slide:
1. You work for a company that has offices in Europe and the United States.
2. All users are part of the default recipient policy.
3. Users in Europe must have an additional SMTP address defined for them.
To accomplish this, you create another recipient policy with a higher
priority than the default policy.
4. On this policy, you configure a query that searches Active Directory for
users whose office location is Europe. This causes the policy to be applied
only to users based in Europe.
How to Create and Configure Recipient Policies

To create and configure Depending on the purpose of the recipient policy, you can use either the E-mail
a recipient policy Address (Policy) tab or the Mailbox Manager Settings (Policy) tab to
configure a recipient policy. Use the E-mail Address (Policy) tab to configure
e-mail addresses for Active Directory recipients. Use the Mailbox Manager
Settings (Policy) tab to configure mailbox management settings for Active
Directory recipients. You create recipient policies in the Recipients container.
The high-level steps to create and configure a recipient policy are as follows:
1. In Exchange System Manager, locate the Recipient Policies container.
2. Use the context menu for the container to create a new recipient policy.
3. Configure the policy by setting the options on the appropriate tabs,
including building the query to select the set of recipients to which your
policy applies.
Recipient Update Service is the service that builds and maintains address
lists. Recipient Update Service polls Active Directory every 60 seconds for
updated recipient information. If this default schedule has been altered, or
you want to force a recipient policy to be applied, right-click the recipient
policy that you want to be applied and then click Apply this policy now.
The detailed steps to create and configure a recipient policy are included in the
To configure e-mail You use the E-Mail Addresses (Policy) tab to define primary and secondary
address settings e-mail addresses, which are used by external users to send messages to users in
your Exchange organization. If you create multiple e-mail addresses of the
same type in a recipient policy, the first one created is the primary e-mail
address for that address type. The primary address appears in the Reply To
field of messages that users send outside of your Exchange organization. Each
subsequent e-mail address defined in the policy is a secondary address for that
address type.
Use the variables in the following table to define e-mail address values in your
recipient policy.
Variable Value
%g Given Name (First Name)

%i Middle Initial
%s Surname (Last Name)
%d Display name
%m Exchange alias
%xs Uses first x letters of surname so that if x=2, the first 2 letters are used
%xg Uses first x letters of given name so that if x=2, the first 2 letters are used
By default, the SMTP address uses the alias of the recipient to define the left
side of the SMTP address. You can override this default by using variables. For
example, say that the default SMTP address for users is alias@domainname. To
generate the SMTP address firstname.lastname@domainname, you can create a
new recipient policy that specifies the SMTP address value as follows:
%g.%s@domainname
Although recipient policies can add additional e-mail addresses to user

accounts, removing these addresses from the policy will not remove them from
the user accounts. You must either remove them manually or by using a script.
To configure Mailbox You use the Mailbox Manager Settings (Policy) tab to define the action that
Manager settings the Mailbox Manager will take when processing mailboxes and folders that
contain messages that exceed policy limits. Mailbox Manager actions include
generating reports on mailboxes containing messages that exceed policy limits,
moving messages that exceed policy limits to the Deleted Items folder or the
System Cleanup folder, and deleting messages exceeding policy limits
immediately. You can use the settings on this tab to define whether Exchange
will send e-mail messages to users after their mailboxes have been processed.
You can also exclude specific message classes from deletion.
Practice: Creating and In this practice, you will read an e-mail message and an attachment from your
applying recipient team lead, Samantha Smith, and then create and apply a recipient policy.
policies
3. Read the attachment entitled rpolicydetail.doc.
! To create a recipient policy

1. In the console tree, expand Recipients.
2. Right-click Recipient Policies, point to New, and then click Recipient
Policy.
3. In the New Policy dialog box, select the Mailbox Manager Settings check
box, and then click OK.
Regular User Mailbox Management Policy and then click Modify.
5. In the Find Exchange Recipients dialog box, click OK.
6. Read the Exchange System Manager warning regarding policies that are
applied to existing users, and then click OK.
7. In the Properties dialog box, click the Mailbox Manager Settings (Policy)
tab. In the When processing a mailbox list, select Delete Immediately.
8. For the Inbox folder, click 30. In the Folder Retention Settings dialog box,
click to clear the Message Size (KB) check box. Then, in the Age Limit
(Days) box, type 1 and click OK.
9. In the Properties dialog box, on the Mailbox Manager Settings (Policy)
tab, select the Send notification mail to user after processing check box,
and then click Message.
10. Verify that the default message is appropriate, select the Insert the number
of messages processed check box, and then click OK.
11. In the Properties dialog box, click OK to create the policy.
12. In the Recipient Policies container, in the details pane, right-click Regular
User Mailbox Management Policy, and then click Apply this policy now.
You have just created a policy that cleans messages out of all user
inboxes that are only one day old. What is a more realistic
configuration of the mailbox manager settings in a recipient policy?
Answers will vary.
Lesson: Configuring Exchange Server 2003 for Proactive

Management

Introduction Proactive management is crucial to ensuring the maximum performance of your
Exchange organization. Before you fully deploy each Exchange server, you
must perform a series of configuration tasks to proactively manage your
Exchange environment.
! Create stores and storage groups.
! Explain the guidelines for creating stores and storage groups.
! Configure mailbox stores and public folder stores for preventive
maintenance.
! Configure service and resource monitoring.
! Configure notifications.
! Describe Exchange performance objects and counters.
! Configure performance monitoring by using the Performance console.
! Configure alerts by using Performance Logs and Alerts.
! Configure message tracking.
! Configure protocol logging.
Note To help you proactively manage your Exchange environment, the

Microsoft Operations Framework (MOF) provides technical guidance for
improving system reliability, availability, and manageability of Microsoft
products and technologies. MOF provides operational guidance in the form of
white papers, operations guides, assessment tools, best practices, case studies,
templates, support tools, and services. For more information about MOF, see
Course 1737, Microsoft Operations Framework Essentials.
Guidelines for Creating Stores and Storage Groups

What are stores and A store is an Exchange database that houses data such as e-mail messages and
storage groups? documents. Stores are contained in storage groups, which are collections of
mailbox stores and public folder stores. Exchange manages each storage group
with a separate server process. Exchange Server 2003 Enterprise Edition
supports five storage groups, one of which is the recovery storage group. Each
storage group has a set of transaction logs that provide detailed logging of every
message sent to and received from a store in a storage group. You can use these
logs to restore data in a recovery situation.
Note For more information about stores and storage groups, see Module 11,
“Managing Data Storage and Hardware Resources,” in Course 2400,
To create a store The high-level steps to create a store are as follows:

1. In the console tree of Exchange System Manager, locate the storage group
in which you want to create the new store.
2. Use the context menu for the storage group to create a new store.
The detailed steps to create a store are included in the practice at the end of this
topic.
To create a storage The high-level steps to create a storage group are as follows:
group
1. In the console tree of Exchange System Manager, locate the server in which
you want to create the storage group.
2. Use the context menu for the server to create a new storage group.
The detailed steps to create a storage group are included in the practice at the
end of this topic.
Guidelines for creating Follow these guiding principles when you create stores:
stores
! Create multiple small mailbox stores or public folder stores instead of
having one large store. Smaller stores allow for faster restore than large
stores, which minimizes the impact of store failures and restores on users.
! Create multiple smaller stores to maximize backup efficiency. You can
estimate the maximum time it will take to perform a backup of each store
based on the speed at which your backup hardware performs in megabytes
per hour. You can then constrain your stores to a maximum size limit, which
allows you to back up all stores in a storage group within the time that you
have allocated for backups each night.
! Create a designated mailbox store for users who require priority service
and fast restore. However, having a designated store for a single user is not
recommended because the increased administrative cost outweighs the
benefits.
! Place information that requires content indexing in a separate mailbox
store or public folder store and enable content indexing for that store. This
can minimize indexing overhead.
! Place similar users, such as users in the same department, in the same
mailbox store. Users in the same department or other groups of similar users
tend to use Reply All or send large attachments to each other. If you place
these similar users together, you maximize single-instance message storage,
which minimizes disk space requirements. This also provides you with
improved administrative control.
! Place data that requires different restore criteria in different mailbox or
public folder stores. This allows for improved administrative control over
data. For example, you may have different restore guidelines for executive
mailboxes, so those mailboxes should be in a separate store.
! Consolidate dedicated servers, such as mailbox-only, public folders-only, or
NNTP-only servers, into a single server. This will improve manageability.
Guidelines for creating Follow these guiding principles when you create storage groups:
storage groups
! Ensure that each storage group has its own dedicated drive for transaction
log files. This allows for faster server performance.
! In a hosting scenario, when possible, host multiple companies on the same
server, with each company having its own partition or drive, storage
groups, transaction log files, public folders, and so on. This allows for
improved administrative control. You should keep different companies in
separate storage groups, because this will keep all transaction logs for each
company separate from each other. Hosting companies in the same storage
group will result in all transactions for each company sharing the same set
of transaction logs, which may cause billing or legal issues for your
customers.
! Place stores requiring the same backup schedule in the same storage group
and use the storage group as a unit for backup. This allows for improved
administrative control.
Practice: Creating a new In this practice, you will create a new storage group and a new mailbox store.
storage group and a new Complete the following steps:
store
1. In Exchange System Manager, in the console tree, expand
Northwind Traders (Exchange)\Administrative Groups\
First Administrative Group\Servers, right-click London, point to New,
and then click Storage Group.
Executive SG and then click OK.
3. In the console tree, right-click Executive SG, point to New, and then click
Mailbox Store.
4. In the Properties dialog box, in the Name box, type Executive Mailbox
Store and click OK. Then, click Yes to mount the store, and click OK.
5. In the console tree, verify that the London server now contains the
Executive SG storage group and that the Executive SG storage group
contains the Executive Mailbox Store.
You just created a new storage group to contain the Executive mailbox
store. What reason do you think your team lead had for asking you to
place this new mailbox store in a new storage group, rather than in the
default storage group?
The most likely reason to create a new storage group in this
situation is if you have different backup requirements for the
executives.
How to Configure Mailbox Stores for Preventive Maintenance

Use the following tables as a guide when configuring the properties of mailbox
store objects.
The General tab Configure the items on the General tab as described in the following table.
Item How to configure it
Default public Identify a public folder store that is physically close to the server
folder store on which the mailbox store is defined. This minimizes network
traffic when clients download the public folder list from the default
public folder store each time they expand the All Public Folders
container.
Archive all Enable this option if you have a legal requirement to retain all
messages sent or messages that are handled by a mailbox store. When you enable
received by this option, you must also specify a mailbox that will store all the
mailboxes on this messages that are archived. For security purposes, this archive
store mailbox should be located on a dedicated, secure server rather than
on a mailbox server.
Note For more information about client access to public folders, see Module 5,
“Managing Public Folders,” in Course 2400, Implementing and Managing
Microsoft Exchange Server 2003.
The Database tab Configure the items on the Database tab as described in the following table.
Exchange Identify a disk on which to store the Exchange database, which

database contains the Rich Text Format (RTF) content of e-mail messages
sent by MAPI clients. Store Exchange databases on separate
physical disks from each other and from transaction log files. Move
your databases to separate drives whenever possible.
Exchange Identify a disk on which to store the Exchange streaming database,
streaming which contains Internet e-mail messages sent in Multipurpose
database Internet Mail Extensions (MIME) format. Store the Exchange
streaming databases on the same disk as the corresponding
Exchange database. If you move the Exchange database, you may
also want to move the associated Exchange streaming database.
Maintenance Identify the time when maintenance occurs. Schedule maintenance
interval to occur when most of your users are offline. This minimizes the
impact on the performance of your server. If you have multiple
storage groups on a single server, schedule maintenance for these
storage groups to occur in a staggered manner. Ideally, there should
be no overlap among the online maintenance schedules for the
storage groups.
Note For more information about disk configuration, see Module 11,
The Limits tab Configure the items on the Limits tab as described in the following table.
• Issue warning at Identify the maximum size that each mailbox will be allowed
(KB) on your hard disk and set that to be the Prohibit send and
• Prohibit send at receive at (KB) amount. This number should be based on the
(KB) maximum size of your mailbox store. It should allow you to
perform full online backups within the time that is allocated
• Prohibit send and each night. As a courtesy to your users, issue a warning before
receive at (KB) their mailboxes reach this hard limit.
Warning message Identify the time of day that Exchange will send warning
interval messages to users whose mailbox storage exceeds the limits
defined. In general, one warning per day is adequate. The
warning should occur outside of your regular business hours.
Keep deleted items Configure this item to a number that is reasonable for your
for (days) environment, because Exchange does not support individual
item recovery from backup media. Because deleted items
occupy space on your hard disk and are not included in
mailbox limits, you may want to leave this at the default seven
days. Be prepared to adjust this number according to user
needs and hardware use.
Keep deleted Configure this item to be a value that is reasonable for your
mailboxes for (days) environment, because mailbox recovery is not supported from
backup media. Because deleted mailboxes occupy space on
your hard disk, you may want to leave this at the default 30
days. Be prepared to adjust this number according to user
needs and hardware use.
Do not permanently When this option is enabled, no information will ever be lost
delete mailboxes and before it is backed up. Set this option and implement a nightly
items until the store backup schedule, except for situations in which you are not
has been backed up responsible for recovering user data.
How to Configure Public Folder Stores for Preventive Maintenance

Use the following tables as a guide when configuring the properties of public
folder store objects.
The Database tab Configure the items on the Database tab as described in the following table.
Exchange Identify a disk on which to store the Exchange database. Store

database Exchange databases on separate physical disks from each other and
from transaction log files. Move your databases to separate drives
whenever possible.
Exchange Identify a disk on which to store the Exchange streaming database.
streaming Store Exchange streaming databases on the same disk as the Exchange
database database. If you move the Exchange database, consider moving the
associated Exchange streaming database.
Maintenance Identify the time when maintenance occurs. Schedule maintenance to
interval occur when most of your users are offline. This minimizes the impact
on the performance of your server. If you have multiple storage groups
on a single server, schedule maintenance for these storage groups to
occur in a staggered manner. Ideally, there should be no overlap among
the online maintenance schedules for the storage groups.
Note For more information about disk configuration, see Module 11,
The Replication tab Configure the items on the Replication tab as described in the following table.
Replication By default, the replication interval is the span of time in which folders
interval that are scheduled to replicate will actually be replicated, or copied, to
other servers. Set this to a value that is appropriate for the type of
content in your folders and the network bandwidth available between
public folder servers. You can override this schedule for each public
folder if necessary.
Replication This determines when replication updates will be sent to other servers
interval for that maintain replicas of folders. If the interval is set to “Always,” you
always can define how often updates will be sent. The default is every 15
(minutes) minutes.
Replication By default, the replication message size limit is 300 kilobytes (KB).
message size However, if the replication messages must go through connectors that
limit (KB) have size limits, then you should set the replication message size limit
to be smaller than the connector limit.
Note For more information about setting replication intervals, see Module 5,
The Limits tab Configure the items on the Limits tab as described in the following table.
• Issue warning Identify the maximum size that each folder will be allowed on your
at (KB) hard disk and set that to be the Prohibit post at (KB) amount. This
• Prohibit post number should be based on the maximum size of your public folder
at (KB) store. As a courtesy to the folder owners, set Exchange to issue a
warning well in advance of this hard limit.
Maximum item Identify the maximum item size to prevent users from posting large
size (KB) files. For example, if most of the items that you expect to see
posted are Microsoft Word documents that occupy less than 500
KB, then set this value to be 1,000 KB.
Warning message Identify the time of day that Exchange will send warning messages
interval to folder owners whose folder storage exceeds the defined limits. In
general, one warning per day is adequate. The warning should
occur outside of your regular business hours.
Keep deleted Configure this item to be a value that is reasonable for your
items for (days) environment, because Exchange does not support individual item
recovery from backup media. Because deleted items occupy space
on your hard disk and are not included in folder storage limits, you
may want to leave this at the default 7 days. Be prepared to adjust
this number according to user needs and hardware use.
Do not You should only need to enable this option if you have just one
permanently public folder server in your organization. In general, the
delete items until availability of public stores should be managed by using
the store has been replication, not backups. If replication is configured correctly, the
backed up only time that you must back up public stores is when you want to
remove transaction log files.
How to Configure Service and Resource Monitoring

Why monitor services For Exchange to function properly, the appropriate services in Exchange and in
and resources? Windows must be running. For example, you must have a foreign connector
running to deliver messages between users on the Exchange system and users
on the foreign system. The proper functioning of Exchange also relies on the
availability of server resources such as virtual memory and free disk space. By
actively monitoring the state of the services and resources, you can minimize
potential issues and reduce system downtime. However, any monitoring that
you perform will impact performance of your servers and network. You should
balance the need for monitoring with the load that you are willing to incur on
your resources.
Exchange services Exchange automatically monitors the following services:
monitored by default
! Microsoft Exchange Information Store
! Microsoft Exchange MTA Stacks
! Microsoft Exchange Routing Engine
! Microsoft Exchange System Attendant
! SMTP
! World Wide Web Publishing Service
Guidelines for setting You should configure Exchange to monitor the performance of additional
thresholds for additional resources and services that are crucial to the proper functioning of Exchange.
resources and services You should define the threshold or critical level for a resource and configure a
that Exchange monitors notification to appear when the threshold is reached. The following table shows
these additional resources and provides guidelines for setting their respective
thresholds.
Resource Guideline for setting the threshold
Available virtual memory Set warning and critical thresholds for available virtual
memory. Virtual memory should not fall below 25
percent free on an Exchange server for any length of
time.
CPU Utilization Set warning and critical limits for CPU usage over a
sustained period. CPU usage should not exceed 80
percent over 5 minutes.
Free disk space Set warning and critical levels for available space on a
volume. Monitor the volumes used for system binaries,
Exchange Server databases, and Exchange Server
transaction logs. Configure the monitor to issue a warning
when a drive has less than 100 megabytes (MB) of disk
space remaining and to issue a critical alert when a drive
has less than 25 MB of disk space remaining.
SMTP queue growth Set thresholds for continuous queue growth. Messages
that stay in the queue for longer than five minutes may
indicate a problem with a connector.
Windows 2000 service Identify additional services in Windows that you want to
monitor. Identify whether each service being stopped is
considered to be in a warning or critical state.
X.400 queue growth Set thresholds for continuous queue growth. Messages
that stay in the queue for longer than five minutes may
indicate a problem with a connector. This queue should
be empty for any environment that only uses SMTP to
connect to other messaging systems.
To monitor additional The high-level steps to monitor the additional resources beyond the default
resources and services resources are as follows:
1. Use Exchange System Manager to locate the appropriate server.
2. Open the server’s Properties dialog box.
3. Use the Monitoring tab to add a resource or service to monitor.
The detailed steps to monitor additional resources are included in the practice
that follows.
Practice: Configuring In this practice, you will configure resource monitoring on your Exchange
resource monitoring on server. Complete the following steps:
an Exchange server
1. In Exchange System Manager, in the console tree, right-click London, and
then click Properties.
2. In the London Properties dialog box, click Monitoring.
3. On the Monitoring tab, click Add.
4. In the Add Resource dialog box, click SMTP queue growth, and then
click OK.
5. In the SMTP Queue Thresholds dialog box, select the Critical state
(minutes) check box, type 5 and then click OK.
6. In the London Properties dialog box, click OK.
7. In the console tree, expand Tools, expand Monitoring and Status, and then
click Status.
Note This step may take several minutes to complete before you can
continue.
8. In the details pane, verify that London Status is indicated as Critical: Queue
growth.
Why is the London status indicated as critical for queue growth?
There is another server in the organization named Miami. Miami is
not currently running, so all messages for Miami are queued on
London.
How would you configure Exchange to monitor for current available

disk space?
Configure a monitor on London that monitors disk space
thresholds.
How to Configure Notifications

What are notifications? You can use Exchange System Manager to direct Exchange to either send an
e-mail message or launch a script when resources that you are monitoring
perform outside of defined thresholds. These messages or scripts that notify you
when something is wrong are called notifications, and they make it possible for
you to immediately take action to restore resources to their normal state. Before
you configure notifications, you must configure your Exchange server to
monitor the resources that you are concerned about and then define the
thresholds in which your resources should perform.
For example, you might want to monitor SMTP queue growth and be notified
when the queue grows continuously for five minutes. To accomplish this,
configure server monitoring to include SMTP queue growth with a critical state
threshold of 5 minutes, and then configure a notification to alert you of the
issue.
To configure The high-level steps to configure notifications are as follows:
notifications
1. Use Exchange System Manager to open the Monitoring and Status tool.
2. Use the Notifications context menu to create a new e-mail or script
notification, identify the server that will perform the monitoring, identify the
servers and connectors to be monitored, and then specify the conditions that
will cause the notification to be sent.
3. Configure the e-mail message that will be sent, or the script that will run, as
appropriate.
The detailed steps to configure notifications are included in the practice that
follows.
Practice: Configuring In this practice, you will configure Exchange to send notifications to you.
notifications by using Complete the following steps:
Exchange System
Manager 1. In Exchange System Manager, in the console tree, expand Tools, expand
Monitoring and Status, right-click Notifications, point to New, and then
click E-mail notification.
2. In the Properties dialog box, click Select.
3. In the Select Exchange Server dialog box, in the Enter the object name to
select (examples) box, type London and then click OK.
4. In the Properties dialog box, in the To box, type LondonAdmin and then
click OK.
5. In the console tree, click Notifications. In the details pane, verify that a
notification is listed for London that indicates an action of
Mailto:LondonAdmin.
What will happen when the London Information Store service enters a
critical state?
London will attempt to send an e-mail notification to
LondonAdmin. However, because the LondonAdmin account is on
the London server, the message will not be received. Message
delivery to local recipients is dependent on the Information Store
service. Instead, you should either configure the notification to be
sent to a recipient on a different server, or you should configure a
script notification that notifies you by using a mechanism other
than e-mail.
Exchange Performance Objects and Counters

Exchange installs its own set of performance objects and counters that provide
information about Exchange services and resources. You can use counters to
monitor specific aspects of the performance of Exchange servers.
Note Guidelines for recommended thresholds are provided in Module 13,

“Performing Preventive Maintenance,” in Course 2400, Implementing and
Managing Exchange Server 2003.
Note If you monitor only Exchange performance objects and counters, you
will not have complete information about the condition of your Exchange
server. You must also monitor your Windows 2000 Server and
Windows Server 2003 for possible performance issues.
Exchange performance To ensure the performance of your Exchange server, monitor the objects in the
objects following table.
Object Description
MSExchangeIS The Exchange store object used to track the performance

of the Microsoft Exchange Information Store service
MSExchangeIS Mailbox The Exchange store object used to track the performance
of a particular mailbox store
MSExchangeIS Public The Exchange store object used to track the performance
of a particular public folder store
SMTP Server The SMTP server object used to track the performance of
SMTP on the server
MSExchangeAL The Address List object used to track the performance of
the Recipient Update Service
Counters to monitor the The following table lists the Exchange store objects and the counters that you
Exchange store objects can use to monitor these objects.
Object Counter
MSExchangeIS User Count

RPC Requests
MSExchangeIS Mailbox Send Queue Size
MSExchangeIS Public Messages Sent/min*
Receive Queue Size
Messages Delivered/min
* min is an abbreviation for minutes.

Counters to monitor the You can use the following counters to monitor the SMTP Server object:
SMTP Server object
! Local Queue Length
! Categorizer Queue Length
! Inbound Connections Current
! Message Bytes Sent/sec*
! Message Bytes Received/sec
! Avg.** Retries/msg*** Delivered
! Avg. Retries/msg Sent
* sec is an abbreviation for seconds.

** Avg. is an abbreviation for average.
*** msg is an abbreviation for message.
Counter to monitor the You use the Address Lists Queue Length counter to monitor the
MSExchangeAL object MSExchangeAL object. You can use this counter to monitor the performance of
the Recipient Update Service, which builds and maintains address lists.
Notes For more information about Recipient Update Service, search for the
article “How the Recipient Update Service populates Address Lists” on the
Product Support Services page of the Microsoft Web site at
http://support.microsoft.com/.
For information about what objects and counters in Windows you should
monitor in conjunction with Exchange objects and counters, search for
“Chapter 27 – Overview of Performance Monitoring,” which is part of the
Windows 2000 Professional Resource Kit on the TechNet page of the Microsoft
Web site at http://www.microsoft.com/technet.
How to Configure Performance Monitoring Using the Performance

Console

You use the Performance console snap-ins to monitor Exchange server
performance. The Performance console contains two snap-ins: the Performance
Logs and Alerts snap-in and the System Monitor snap-in.
Uses of Performance You use Performance Logs and Alerts to record and log system activity over a
Logs and Alerts period of time. You can then analyze the data collected in the log files to
perform trend analysis and future capacity planning. In addition, you can use
this snap-in to configure real-time alerts on object counters to provide
information on the performance of Exchange components. Real-time alerts
enable you to take appropriate actions at the first sign of a problem.
Uses of System Monitor You use System Monitor to view performance charts in real time and to display
information contained in log files. This is useful during times of performance
degradation.
Note You can also use Microsoft Operations Manager to automate the
monitoring of servers and applications. The Microsoft Operations Manager
Management Pack for Exchange includes key performance metrics to monitor
the overall performance of Exchange and to alert you to critical performance
issues. For more information about Microsoft Operations Manager and the
Management Pack for Exchange, see the Microsoft Operations Manager Web
site at http://www.microsoft.com/mom/.
To log objects and The high-level steps to log objects and counters are as follows:
counters
1. Open the Performance console.
2. Expand Performance Logs and Alerts to locate Counter Logs.
3. Use the context menu to create a new log file.
4. In the dialog box for the new log, add the performance objects and counters
and configure the logging schedule.
5. In the details pane of Counter Logs, use the context menu of the log file to
start the logging.
Logging automatically begins as soon as you create the log file or when the
start time that you specify on the schedule’s tab equals the current time. To stop
the log file manually, you can use the log file’s context menu. Detailed steps for
logging objects and counters are included in the practice that follows.
Practice: Configuring In this practice, you will read an e-mail message and an attachment from your
performance logs team lead, Samantha Smith, and then configure the Performance console to
monitor Exchange objects and counters.

3. Read the attachment entitled perfloginfo.doc.
! To configure performance logs

1. On the desktop, click Start, click Run, type perfmon and then click OK.
2. In the Performance console tree, expand Performance Logs and Alerts.
3. Right-click Counter Logs and then click New Log Settings.
4. In the New Log Settings dialog box, in the Name box, type London Stores
and then click OK.
5. In the London Stores dialog box, on the General tab, click Add Counters.
6. In the Add Counters dialog box, in the Performance object box, select the
objects and counters that you want to monitor, and in the Select counters
from list box, select a counter, and then click Add to add each counter. For
counters with multiple instances, select _Total from the instances list. The
following table shows the objects and counters to add.
Object Counter
MSExchangeIS User Count

RPC Requests
MSExchangeIS Mailbox Messages Delivered/min
MSExchangeIS Public Messages Sent/min
Receive Queue Size
Send Queue Size
Processor %Processor Time
(continued)
Object Counter
Memory Pages/sec
LogicalDisk %Free Space
Free Megabytes
7. After you have added all of these objects and counters, in the Add
Counters dialog box, click Close.
8. In the London Stores dialog box, on the General tab:
a. In the Interval box, type 1
b. In the Units box, click minutes, and then click Log Files.
9. On the Log Files tab, in the Log file type box, click Text File (Tab
delimited), and then click Configure.
10. In the Configure Log Files dialog box, click Limit of, type 5 and then click
OK.
11. In the London Stores dialog box, click Yes to create the C:\PerfLogs
folder, and then click OK.
12. In the console tree, click Counter Logs. In the details pane, verify that the
log named London Stores is green. This indicates that the log is started. If
the log is not started, right-click London Stores and then click Start.
You configured counters for Processor, Memory, and LogicalDisk. Are

there other objects or counters that you should configure for your
production environment? Why or why not?
Yes. Several counters are recommended for tracking hardware
resource usage. In addition to the few counters listed in this
practice, there are several additional counters for each object (such
as Memory\Page Faults/sec, Memory\Pages Input/sec, and
Memory\Page Reads/sec) that you should be tracking. You should
also be monitoring your network.
How to Configure Alerts Using Performance Logs and Alerts

What is an alert? An alert is a system-generated event that is triggered when counters that you
are tracking perform outside of predefined thresholds. You use Performance
Logs and Alerts to configure alerts. For example, you can configure an alert to
notify you when the MSExchangeIS Mailbox object’s Send Queue Size counter
exceeds 25 messages.
Note The alert functionality depends on the Windows 2003 Messenger

Service, the Windows 2003 Alerter Service, and the existence of the recipient
account registration in the Windows Internet Name Service (WINS). The
Messenger and Alerter services are disabled by default and must be enabled and
started to allow network messages to be transmitted.
To configure alerts The high-level steps to configure alerts in Performance Logs and Alerts are as
follows:
1. Open the Performance console, and then open Performance Logs and
Alerts.
2. Use the Alerts context menu to create a new alert.
3. Configure the new alert by adding counters, configuring thresholds,
configuring the data sampling rate, configuring the schedule during which
you want the alert to be operational, and defining actions that occur when an
alert is triggered.
The detailed steps to configure alerts by using Performance Logs and Alerts are
included in the practice that follows.
Practice: Configuring In this practice, you will use the Performance console to configure alerts.
alerts by using Complete the following steps:
Performance Logs and
Alerts 1. In Performance, in the console tree, right-click Alerts, and then click New
Alert Settings.
2. In the New Alert Settings dialog box, type London Send Queue Alert and
then click OK.
3. In the London Send Queue Alert dialog box, on the General tab, click
Add.
4. In the Add Counters dialog box, in the Performance object box, click
MSExchangeIS Mailbox, verify that Send Queue Size is selected, click
Add, and then click Close.
5. In the London Send Queue Alert dialog box, in the Limit box, type 25 and
then click the Action tab.
6. On the Action tab, select the Send a network message to check box, type
LondonAdmin in the corresponding box, and then click OK.
7. In the Performance console tree, click Alerts. Verify that the London Send
Queue Alert is green. This indicates that the alert is started.
8. Close Performance.
Why did your team lead choose 25 as the limit for the London send
queue alert?
The threshold for this value should be determined based on your
existing performance baseline and the level of service that you
provide to your employees. Using this information, the team lead
decided that there should never be more than 24 messages waiting
to be sent out from the London server and that if there was more
than that amount, there must be a problem with some component
of the messaging environment.
How to Enable Message Tracking

Why track messages? You can use message tracking to track the path of messages that are transmitted
in your Exchange organization. You can track messages sent to or from users
defined in your organization and to or from connectors, such as the SMTP
connector. By tracking messages, you can troubleshoot message delivery
problems. For example, you can use message tracking to trace a message that is
sent from an Exchange user to determine at what point the message failed to
transfer.
To enable message By default, message tracking is turned off. In addition to verifying that the
tracking Exchange Management Service is started, you can enable message tracking by:
! Creating a system policy to enable message tracking and applying the policy
to the servers for which you want to track messages.
! Editing the properties of each server for which you want to track messages.
What are message When you enable message tracking on a server running Exchange,
tracking logs? Exchange creates a set of logs in a shared folder named servername.log (where
servername is the name of the Exchange server on which you enabled message
tracking). A new message tracking log file is created each day. Information
about messages that are handled by the server that day is recorded in the
corresponding log file.
You can configure message tracking to record information about the sender, the
message, the recipient, and the subject line of the message. By default,
Exchange does not display message subjects in message logs. If you want
message subjects to be visible during message tracking on both the SMTP and
MAPI queues, you can enable subject logging. You may need this information
if you want to trace a message back to its source to troubleshoot delivery
problems.
Note To track messages, administrators have permission to view the log files.
If you have enabled subject logging, administrators will be able to read the
message subjects. This may be a security consideration in your environment.
To redirect message By default, message tracking logs are stored on the Exchange installation drive.
tracking log storage The size and number of these logs can increase considerably over time. You
may want to change the location of the message tracking logs to accommodate
the size requirements. To move message tracking logs:
1. Open Exchange System Manager and locate the Exchange server that has
the message logs that you want to move.
2. On that server, open the Properties dialog box and then use the General tab
to select the directory in which you want to store the message tracking logs.
Practice: Configuring In this practice, you will read an e-mail message and an attachment from your
message tracking team lead, Samantha Smith, and then create and apply a policy that enables
message tracking on your server.
Important To complete this practice, a System Policies container must exist in

your organization. If no System Policies container exists, create one by
completing the Creating a System Policies container practice in the lesson
“Creating and Applying Exchange Policies” in Module 2, “Configuring and
Managing Exchange Server 2003,” in Course 2400, Implementing and
Managing Microsoft Exchange Server 2003.

3. Read the attachment entitled policydetail.doc.
! To create a server policy that enables message tracking

1. In Exchange System Manager, in the console tree, right-click System
Policies, point to New, and then click Server policy.
2. In the New Policy dialog box, select the General check box, and then click
OK.
3. In the Properties dialog box, on the General tab, type Message Tracking
Policy and then click the General (Policy) tab.
4. On the General (Policy) tab, select the Enable message tracking check
box, and then select the Remove log files check box.
5. In the Remove files older than (days) box, type 7 and then click OK.
6. In the details pane for System Policies, right-click Message Tracking
Policy, and then click Add Server.
box, in the Enter the object names to select (examples) box, type London
and then click OK.
9. In the console tree, browse to Administrative Groups\First Administrative

Group\Servers\London\, right-click London, and then click Properties.
10. In the LONDON Properties dialog box, click Policies.
11. On the Policies tab, verify that the message tracking policy is applied to the
server, and then click OK.
You would like to create a policy that configures all servers to monitor
all Exchange services. How can you accomplish this?
You cannot do this. The only configuration that a server policy can
control is message tracking.
How to Configure Protocol Logging

What is protocol Protocol logging is a feature that provides detailed information about the
logging? commands received by supported Internet protocols. When protocol logging is
enabled, all commands that are sent between the client and the server are logged
to the protocol log file. The information that is logged includes client IP
address, client domain name, date and time of message, number of bytes sent,
and the actual commands and responses exchanged between the client and the
server. You can use the log file to troubleshoot protocol or connection errors.
Protocols supported by The following table describes the protocols supported by Exchange
Exchange Server 2003 Server 2003.
Protocol Description
HTTP Exchange supports Hypertext Transfer Protocol (HTTP) to provide

Outlook Web Access client access to Exchange public folders, mailbox
contents, and directory information.
POP3 Internet messaging clients use Post Office Protocol version 3 (POP3) to
retrieve messages from a server. With POP3, messages are stored on the
server until a client requests them. POP3 is a retrieve-only protocol; POP3
clients use SMTP to send messages.
IMAP4 Internet messaging clients use Internet Message Access Protocol version 4,
revision 1 (IMAP4) to retrieve messages from a server. IMAP4 is an
advanced protocol that enables users to access public and private folders,
search a mailbox, and store flags on a message to indicate that the message
was read. As with POP3, IMAP4 is a retrieve-only protocol; clients use
SMTP to send messages.
(continued)
Protocol Description
ESMTP/ Extended Simple Mail Transfer Protocol (ESMTP) is an extension of the

SMTP default SMTP that is used to send messages across the Internet. Exchange
supports both SMTP and ESMTP.
NNTP Network News Transfer Protocol (NNTP) is used by news clients to read
and post messages to newsgroups. Exchange uses NNTP to gain access to
newsgroups and to allow users to connect to public folders by using news
clients.
To configure protocol You can use a virtual server to host different protocols on the same physical
logging for virtual server. During installation, Exchange creates a default virtual server for each
servers supported protocol. Each virtual server has a unique network name and IP
address. Clients connect to a virtual server the same way that they would
connect to a physical server. To configure protocol logging for SMTP and
NNTP virtual servers:
1. In Exchange System Manager, select the appropriate virtual server from the
Protocols container of the server.
2. Open the Properties dialog box on the virtual server.
3. Use the General tab to enable logging.
4. Set the protocol logging level, log format, logging frequency, and other log
file information.
Note To enable HTTP logging, open Internet Information Services (IIS)

Manager, expand Web Sites, and access the properties of the Default Web Site
container. Use the Web Site tab to enable HTTP logging.
Note You can also enable diagnostic logging for POP3 and IMAP4. For more
information, search for “Chapter 4 – Enterprise Monitoring,” which is part of
the Exchange 2000 Server Operations Guide on the TechNet page of the
Microsoft Web site at http://www.microsoft.com/technet/.
Practice: Configuring In this practice, you will configure SMTP logging on your server. To do this,
SMTP logging complete the following steps:
1. In Exchange System Manager, in the console tree, expand LONDON,
expand Protocols, and then click SMTP.
2. In the console tree, right-click Default SMTP Virtual Server, and then
click Properties.
3. In the Default SMTP Virtual Server Properties dialog box, on the
General tab, select the Enable logging check box.
4. In the Active log format box, select Microsoft IIS Log File Format from
the list, and then click OK.
5. On the desktop, click Start, click Run, type cmd and then click OK.
6. At the command prompt, type telnet London 25 and then press ENTER.
7. In Telnet London, type helo and then press ENTER
8. In Telnet London, type quit and then press ENTER.
9. In Windows Explorer, use Notepad to open the SMTP log file located at
C:\windows\system32\logfiles\smtpsvc1. Verify that the log file is
generated and that the helo and quit commands that you sent to the SMTP
virtual server were logged.
10. Close Microsoft Notepad, close Windows Explorer, and then close the
command prompt window.
At the command prompt, you typed the number 25 in the telnet

command. Why did you have to do that?
The SMTP virtual server listens to port 25 by default. To connect
to the SMTP virtual server and send SMTP commands, you must
connect to port 25.
Lesson: Adding, Removing, and Updating Exchange

Servers

Introduction Managing your Exchange organization includes periodically adding and
removing servers to meet the needs of your organization. You can add
additional physical servers or configure virtual servers to host multiple
protocols on one server. Occasionally, you may also need to remove servers to
consolidate data or enhance performance. In addition, promptly applying the
latest software updates is critical in maintaining the proper functioning of your
Exchange organization.
! Add virtual servers.
! Remove servers from an existing environment.
! Remove the first Exchange sever in a routing group.
! Apply product updates.
How to Add Virtual Servers

Why implement multiple If you require different configurations for the same protocol on a single server
virtual servers for a running Exchange, you can configure multiple virtual servers for that protocol.
single protocol? Reasons for creating multiple virtual servers for a protocol include:
! To supply different encryption methods for local and remote clients. For
example, remote users sending messages over the Internet may want all
messages encrypted for additional security, while users on the internal
intranet do not require encryption.
! To segregate traffic for the same protocol over different ports. For example,
if you have a custom application that uses POP3 to access data in Exchange
Server 2003, this application can use a unique Transmission Control
Protocol (TCP) port associated with POP3 through an Exchange
Server 2003 POP3 virtual server. This port can then be granted special
access or priority over your intranet network.
Note To create multiple virtual servers for a specific protocol, you must
uniquely identify each virtual server. To do this, you must specify a unique
TCP port and address combination for each server running that protocol.
Protocols and their The following table shows the default and secure TCP ports that are associated
associated TCP ports with the protocols supported in Exchange Server 2003.
Protocol Default port Secure port
POP3 110 995

IMAP4 143 993
HTTP 80 443
NNTP 119 563
SMTP 25 25
To create an additional The high-level steps for creating an additional virtual server are as follows:
virtual server
1. Use Exchange System Manager to locate the physical server on which you
want to add an additional virtual server.
2. Open the protocol that the new virtual server will provide.
3. Use the context menu of the protocol to create the new virtual server.
4. Configure the default settings for the virtual server by using the wizard.
The detailed steps are included in the practice that follows.

Practice: Adding an In this practice, you will read an e-mail message and attachment from your
SMTP virtual server team lead, Samantha Smith, and then add an SMTP virtual server.

3. Read the attachment entitled smtpvs.doc.
! To add an SMTP virtual server

1. In Exchange System Manager, in the console tree, browse to
Administrative Groups\First Administrative Group\Servers\London\
Protocols\SMTP, right-click SMTP, point to New, and then click SMTP
Virtual Server.
2. On the Welcome to the New SMTP Virtual Server Wizard page, in the
Name box, type Secure to Contoso and then click Next.
3. On the Select IP Address page, click Finish, and then click Yes to
acknowledge the warning.
4. In the console tree, right-click Secure to Contoso, and then click
Properties.
5. In the Secure to Contoso Properties dialog box, on the General tab, click
Advanced. In the Advanced dialog box, click Edit.
6. In the Identification dialog box, in the TCP port box, type 2400 and then
click OK.
7. In the Advanced dialog box, click OK.
8. In the Secure to Contoso Properties dialog box, click the Access tab.
9. On the Access tab, click Certificate.
10. On the Welcome to the Web Server Certificate Wizard page, click Next.
11. On the Server Certificate page, click Next.
12. On the Delayed or Immediate Request page, click Send the request
immediately to an online certification authority, and then click Next.
Note You must be a member of the Enterprise Admins group to auto-enroll

for a certificate.
13. On the Name and Security Settings page, click Next.

14. On the Organization Information page:

a. In the Organization box, type Northwind Traders
b. In the Organizational unit box, type Messaging and then click Next.
15. On the Your Site’s Common Name page, type London.nwtraders.msft
and then click Next.
16. On the Geographical Information page:
a. In the Country/Region box, click GB (United Kingdom).
b. In the State/province box, type England
c. In the City/locality box, type London and then click Next.
17. On the Choose a Certification Authority page, click Next.
18. On the Certificate Request Submission page, click Next.
19. On the Completing the Web Server Certificate Wizard page, click
Finish.
20. On the Access tab, click Connection.
21. In the Connection dialog box, click Only the list below, and then click
Add.
22. In the Computer dialog box, click Domain, read the message, click OK,
type contoso.msft and then click OK.
23. In the Connection dialog box, click OK.
24. In the Secure to Contoso Properties dialog box, click OK.
What configuration must Contoso perform to communicate with you

securely on this virtual server?
Contoso will need to specify that Port 2400 is the default port that
is used to transmit SMTP messages to Northwind Traders. You
should work with the firewall administrator in your environment
whenever you require port configuration changes to support your
Exchange environment.
How to Remove Servers

To consolidate server functionality or perform maintenance, you will
occasionally need to remove a server from your environment.
To remove a server To remove a server, you can either use Exchange System Manager or run Setup.
When you run Setup, you can remove the object and the software from the
server. When you use Exchange System Manager, you can only remove the
object, and the software remains on the physical server. In either case, you must
use a three-step process:
1. Move the public folders and system folders (for example, the Offline
Address Book folder, Schedule+ Free and Busy folder, and other folders) to
another server in the routing group.
2. Move the mailboxes to another server in the routing group.
3. Delete the server from Active Directory.
To move this Do this
To move public folders 1. Use Exchange System Manager to replicate the folders
and system folders to to the new server.
another Exchange server 2. After replication is complete, confirm that the replica
in the routing group folders are synchronized with the source folders.
To move all mailboxes • Use either Exchange System Manager or Exchange Task
to another server Wizard in Active Directory Users and Computers.
To remove the server • Run the Exchange Setup program to uninstall the server
from Active Directory and remove it from Active Directory.
Note For more information about public folder replication, see Module 5,
How to Remove the First Exchange Server in a Routing Group

The first Exchange server installed in a routing group performs certain
important roles. By default, other servers in the routing group rely on this first
server for information. The first server is responsible for the routing group
folders, which include the Offline Address Book folder, Schedule+ Free and
Busy folder, and other system folders. If you remove the first Exchange server
in a routing group without first relocating these system folders, your users will
no longer be able to use the offline address book and see each other’s free and
busy time in the calendar.
To remove the first Perform the following steps:
Exchange server in a
routing group 1. Relocate all public folders, including system folders, to another Exchange
server in the same routing group.
2. Relocate the Recipient Update Service to another Exchange server in the
domain.
3. If this server is the routing group master, which is the server that manages
link state in a routing group, designate another server to be the routing
group master.
4. If you have an Exchange 5.5 server, and if the Exchange 2003 server that
you are removing is running the Site Replication Service (SRS), you must
create a new SRS in Exchange System Manager. SRS is used to synchronize
the Exchange 5.5 directory with Active Directory.
5. If the Exchange server has any connectors hosted on it, move these
connectors to another server before you remove this server from the site.
6. Insert the Exchange Server 2003 Server CD-ROM in the computer, and then
remove all components.
Notes For more information about SRS, search for “Chapter 6, Deployment
Strategies” which is part of the Microsoft Exchange Server 2000 Resource Kit
on the TechNet page of the Microsoft Web site at
http://www.microsoft.com/technet/.
For more information about routing groups, see Module 9, “Managing
Routing,” in Course 2400, Implementing and Managing Microsoft Exchange
Server 2003.
Best Practices for Applying Product Updates

Why apply updates? Product updates are your first line of defense against the latest security threats.
In addition to mitigating security threats, if you update Exchange, you help
ensure that any performance enhancements that are available are applied to your
server.
Types of updates Microsoft releases Exchange updates in two forms:
! Hotfixes. These are single cumulative packages composed of one or more
files used to address a defect in a product. They address a specific customer
situation and may not be distributed outside the customer organization
without written legal consent from Microsoft. Because Microsoft releases
hotfixes to address a single urgent issue, they do not go through the same
rigorous testing as other software.
! Service packs. These are broadly released fixes for a specific product, and
they address a security vulnerability. They may include hotfixes, updates,
system administration tools, drivers, and other additional components.
Service packs are tested more thoroughly than hotfixes and are, therefore,
distributed less frequently. Service packs are cumulative, which means that
issues that are fixed in one service pack are also fixed in subsequent service
packs.
Where to find updates You can download Exchange updates from the Exchange Server page of the
Microsoft Web site at http://www.microsoft.com/exchange/downloads and from
the Microsoft Product Support Services page at http://support.microsoft.com.
Best practices for Follow these best practices when applying a hotfix or service pack:
applying product
updates ! Use a change control process to manage the process from start to finish.
! Read all related documentation before applying any update.
! Apply updates only on an as-needed basis.
! Test the updates on a representative test environment before deploying the
update.
! Install the update in such a way that it can be uninstalled when necessary.
! Maintain consistency across all domain controllers whenever possible.
! Have a working backup and schedule production downtime.
! Create a backout plan that allows the system to return to its original state.
! Forewarn Help Desk and key user groups before you apply a hotfix or
service pack.
! Schedule periodic updates to avoid being more than two service packs
behind.
! Deploy updates on non-critical servers first and then move to primary
servers.
Note For more information about the best practices for applying product
updates, search for “Best Practices for Applying Service Packs, Hotfixes and
Security Patches” on the TechNet page of the Microsoft Web site at
http://www.microsoft.com/technet/.
Practice: Applying a In this practice, you will search www.microsoft.com\exchange for current
hotfix product updates and hotfixes.
! To search for product updates and hotfixes

1. On your host computer, from the desktop, click Start, click Run, type
http://www.microsoft.com/exchange and then click OK.
2. Explore the Exchange product home page.
Are any service packs or hotfixes recommended for Exchange 2003?
At the time this course was released, no service packs or hotfixes
were recommended.
3. Close Internet Explorer.
! 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 check box is selected, and
then click OK.
3. Restart 2400_London-Virtual PC.
Lesson: Managing Exchange Server 2003 in a Mixed

Environment

Introduction Exchange Server 2003 is designed to coexist with Exchange 2000. Depending
on the tasks that you need to perform, you may use different tools to manage
this mixed environment.
! Describe the Exchange 2000 components that are not supported in
Exchange Server 2003.
! Describe the tools for managing Exchange Server 2003 in a mixed
environment.
Exchange 2000 Components Not Supported in


Several components that were previously included with Exchange 2000 Server
are no longer supported in Exchange Server 2003. These components include:
! Instant Messaging
! Key Management Service
! Microsoft Exchange 2000 Chat Service
! MSMail Connector
! cc:Mail Connector
If one or more of these components is installed on a computer running

Exchange 2000 Server in your organization, you must remove the component
before upgrading to Exchange Server 2003. If you want to retain Instant
Messaging or Key Management Service in your organization, consider moving
the Instant Messaging or Key Management services to components that are
supported by Exchange Server 2003, as listed in the following note. If you want
to retain the Exchange Chat Service functionality, do not upgrade the
Exchange 2000 servers that are running Exchange Chat Service. Instead, install
Exchange Server 2003 on other servers in your organization.
Note Instant Messaging is supported in Real-Time Communications

Server 2003. User certificates, digital signatures, and encryption are supported
by Windows Server 2003 and Certificate Server.
Tools for Managing Exchange Server 2003 in a Mixed Environment

Exchange Server 2003 In general, use Exchange Server 2003 tools to manage your organization
tools and their whenever possible. You cannot use Exchange Server 2003 tools to manage any
limitations Exchange 2000 components that are not supported in Exchange Server 2003.
For example, you cannot use Exchange Server 2003 tools to manage
Exchange 2000 Instant Messaging, Exchange Chat Services, event services, or
Key Management Service. However, Exchange System Manager in
Exchange Server 2003 can be used to manage any other Exchange 2000
component.
You must manage certain Exchange Server 2003 features by using
Exchange Server 2003 tools. For example, you can create and manage query-
based distribution groups in Active Directory Users and Computers; however,
you must have the Exchange System Manager in Exchange Server 2003
installed on the computer on which you administer the query-based distribution
groups.
Note For more information about query-based distribution groups, see

Module 4, “Managing Recipients,” in Course 2400, Implementing and
Managing Microsoft Exchange Server 2003.
Exchange 2000 tools If you use Exchange 2000 tools to manage Exchange in a mixed environment,
and their limitations you are limited to the feature set that Exchange 2000 offered. For example, you
will not be able to use the enhanced Exchange System Manager features,
including moving and deleting mailboxes, viewing the content of public folders,
searching public folders, and using the Mailbox Recovery Center. To use these
features, you must use Exchange System Manager in Exchange Server 2003.
Discussion: Configuring and Managing


Instructions Read the following four scenarios and discuss possible solutions with the class.
Scenario 1 You have one server running Exchange Server 2003 installed with default
settings and your company has no plans for future growth. You are preparing to
configure your mailbox store. You want to control how much space user
mailboxes can occupy in the mailbox store. What is the best way to configure
this?
Because you only have one server, and your company is not expecting to
grow, and because the default installation is a single mailbox store, there is
nothing gained by using a policy. Policies are most useful when you have
more than one mailbox store, public folder store, or server in your
organization, and you need to be able to configure several of the same type
of objects with the same settings. You may want to use policies in
environments with a single server and single store if you expect to be
adding servers or stores at a later date.
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
Scenario 2 You are a messaging administrator. You want to be notified when there are
problems with your Exchange server. You want to be able to predict when you
might have problems with your Exchange server. And you want to be able to
find out all the servers that have processed any given message. What should
you do?
Configure service and resource monitoring and notifications by using
Exchange System Manager, configure message tracking by using Exchange
System Manager, and configure protocol logging by using Exchange
System Manager. You configure service and resource monitoring and
notifications by using Exchange System Manager so that you can be
notified when Exchange services enter warning or critical states. You
should also configure message tracking on all server objects to maximize
your ability to locate messages that failed to transfer. Configure protocol
logging so that information processed by SMTP, NNTP, POP3 and/or
IMAP4 is logged. To predict when your server might have problems, you
should configure performance monitoring and alerts by using Performance
Console, and you should review the log files regularly. Exchange System
Manager does not allow you to configure performance monitoring and
alerts.
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
Scenario 3 You want to configure your Exchange server to transmit SMTP data over the
Internet securely to your branch offices. However, you want to continue to be
able to receive standard SMTP messages from unknown senders on the Internet.
What should you do?
Create a secondary SMTP virtual server. Configure this virtual server to
encrypt data sent outbound, and require incoming messages to be
encrypted. Use the connection control dialog box to identify the hosts at
your branch offices that you want to communicate securely with. If you
require different configurations for the same protocol on a single server
running Exchange, you can configure multiple virtual servers for that
protocol. Consider creating multiple virtual servers for a protocol when
you need to supply different encryption methods for different groups of
users or if you want to segregate traffic for the same protocol over different
ports. You can further control the way SMTP messages are handled by
using SMTP connectors.
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
Scenario 4 You are the messaging administrator for a company that uses Exchange 2000.
Security is of the utmost concern for you. Currently, you have Key
Management Service deployed to allow messaging users to digitally sign and
encrypt messages. You believe that this is a crucial service for your users. You
are considering upgrading to Exchange Server 2003. Given your understanding
of the features of Exchange Server 2003, how should you proceed with the
upgrade?
Because Exchange Server 2003 does not support Key Management Service,
and Key Management Service provides a critical service to your users, you
should only upgrade the Exchange 2000 servers that are not providing the
Key Management Service to your users until you are able to implement a
public key infrastructure (PKI). Also, because you cannot use Exchange
System Manager in Exchange Server 2003 to manage the Key Management
Service, you must continue to use the Exchange 2000 version of Exchange
System Manager to manage the Key Management Service.
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
THIS PAGE INTENTIONALLY LEFT BLANK

0989702

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

0989702

Загружено:

Авторское право:

Доступные форматы

Module 2: Configuring

 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: Creating and Applying Exchange Policies

Lesson: Configuring Exchange Server 2003 for Proactive

Lesson: Adding, Removing, and Updating Exchange Servers

Lesson: Managing Exchange Server 2003 in a Mixed Environment

Discussion: Configuring and Managing Exchange Server 2003

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

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

Lesson: Creating and Applying Exchange Policies

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

What Is an Exchange Policy?

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

Note Recipients are mail-enabled or mailbox-enabled Active Directory objects

Types of Exchange Policies

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

When to Use Exchange Policies

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

Requirements for Creating and Applying Exchange System Policies

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

! To prepare for this practice

! To create a system policies container

What is the impact of not creating a System Policies container?

How to Create and Apply System Policies

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

! To prepare for this practice

! To create and apply a public folder store policy

! To create and apply a mailbox store policy

You set the storage limit to issue a warning at 10 KB. Is this a

How to Remove and Override System Policies

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

Recipient Policy Priorities and Search Criteria

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

How to Create and Configure Recipient Policies

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

%g Given Name (First Name)

Although recipient policies can add additional e-mail addresses to user

! To create a recipient policy

Lesson: Configuring Exchange Server 2003 for Proactive

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

Note To help you proactively manage your Exchange environment, the

Guidelines for Creating Stores and Storage Groups

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

To create a store The high-level steps to create a store are as follows:

How to Configure Mailbox Stores for Preventive Maintenance

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

Exchange Identify a disk on which to store the Exchange database, which

How to Configure Public Folder Stores for Preventive Maintenance

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

Exchange Identify a disk on which to store the Exchange database. Store

How to Configure Service and Resource Monitoring

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

How would you configure Exchange to monitor for current available

How to Configure Notifications

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

Exchange Performance Objects and Counters

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

Note Guidelines for recommended thresholds are provided in Module 13,

MSExchangeIS The Exchange store object used to track the performance

MSExchangeIS User Count

* min is an abbreviation for minutes.

*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**