Microsoft Exchange 2000 Server Service Pack 2 Deployment Guide

Microsoft Exchange 2000 Server
Service Pack 2 Deployment Guide
Version 1.5
Published: February 2002

Table of Contents
Table of Contents ................................................................................................. 1
Introduction......................................................................................................... 2
Build Information.................................................................................................. 3
Preparing for Exchange 2000 SP2 ........................................................................... 3

Release Notes................................................................................................... 3
Microsoft Knowledge Base Articles ....................................................................... 3
Windows 2000 Prerequisites ............................................................................... 3
Installing Multiple Service Packs .......................................................................... 4
Installing Exchange 2000 SP2 ............................................................................. 4
Exchange 2000 SP2 Co-Existence ........................................................................ 4
Active Directory Connector Custom Local.map and Remote.map Files ....................... 4
Active Directory Schema Updates ........................................................................ 5
Forest and Domain Preparation ........................................................................... 5
Anti-Virus Software ........................................................................................... 5
Exchange 2000 SP2 Installation Considerations ..................................................... 5
Exchange 2000 Conferencing Server SP2 Installation ............................................. 5
Servers with Hotfixes......................................................................................... 6
Manual Registry Changes ................................................................................... 6
Disable Notifications .......................................................................................... 6
Slipstream Support ........................................................................................... 6
Unattended Installation...................................................................................... 6
Updating Through Terminal Services .................................................................... 7
Minimizing Downtime......................................................................................... 7
SP2 and Front-End Servers................................................................................. 8
SP2 Update Process Stops Non-Critical Services .................................................... 9
Removing Service Pack 2 ................................................................................... 9
Active Directory Connector SP2 Update Permissions ............................................... 9
Exchange 2000 SP2 Update Permissions............................................................. 10
Exchange System Management Tools SP2 Update Permissions............................... 10
Exchange 2000 Conferencing Server SP2 Update Permissions ................................ 10
Manual Changes Made to ASP Files in Conferencing Server.................................... 10
Applying Exchange 2000 SP2................................................................................ 11

Updating the Active Directory Connector Service ................................................. 11
Updating Exchange 2000 Server........................................................................ 11
Updating an Exchange 2000 Cluster................................................................... 11
Updating Exchange 2000 Conferencing Server..................................................... 12
Verifying That the Upgrade was Successful ............................................................. 12
Troubleshooting SP2 Upgrade Problems ................................................................. 13

Troubleshooting Exchange 2000 SP2.................................................................. 13
Troubleshooting Exchange 2000 Conferencing Server SP2..................................... 13
Clustering Scenarios ........................................................................................... 15
Overview of New Features and Enhancements in Exchange 2000 SP2 ......................... 16

Directory Enhancements .................................................................................. 16
Transport Enhancements.................................................................................. 16
Exchange Information Store and Extensible Storage Engine (ESE) Enhancements..... 16
Content Indexing Enhancements ....................................................................... 16
Administration Enhancements ........................................................................... 16
Troubleshooting Enhancements ......................................................................... 17
Migration Enhancements .................................................................................. 17
Setup Enhancement ........................................................................................ 17
Outlook Web Access Enhancements ................................................................... 17
In-Depth Guide to New Features and Enhancements in Exchange 2000 SP2 ................ 19
Directory ....................................................................................................... 19
Transport....................................................................................................... 23
Store and ESE ................................................................................................ 25
Content Indexing ............................................................................................ 25
Administration ................................................................................................ 25
Troubleshooting .............................................................................................. 30
Migration ....................................................................................................... 30
SETUP ........................................................................................................... 31
Outlook Web Access ........................................................................................ 31
Additional Resources ........................................................................................... 37

Web Sites ...................................................................................................... 37
White Paper ................................................................................................... 37
Microsoft Knowledge Base Articles ..................................................................... 37
Microsoft Exchange 2000 Server
Service Pack 2 Deployment Guide
Technical Paper
Published: February 2002
For the latest information, please see http://www.microsoft.com/exchange
Introduction
This technical paper presents the best practices for deploying Microsoft®
Exchange 2000 Service Pack 2 (SP2). The aim of this paper is to provide
Exchange deployment experts with in-depth technical information about the
changes introduced with SP2 and real world tips and tricks for deployment. The
following teams contributed to the production of this paper:
• Microsoft Exchange Server Development Team
• Microsoft Exchange Joint Development Program (JDP) management team
• Microsoft Exchange Beta Technology Support (BTS)
• Microsoft Exchange User Experience (UE)
Note This paper is intended for advanced-level Exchange 2000

administrators. It is recommended that you have a good understanding
of large and complex Exchange 2000 environments before reading this
paper.
Exchange 2000 SP2 contains fixes for issues reported since the initial release of
Exchange 2000. The majority of these issues address the overall quality of the
product, while others address critical problems found in the original code. SP2
resolves these issues, thereby increasing the performance, stability, availability,
and functionality of servers running Exchange 2000. In addition, SP2 contains
some new features, including:
• Enhanced Microsoft Outlook® Web Access
• Re-architected DSAccess component
• Enhanced Message Tracking Center
• Enhanced Mailbox Manager support
• Enhancements to the Exchange System Manager console, including two new

Microsoft Windows® Management Instrumentation (WMI) providers
Build Information
Each version of Exchange Server includes a build number so that you can easily
identify which version of the product you are running:
• Exchange 2000 = 4417.5
• Exchange 2000 Service Pack 1 = 4712.7
• Exchange 2000 Service Pack 2 = 5762.4
Preparing for Exchange 2000 SP2

It is imperative that you prepare for and test Exchange 2000 SP2 before
deployment. Lack of planning can result in long periods of user downtime. In
addition to following the planning tips in this section, you should also thoroughly
test SP2 in your laboratory environment before deploying it on production
servers. In particular, you should familiarize yourself with the new Outlook Web
Access functionality and understand its impact on users.
Release Notes
Before you upgrade your servers to SP2, read the Exchange 2000 SP2 release
notes. Because the release notes are finalized a few weeks before a service pack
is released, view the release note updates on the Microsoft Exchange Web site at
http://www.microsoft.com/exchange.
Microsoft Knowledge Base Articles
For a list of articles associated with Exchange 2000 SP2, see Microsoft Knowledge
Base article Q311456, “XGEN: List of Bugs Fixed by Exchange 2000 Server
Service Packs.”
Windows 2000 Prerequisites
You can only install Exchange 2000 SP2 on existing Exchange 2000 servers that
are running Windows® 2000 SP2. To download Windows 2000 SP2, see the
Windows 2000 Web site at http://www.microsoft.com/windows2000. You should
also install the critical post-SP2 hot fixes for Windows 2000.
Although not absolutely necessary, you should also install Windows 2000 SP2 on
computers running the Microsoft Active Directory® Connector service (ADC),
Microsoft Exchange 2000 Conferencing Server, and all domain controller and
global catalog servers.
Note There is a compatibility issue between Windows 2000 SP2 and

Microsoft Winsock Proxy Client version 2.0. After you apply
Windows 2000 SP2 to an Exchange 2000 server running Winsock Proxy
Client 2.0, all Exchange services will fail to start. To correct this problem,
perform one of the following tasks:
• Contact Microsoft Product Support Services (PSS) for a fix.
Microsoft Exchange 2000 Server Service Pack 2 Deployment Guide 3

• Remove Winsock Proxy Client.
• Upgrade to ISA Client.
For more information about this issue, see Microsoft Knowledge Base article
Q300517, “Exchange 2000 Services Do Not Start After Windows 2000 SP2
Upgrade.”
Installing Multiple Service Packs
You can install Windows and Exchange service packs in any order. For example, if
you install a Windows 2000 service pack after installing Exchange 2000 SP2, you
do not need to re-install Exchange 2000 SP2.
If you previously ran Exchange 2000 on Windows 2000 SP1 and then upgraded to
Windows 2000 SP2, you might be presented with file copy options when installing
Exchange 2000 SP2. If this occurs, a prompt appears indicating that the target
file already exists and is newer than the source. If you receive these errors,
click No to all.
Installing Exchange 2000 SP2
Exchange 2000 SP2 is designed as an upgrade. You can install it on any server
running:
• Exchange 2000.
• Exchange 2000 SP1.
You do not need to upgrade a server running Exchange 2000 to SP1 before
upgrading to SP2. You may also install Exchange 2000 SP2 on servers running
post Exchange 2000 and Exchange 2000 SP1 hotfixes.
Exchange 2000 SP2 Co-Existence
Servers running Exchange 2000 SP2 can fully co-exist with servers running
Exchange 5.5, Exchange 2000, and Exchange 2000 SP1. However, you cannot
use an Exchange 2000 or Exchange 2000 SP1 front-end server to access an
Exchange 2000 SP2 back-end server. As a best practice, always upgrade front-
end servers to Exchange 2000 SP2 before upgrading back-end servers.
Active Directory Connector Custom Local.map and Remote.map

Files
If you deployed the Active Directory Connector service (ADC) with custom
versions of Local.map and Remote.map files, you must make the same
customizations to the SP2 version of the ADC service before you upgrade.
As a safeguard, use a tool such as LDP to export the contents of the

msExchServer1SchemaMap and msExchServer2SchemaMap attributes
before you upgrade the ADC service. If you require help with this process please
contact Product Support Services (PSS).

Active Directory Schema Updates
Exchange 2000 SP2 does not include or require updates to the Microsoft Active
Directory® directory service schema. However, if you want to take full advantage
of the new segmentation support in Outlook Web Access, you can import the
Active Directory schema update file found in the \Support\OWAschema folder.
Outlook Web Access segmentation is a new feature in Exchange 2000 SP2. You
can use Outlook Web Access segmentation to hide folders and functionality from
users (for example, you can hide the Contacts folder) or to force all browsers to
use the HTML 3.2/HTTP rendered client. By upgrading your back-end server to
Exchange 2000 SP2, you can set the segmentation level on a per-server basis
(registry entry). However, by importing the optional Active Directory schema
update file, you can set segmentation on a per-user basis (new attribute on the
user object).
Forest and Domain Preparation
When installing Exchange 2000 SP2, it is not necessary to run /ForestPrep or

/DomainPrep again.
Anti-Virus Software
Exchange 2000 SP2 contains the same virus scanning API as Exchange 2000 SP1.
Exchange 2000 SP2 Installation Considerations
In general, you can update your servers running Exchange 2000 to SP2 in any
order. However, it is important to observe the following rules and best practices:
• Update front-end servers to SP2 before updating back-end servers. If you do

not update the front-end servers first, the back-end servers will experience
problems, and users will receive error messages.
• As a best practice, update servers running the Active Directory Connector

service before updating servers running Exchange 2000.
• As a best practice, update messaging bridgehead servers (at both ends of a

connector) at the same time.
• Remember to update servers and workstations that only have the System
Management Tools components installed. If you do not update these servers
and workstations, you will lose the new management functionality.
Exchange 2000 Conferencing Server SP2 Installation
As a best practice, you should upgrade all servers running Microsoft

Exchange 2000 Conferencing Server to SP2 at the same time. If this is not
possible in your Exchange 2000 environment, you should consider simultaneously
upgrading all servers running Exchange 2000 Conferencing Server that reside in
the same Active Directory site.

Servers with Hotfixes
You can upgrade any server running Exchange 2000 to SP2. If your existing
servers have Exchange 2000 hotfixes, you do not need to uninstall the hotfixes
before applying SP2. Hot-fixed files are over-written by the SP2 upgrade process.
Some post-SP1 hotfixes are not included with Exchange 2000 SP2. If you are
running “special” post-SP1 hotfixes (that is, hotfixes not available from the
Microsoft Product Support services Web site at http://support.microsoft.com/), you
should contact Microsoft Product Support Services (PSS). PSS can confirm
whether your post-SP1 hotfix is included with SP2, or they can supply you with a
post-SP2 hotfix that corrects the same problem. The following post-SP1 hotfixes
are not included with Exchange 2000 SP2:
Q306860, Q312606, Q311304, Q305473, Q306514, Q307652, Q306122,

Q311532, Q311535, Q311020, Q300574, Q306999, Q305314, Q311413,
Q310080, Q307194, Q306177, Q306644, Q310653, Q312019, Q298911,
Q309421, Q300617, Q309092, Q306634, Q306796, Q310501, Q310821,
Q302930, Q311509, Q306241, Q306633, Q311089, Q307330, Q308350,
Q308397, Q310120, Q311437
Note Exchange 2000 SP1 does not include the View as Web Page
option in Outlook Web Access. This option has been reinstated with
Exchange 2000 SP2.
Manual Registry Changes
If you made manual changes to the registry on your servers running

Exchange 2000, these changes may be reset to their default settings during the
installation of Exchange 2000 SP2.
Disable Notifications
If you attempt to install Exchange 2000 SP2 on a server that is configured to

monitor and send e-mail notifications, the installation will fail — specifically, a
0xC103798A error will occur when processing Miscellaneous Atom. For
information about how to correct this problem, see Microsoft Knowledge Base
article Q270668, “XADM: Exchange 2000 Setup Fails with OxC103798.”
Slipstream Support
Exchange 2000 SP2 does not support ”slipstreaming” – meaning that you must
install Exchange 2000 before applying SP2. However, the Active Directory
Connector (ADC) service supplied with Exchange 2000 SP2 is a full installation
that includes Setup.exe. Therefore, you can install the SP2 version of the ADC
service without first installing the original or SP1 version.
Unattended Installation
To create an unattended installation script for updating your servers running

Exchange 2000, use the /CreateUnattend command-line parameter of
Update.exe.

Updating Through Terminal Services
You can install all SP2 components through Terminal Services Client. However, to
properly update the Exifs.dll driver, you must restart the server at the end of the
update (you will be notified to restart). You must do this because the Exchange
Installable File System driver, which resides in kernel mode, cannot be properly
shut down through Terminal Services Client.
For best results, select No when prompted for the automatic restart. Then
manually initiate the restart from the Start menu. Some automatic restart
prompts actually shut down the server rather than restart it.
To ensure that your server restarts after applying SP2 through Terminal
Services
1. After the SP2 update process is finished, indicate that you do not want to
restart the server.
2. Click Start, and then click Shut Down.
3. In Shut Down Windows, in the drop-down list box, click Restart.
4. Click OK.
Minimizing Downtime
To update your servers running Exchange 2000 to SP2 without requiring a restart
at the end of the installation, use the Update.exe file at the server console
(however, all Exchange services still shut down during the update process). The
installation process determines whether the you must reboot message appears
at the end of the installation process.
To avoid a server restart after applying SP2
1. Run Update.exe directly from the console, not through Terminal Services
Client.
2. Before you run the update, shut down all Exchange management consoles and
any custom scripts and applications that rely on Exchange resources (such as
Cdoexm.dll). During the update process, if all files can be successfully over-
written, you are not prompted to restart.
3. If the update experiences problems updating one or more files, the file names
in question appear in a warning dialog box during the installation. You are
usually presented with the option to Retry, Continue, or Abort. If you realize
that an external process is keeping the file in question open, close down that
process and then select Retry. If selecting Retry does not allow the update to
continue, you should select Continue. Selecting Continue forcibly gives the
files in question temporary names and copies the new versions of the files to
the correct folder. If you select Continue, a restart is required, so the
temporary files can be deleted, and the images of the old file versions can be
removed from memory.
If you are prompted to restart at the end of the installation, it is important to do

so. Running your server without restarting can cause access violations (service
crashes) due to incompatible versions of DLLs in memory.

It is also important to restart the server if the databases fail to mount after SP2 is
applied. The following events in the application log indicate that there is a
problem:
Event Type: Error
Event Source: ESE98
Event Category: Database Corruption
Event ID: 470
Date: 5/31/2001
Time: 12:36:10 PM
User: N/A
Computer: SERVER-01
Description:
Information Store (2688) Database F:\EXCHSRVR\MDBDATA\PRIV3.edb is

partially attached. Attachment stage: 4. Error: -1811.
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9519
Date: 5/31/2001
Time: 12:36:10 PM
User: N/A
Computer: SERVER-01
Description:
Error 0xfffffbbe starting database "Storage Group 1\Mailbox Database 3" on

the Microsoft Exchange Information Store.
Failed to attach to Jet DB.
This problem occurs when outstanding file handles to IFS are still open during the
upgrade to SP2. The ExIFS driver does not shut down cleanly and therefore fails
to restart. To fix the problem, restart the server — you do not need to reinstall
SP2.
SP2 and Front-End Servers
After a front-end server running Exchange 2000 is upgraded to SP2, the system
attendant process will no longer initialize the Recipient Update Service, the offline

address book generation process, the directory service proxy (DSProxy) process,
free/busy publishing, and Mailbox Manager. Ensure that only back-end servers
are designated to run the Recipient Update Service and offline address book
generation process. Additionally, because DSProxy is no longer initialized on SP2
front-end servers, it is not possible to build a new MAPI profile by instructing the
client to communicate with the front-end.
SP2 Update Process Stops Non-Critical Services
As part of the update process, non-critical services such as License Logging, IIS
Admin, and Windows Management Service are stopped. Many of these services
hold Exchange-specific DLLs open, and the update process attempts to shut down
these services so that files can be upgraded cleanly.
In some circumstances, these non-critical services may fail to shut down within
the allotted time. This is not a problem for the update process; the process
continues and does not experience a critical error. However, during the file copy
process, the update process may report files, such as Address.dll, as being in use.
Selecting Retry does not resolve this issue. If you want to avoid restarting at the
end of the update process, use the Computer Management snap-in to manually
shut down these non-critical services. Then, after you shut down these services,
select Retry at the file copy stage to resolve the problem. If you don’t mind
restarting at the end of the update process, select Continue and the file is
cleaned upon restarting.
Removing Service Pack 2
After installation, it is not possible to remove Exchange 2000 SP2 or

Exchange 2000 Conferencing Server SP2. If you need to back-out of the SP2
upgrade and go back to the original release of Exchange 2000, you must restore
the original system state, file system, transaction log files, and databases.
If you apply SP2 to a server, the databases are upgraded to a new major version.
For this reason, you should immediately back up your server after applying SP2.
If you attempt to restore an SP1 database and log file set to an SP2 server, the
database will fail to upgrade because of the major ESE version change. For more
information, see Microsoft Knowledge Base article Q316794, “XADM: Exchange
2000 SP2 Does Not Allow You to Restore Exchange 2000 or Exchange 2000 SP1”.
Active Directory Connector SP2 Update Permissions
To install a new Active Directory Connector, or to update an existing Active

Directory Connector to SP2, log on to the target machine with the following
permissions:
• Member of the “Enterprise Admins” group in the Active Directory database
• Member of the local “Administrators” group

Exchange 2000 SP2 Update Permissions
To update an existing Exchange 2000 installation to SP2, log on to the target

machine with the following permissions:
• At least Exchange Administrator (full or standard) of the Administrative Group

that contains the server object to be updated
Note If the server running Exchange 2000 is part of an Exchange

cluster, or has Key Management Service installed, log on to the target
machine with the following permissions:
• Full Exchange Administrator to the Exchange organization
Exchange System Management Tools SP2 Update Permissions
It is important that you update any computers running System Management

Tools to Service Pack 2. To update an existing Exchange System Manager
installation to Service Pack 2, log on to the target machine with the following
permission:
Exchange 2000 Conferencing Server SP2 Update Permissions
To update your servers running Exchange 2000 Conferencing Server to SP2, log
on to the target computer with the following permissions:
• Full Exchange Administrator to the Exchange organization
If you didn’t previously update to Exchange 2000 Conferencing Server SP1, you
will also require the following permission:
• Member of “Domain Admins” in the domain where the conferencing server

resides
Note The ”Domain Admins” permission is required because the SP2

update for Exchange Conferencing Server creates a new global security
group called “Exchange Conferencing Access Servers” in the Users
container of the Active Directory domain.
Manual Changes Made to ASP Files in Conferencing Server
If you manually edit any of the Exchange 2000 Conferencing Server files (such as
List.asp), the Exchange Conferencing Server SP2 update process does not
upgrade those files to SP2. In these circumstances, you may have a non-
functional Web user interface after applying SP2. To resolve this problem, restore
the original versions of the Exchange 2000 Conferencing Server files and reapply
the Exchange Conferencing Server SP2 update.

Applying Exchange 2000 SP2
This section outlines the recommended steps for upgrading your Exchange
installation to SP2.
Updating the Active Directory Connector Service
To update an existing Active Directory Connector to SP2
1. Run Setup.exe from the \adc\i386 folder.
2. Select Reinstall.
Updating Exchange 2000 Server
To update an existing server running Exchange 2000 to SP2
1. Run Update.exe from the \Setup\i386 folder.
2. From the component list, select Update.
3. After the installation, restart the server if prompted to do so.
Updating an Exchange 2000 Cluster
Exchange 2000 SP2 supports rolling upgrades.
To update an Exchange 2000 cluster running in Active/Passive mode
1. Update the passive node to SP2 by running Update.exe from the \Setup\i386
folder.
2. Select Update.
3. Wait for the update to complete.
4. Restart the upgraded node.
Note If you do not restart the node after applying SP2, the virtual
servers may not fail-back correctly.
5. Fail-over the Exchange virtual servers from the active node to the updated
passive node.
6. Repeat steps 1 though 4 for the other node.
7. Optional: fail-over the Exchange virtual servers to the original server. To

minimize user downtime, ignore this step.
If you are running a 2-node Active/Active cluster, you can follow a similar process
to update your servers to SP2. For Active/Active cluster upgrades, you should fail-
over your Exchange virtual servers so that both are running on the same node.
After you have performed this operation, follow the Active/Passive upgrade steps
listed above.

Updating Exchange 2000 Conferencing Server
When updating Exchange 2000 Conferencing Server to SP2, It is extremely

important that you change the current working directory to the path containing
the Exchange 2000 Conferencing Server SP2 installation .msi package before you
execute Update.exe. If you fail to do this, an error appears indicating that the
.msi package could not be found.
For example, if the Microsoft Exchange 2000 Conferencing Server.msi file is

located in D:\Conferencing\Setup\i386, open a command prompt or Windows
Explorer, change the directory to this path, and then run Update.exe.
Note In the scenario above, the update will not be successful if you
click Start, click Run, and then type
D:\Conferencing\Setup\i386\update.exe.
Verifying That the Upgrade was Successful

After updating each server running Exchange 2000 to SP2, verify that the
upgrade was successful.
To verify that an SP2 upgrade was successful
1. In Exchange System Manager, click Servers and verify that the build stamp
shows the upgraded server running build 5762.4
2. In the Computer Management snap-in, ensure that all the appropriate

Exchange services are listed as Started.
3. Log on to a mailbox homed on the upgraded server. Send a message to

yourself and expand the public folder hierarchy.
4. Look in the application log on the upgraded server. Verify that unexpected
warning and/or error messages were not logged.

Troubleshooting SP2 Upgrade Problems
Your Exchange 2000 SP2 upgrade should be free of errors. This section helps you
troubleshoot unexpected upgrade problems.
Troubleshooting Exchange 2000 SP2
In some circumstances, you may see an error when attempting to apply

Exchange 2000 SP2.
To troubleshoot errors while applying Exchange 2000 SP2
1. Make a note of the error, and search for it at http://support.microsoft.com to

see if the error is a known issue.
2. Restart the server running Exchange, and immediately attempt to reinstall

SP2.
3. Restart the server running Exchange, manually shut down all Exchange and
IIS services, and then attempt to reinstall SP2.
4. Look at the Exchange Server Setup progress log that exists in the root of your
system partition. Stating at the end of the log file, search the contents until
you see the details of the error. The progress log may give you additional
information as to why the update failed.
5. Contact Microsoft Product Support Services (PSS). Be ready to supply the

Exchange Server Setup Progress Log to PSS.
In practice, you can rectify most failed service pack installations by restarting the
server and attempting the installation again. Problems can occur when a server
running Exchange has been in continuous operation for a long duration, and the
services fail to stop before the timeout. For example, it is relatively common for
the Microsoft Exchange Store process (Store.exe) or Site Replication Service
(SRS) to take a long time to shut down.
Troubleshooting Exchange 2000 Conferencing Server SP2
To troubleshoot errors while applying Exchange 2000 Conferencing

Server SP2
1. Double-check that the administrator installing the service pack has all the
necessary permissions to install SP2. The majority of installation errors occur
because the administrator does not have the correct permissions. For more
information about Exchange 2000 Conferencing Server update permissions,
see “Exchange 2000 Conferencing Server SP2 Update Permissions” earlier in
this document.
2. Double-check that the working directory, when running Update.exe points to

the folder where the .msi file exists.
3. Create a log file for the update by running:

MSIEXEC /fvemus “Microsoft Exchange 2000 Conferencing Server.MSI”
/L*v “C:\ECSSP2.LOG”
4. Inspect the log file that was generated; it may give you some detailed
information as to what went wrong.
5. If the update process is still not successful, contact Microsoft Product Support
Services (PSS), and be ready to supply the .msi log file as described in step 3.

Clustering Scenarios
Exchange 2000 SP2 includes support for the following cluster configurations on
Windows 2000 Advanced Server with SP2:
• 2-node Active/Active
• 2-node Active/Passive
For Active/Active clusters it is strongly recommended that you configure no more

than two Exchange virtual servers. For Active/Passive clusters you should
configure a single Exchange virtual server.
Note Exchange 2000 SP2 strictly enforces a maximum of four active

storage groups per node, independent of the number of Exchange virtual
servers running.
Additionally, Exchange 2000 SP2 includes support for the following cluster
configurations on Windows 2000 Datacenter Server:
• 2-node Active/Passive
• 3-node Active/Active/Passive (N+1)
• 4-node Active/Active/Active/Passive (N+1)
• 4-node Active/Active/Passive/Passive (N+2)
Use Active/Passive clusters when possible to increase scalability and reduce

failover times. Active/Active clusters are only supported in 2-node configurations
in which each node has a maximum of 40 percent loading and 1900 simultaneous
users.
Exchange 2000 enforces N+1 mode in 3- and 4-node configurations. Additionally,

you can only have one Exchange virtual server active on a node at any time.
For more information about clustering with Exchange 2000 SP2, see the white
paper Deploying Microsoft Exchange 2000 Server Service Pack 2 Clusters at
http://www.microsoft.com/exchange/techinfo/deployment/2000/E2KSP2_Clus
ter.asp.

Overview of New Features and Enhancements in
Exchange 2000 SP2
This section lists new features and enhancements in Exchange 2000 SP2.
Directory Enhancements
• New DSAccess architecture
• Automatic failover for Recipient Update Service
• Enhanced support for one-way Active Directory Connector (ADC) Recipient

Connection Agreements
• Site Replication Service (SRS) arbitration preference
• Better support for the ADC service when using migration tools such as the
Active Directory Migration Tool (ADMT)
Transport Enhancements
• New non-delivery report (NDR) codes and descriptions
• PreSubmissionQueue exposed in the Exchange System Manager console
• Enhanced queue management
• Increased performance through asynchronous delivery to local databases
• Delivery Status Notification hooks for transport event sinks
• NDR improvements
• Link state suppression
Exchange Information Store and Extensible Storage Engine (ESE)

Enhancements
• Improved virtual memory and thread utilization
Content Indexing Enhancements
• Removed scheduled rebuild functionality
• Miscellaneous enhancements and improvements
Administration Enhancements
• Enhanced Windows Management Instrumentation (WMI) support and

Exchange Management service
• Directory Access user interface

• Enhanced message tracking
• Enhanced public folder management
• Enhanced Mailbox Manager
• Dr. Watson.NET support
• Mailbox attribute cleanup support
• Deleting a mailbox when the Exchange Information Store is down
• Exposing the Admin Note field as a column
• Warning raised if Apply Now is selected on a recipient policy
Troubleshooting Enhancements
• Archive Sink
• E2KDSInteg tool
• SMTP Reinstall tool
Migration Enhancements
• Mailbox migration support for Exchange 2000
• Two-step migration (through .pst files)
• Filter messages to migrate (date and subject)
Setup Enhancement
• RemoveOrg switch
Outlook Web Access Enhancements
• Contact distribution list support
• Search
• Log Off page & warning
• Segmentation
• New mail notification
• Calendar reminders
• New calendar controls
• Improved calendar printing
• New tree control
• Type-down search

• Enhanced keyboard navigation support
• Indent messages when By Conversation Topic is selected in the View list

box
• New Uplevel Help
• Localized into Catalan

In-Depth Guide to New Features and Enhancements
in Exchange 2000 SP2
This section describes, in detail, the new features and enhancements in
Exchange 2000 SP2.
Directory
New DSAccess Architecture

The DSAccess component in Exchange 2000 SP2 provides the underlying
mechanism to support queries to the Active Directory database and has been
much improved over the version that ships with Exchange 2000 SP1.
The following list describes the improvements to the DSAcess architecture in

Exchange 2000 SP2:
• Suitability testing of all domain controllers and global catalog servers to

ensure that each Active Directory server is functioning correctly before use.
• Better load balancing of requests — more than ten Active Directory servers
can be used in the local site if they are available.
• Cache fine-tuning — objects returned from the configuration naming context

can be cached for 15 minutes.
• Better tolerance of domain controller and global catalog server outages —

seamless fail-over.
• Better out-of-site fail-over support. DSAccess now uses the Active Directory
site infrastructure (site links and costs) to determine the best domain
controllers and global catalog servers for fail-over.
• Fail-back support (within 5 minutes) when the local domain controller and
global catalog server is back up and running.
• Diagnostics logging to troubleshoot problems.
• A new tab called Directory Access is available on the server object in the
Exchange System Manager console. This tab allows you to both view and set
the domain controllers and global catalog servers being used by DSAccess.
• Better support for running front-end servers in a de-militarized zone without

an RPC requirement to Active Directory servers inside the corporate network.
Around 60 percent of the DSAccess component was re-architected between

Exchange 2000 SP1 and SP2. This re-architecture came about to resolve the
various problems that Active Directory servers could experience. Previously,
DSAccess would use a domain controller or global catalog server as long as it
responded on port 389 or 3268. Even though a server may respond to a port
open request, it may be experiencing various faults or issues. Communicating
with a malfunctioning domain controller or global catalog server results in poor
Exchange 2000 performance.

Exchange 2000 SP2 introduces a set of suitability tests to ensure that only
functional Active Directory servers are used. These tests are divided into three
categories:
• Hard Determines whether DSAccess uses a domain controller or global

catalog server at all
• Soft Determines how often a domain controller or global catalog server is

used (relative to other domain controllers or global catalog servers)
• Side Determines what a particular domain controller or global catalog server

can be used for
The following list describes the hard suitability tests in Exchange 2000 SP2:
• Reachable over port 389 (domain controller) and 3268 (global catalog server)
• Group policy system access control list (SACL) test (that is, whether the
server resides in a domain that has been prepared with DomainPrep)
• RootDSE returns isSynchronized = TRUE (for domain controllers and global

catalog servers)
• RootDSE returns isGlobalCatalogReady = TRUE (for global catalog servers

only)
• Connection to NETLOGON service over RPC to check:
o Available disk space.
o Time synchronization.
o Replication participation.
The following list describes the soft suitability tests in Exchange 2000 SP2:
• Evaluation of DNS weight by means of the DNSQUERY API (DNS priorities are
not evaluated)
• Flexible Single Master Operations (FSMO) roles
• Active Directory site residence
• LDAP result speed
• Number of outstanding LDAP requests
The following list describes the side suitability tests in Exchange 2000 SP2:
• Number of writable naming contexts
• Global catalog server (TRUE or FALSE)
If you enable diagnostics logging for the Topology category of DSAccess, you are
also presented with a suitability report (see Figure 1).

Figure 1 Suitability report from DSAccess
Automatic Fail-Over for Recipient Update Service

The Recipient Update Service is responsible for stamping critical information on
mail and mailbox-enabled objects in the Active Directory database. For example,
the Recipient Update Service is responsible for stamping the SMTP address and
Address List identifiers on a newly created mailbox.
Each domain that is prepared with DomainPrep must have at least one Recipient
Update Service. Multiple instances of the Recipient Update Service can be created
if more than one domain controller exists within the domain. The Recipient
Update Service runs on a single server running Exchange 2000 and processes
information based on the information that it retrieves from a single, nominated
domain controller.
With Exchange 2000 SP2, if the nominated domain controller fails, the Recipient
Update Service will fail-over to a different Recipient Update Service within the
local Active Directory site and domain (if available) to continue its important
processing tasks. When fail-over occurs, the new domain controller is used. Every
few minutes, the Recipient Update Service checks to see if the nominated server
has returned to service.
Enhanced Support for One-Way ADC Recipient Connection Agreements

If one-way Recipient Connection Agreements are configured between
Exchange 5.5 and the Active Directory database, the Active Directory Connector
(ADC) service behaves differently after the ADC service is upgraded to
Exchange 2000 SP2.

When the ADC service is instructed to perform a full re-synchronization, or when
new objects are to be created in the Active Directory database, the ADC service
automatically sets the msExchPoliciesExcluded attribute on each processed
user object. The data value of this attribute is the globally unique identifier
(GUID) for the Exchange organization. Effectively, this setting prevents the
Recipient Update Service from re-evaluating the proxy e-mail addresses for users
synchronized by this Recipient Connection Agreement. This is important because
in previous versions of Exchange 2000, the Recipient Update Service could
change the SMTP address of users synchronized by means of a one-way Recipient
Connection Agreement. This change could result in non-delivery reports (NDRs)
and overwrite SMTP addresses when the connection agreement is changed to
two-way.
Although this behavioral change can be positive, companies that employ bi-
directional, one-way Recipient Connection Agreements from the same containers
will run into problems because changes in the Active Directory database will not
fully propagate back to Exchange 5.5. In these scenarios, it is highly
recommended that two-way Recipient Connection Agreements be used.
Site Replication Service (SRS) Arbitration Preference

When a new Administrative Group is created in an Exchange 2000 mixed-mode
organization, an existing Site Replication Service (SRS) is selected to replicate
this new group to the Exchange 5.5 environment. Similarly, when a new
Exchange 5.5 site is added to a mixed-mode organization, an existing SRS is
selected to replicate the new site to the Active Directory database.
Prior to Exchange 2000 SP2, the arbitration logic for which SRS was selected was
dictated by the alphabetical ordering of these Administrative Groups and site
names. For example, consider the following mixed Exchange 5.5/2000
Administrative Groups:
• Brisbane-01
• London-01
• Vancouver-01
If you want to add a new Exchange 2000 Administrative Group called Melbourne-
01 to Exchange 5.5, the London-01 SRS replicates the new group because
Melbourne-01 is alphabetically closer to London-01 than the other names. This
may create undesirable replication patterns in mixed environments.
To resolve this issue, Exchange 2000 SP2 includes a PreferredSRS setting that
allows you to dictate which SRS is used in the arbitration logic. Set
PreferredSRS in the following locations for Exchange 2000 and Exchange 5.5:
• For new Exchange 2000 Administrative Groups, type PreferredSRS <SRS-

Server-Name> in the Administrative note field of the Administrative Group
object in the Active Directory database.
• For new Exchange 5.5 sites, type PreferredSRS <SRS-Server-Name> in

the Administrative note field of the Configuration object, underneath the
site object in the Exchange 5.5 Directory.
The <SRS-Server-Name> field should be populated with the short name (for
example, LON-01) of the server running Exchange 2000 on which an instance of

the SRS database resides. Remember to upgrade all SRS servers to
Exchange 2000 SP2 or higher before using the PreferredSRS setting because
earlier versions of Exchange 2000 do not recognize this parameter. Additionally,
the PreferredSRS setting does not re-arbitrate existing Administrative Groups
and sites; the setting only works for new groups or sites that are created after
Exchange 2000 SP2 is applied.
Better Support for the ADC Service When Using Migration Tools Such As
ADMT
If you use the Active Directory Migration Tool (ADMT) to migrate user accounts
from Microsoft Windows NT® 4.0 domains to the Active Directory database, and
then use the ADC service to synchronize these accounts with Exchange 5.5, it is
important that you use the ADC service that is supplied with Exchange 2000 SP2.
Previous versions of the ADC service do not stamp the
msExchMasterAccountSid attribute on user accounts that are not created by
the ADC service. This attribute is critical to the operation of Exchange 2000
mailboxes.
Transport
New NDR Codes and Descriptions

Prior to Exchange 2000 SP2, most non-delivery reports (NDRs) would return with
a generic 5.0.0 error code. This generic error did not help identify where in the
system the failure occurred. In Exchange 2000 SP2, the 5.0.0 error is still
returned in some scenarios. However, in most cases one of the new error codes is
returned. The new codes and descriptions provide a much better explanation as
to which component has failed. The following list describes the new error codes:
• 5.5.0 – Protocol error (SMTP error)
• 5.4.4 – Routing next hop not found
• 5.4.0 – DNS failure
• 4.3.2 – The administrator has manually non-delivered the message
For more information about NDR codes in Exchange 2000 SP2, see the Microsoft
Knowledge Base article Q284204, “XCON: Delivery Status Notifications in
Exchange 2000 Server.”
PreSubmissionQueue Exposed in the Exchange System Manager Console

Exchange 2000 SP2 includes a new queue called PresubmissionQueue. This new
queue is exposed under the SMTP virtual server in the Exchange System Manager
console. This queue existed in previous versions of Exchange, but it was hidden
from the user interface. PreSubmissionQueue holds messages that are received
by the server, but have not been processed by the OnSubmission transport event
sinks.
The exposure of this new queue is designed as a troubleshooting aid. In previous

versions of Exchange, it was possible for messages to become stuck in this
queue, and without the associated UI, it was difficult to troubleshoot the problem.

Enhanced Queue Management
In Exchange 2000 SP2, the queue user interface in the Exchange System
Manager console now displays the correct values for columns when viewing
messages that are waiting in queues. In addition, SP2 now includes new
performance monitor counters.
Increased Performance Through Asynchronous Delivery to Local

Databases
In Exchange 2000 SP2, messages are delivered from the transport to local
databases using asynchronous threads. Prior to SP2, a synchronous threading
model was used, and in some scenarios, the MAPI client stopped responding after
sending messages.
DSN Hooks for Transport Event Sinks

If you are writing C++ transport event sinks, it is now possible to hook the
Delivery Status Notification interface so that you can perform actions on read
receipts, delivery receipts, and non-delivery receipts. For example, it is possible
to change the text of a Delivery Status Notification or to suppress the message
altogether. For more information about Delivery Status Notification events, see
the latest version of the Exchange Software Development Kit (SDK) available on
the MSDN Web site at http://msdn.microsoft.com/exchange.
NDR Improvements
In Exchange 2000 SP2, all non-delivery messages are logged in the application
event log if Maximum diagnostics logging is set on the Connection Manager
category of the MSExchangeTransport service. All NDR messages are logged with
an event identifier of 756. This setting aids monitoring and troubleshooting.
It is also possible to specify (through a registry parameter) that messages larger

than a certain size not be returned with NDR error messages. By default, there is
no size restriction; this allows users to use the Send Again function. In
bandwidth-sensitive environments, it is important to set the following registry
parameter to reduce the amount of traffic on the WAN:
Path: HKEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Services \ SMTPSVC \ Queuing
Parameter name: MaxDSNSize
Parameter type: REG_DWORD
Parameter value: <value in bytes>
Link State Suppression

When the state of a network link is changed, status information is sent to all
other servers running Exchange 2000 in the organization. When working in large
routed environments or networks that constantly suffer from outages, link state
traffic can possibly account for a large proportion of the total traffic on the
network. In some environments, especially hub-and-spoke routed scenarios, it is
advantageous to turn off link state routing or suppress it on certain servers. With
Exchange 2000 SP2, it is possible to suppress and disable link state traffic by use
of the following registry parameter:
Path: HKEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Services \ RESvc \ Parameters
Parameter name: SuppressStateChanges

Parameter value: 0x00000001
Store and ESE
Improved Virtual Memory and Thread Utilization

In Exchange 2000 SP2, both the Store.exe process and Extensible Storage Engine
(ESE) are improved. There is a reduced requirement for contiguous memory when
failing over in a cluster configuration and better performance optimization of ESE
parameters in a default configuration.
Content Indexing
Scheduled Rebuild Functionality is Removed

In Exchange 2000 SP2, it is no longer necessary to set a rebuild frequency for
full-text indexing on a database. The only scheduled operation for full-text
indexing is the update interval (for example, an incremental crawl).
From the context menu of the database object in the Exchange System Manager
console, you can perform the following immediate operations:
• Delete full-text index
• Start incremental population
• Start full population
Miscellaneous Enhancements and Improvements

Exchange 2000 SP2 includes many updates and improvements to the content
indexing engine. The majority of these improvements address the performance
and stability of the MS Search service.
Administration
Enhanced Windows Management Instrumentation (WMI) Support and

Exchange Management Service
The following new Windows Management Instrumentation (WMI) providers are
supplied with Exchange 2000 SP2:
• DSAccess WMI provider Allows you to programmatically retrieve/set the

domain controller and global catalog servers used by the server running
Exchange 2000.
• Message Tracking WMI provider Allows you to programmatically search

for messages across servers running Exchange 2000.
The Exchange System Management service executes the new Exchange WMI
providers. This new service is located under Services in the Computer
Management snap-in.

Note For the new Directory Access and Message Tracking features to
work, it is important that the new Exchange System Management service
is running.
For more information about WMI support in Exchange 2000, see the latest version
of the Exchange SDK available on the MSDN Web site at
http://msdn.microsoft.com/exchange.
Directory Access User Interface

In the Exchange System Manager console, a new Directory Access tab is
located in server Properties (see Figure 2). You can use this tab to view and set
the domain controllers and global catalog servers that the DSAccess component
uses. Hard-coded server settings are made in the registry of the server running
Exchange 2000 SP2. These hard-codes are evaluated every 15 minutes, and the
domain controllers and global catalog servers are tested for suitability. For more
information about DSAccess, see “New DSAccess Architecture” earlier in this
document.
Any Active Directory servers that do not pass suitability testing are logged in the
application event log and excluded from the DSAccess topology. If all hard-coded
servers do not pass the suitability tests, DSAccess uses its standard topology
discovery logic to find Active Directory servers. Therefore, DSAccess uses the
hard-coded server list as a preferred set of Active Directory servers.
The Directory Access tab uses the new DSAccess WMI provider to communicate
with the DSAccess component. It is possible to programmatically view or set
DSAccess information using your own scripts. For more information about this
topic, see the latest version of the Exchange SDK available on the MSDN Web site
at http://msdn.microsoft.com/exchange.

Figure 2 The Directory Access tab in server Properties
Enhanced Message Tracking

Exchange 2000 SP2 includes significant enhancements to the message tracking
feature. Firstly, the user interface in the Exchange System Manager console is
improved. Secondly, the new UI relies upon the Message Tracking WMI provider
on each Exchange 2000 SP2 server instead of manually searching through the
files on the tracking log share. By using the Message Tracking WMI provider,
message tracking is much faster, especially across large, distributed Exchange
deployments. In scenarios where slow WANs are utilized, message tracking
performance can improve from several hours to a few seconds.
Prior to Exchange 2000 SP2, when the Exchange System Manager console was
used to track messages, the administrator specified which Exchange server would
be the starting point. Then the Exchange System Manager console would connect
to the tracking log share in sequence, download all the tracking logs, and search
each line until it found the next server in the chain. These types of searches could
take several hours in large environments.
In Exchange 2000 SP2, the Exchange System Manager console connects to the
Message Tracking WMI provider and relays the data to the WMI provider. The
WMI provider then searches for that data in the message tracking logs. Although
the message tracking architecture has not changed, the execution of the search
occurs locally on each server rather than being driven from the Exchange System
Manager console. Only the results of the search are passed back to the Exchange
administrator.
Fast, local searching only occurs on servers running Exchange 2000 SP2. If a
message track hits a server running Exchange 5.5 or Exchange 2000 SP1, the
logic falls-back to the old searching style.

Note In the Exchange System Manager console, when you select
Message Tracking Center for the first time, a background thread runs
to build the tracking topology. A message track cannot occur until the
topology is built; therefore, the very first message track may take
slightly longer to perform. Subsequent message tracks occur quicker. For
this reason, to ensure that all searches are fast, it is recommended that
you keep the Exchange System Manager console open (although the
window focus does not need to be kept on the Message Tracking
Center).
Enhanced Public Folder Management

Prior to Exchange 2000 SP2, all public folder management using the Exchange
System Manager console was performed through remote OLE DB. In
Exchange 2000 SP2, the system management interface uses WebDAV to yield
better performance and error reporting.
Enhanced Mailbox Manager

Exchange 2000 SP1 delivered the Mailbox Manager component. Exchange 2000
SP2 enhances this component by allowing you to include specific custom folders
in the processing schedule. Additionally, you can now forcibly stop Mailbox
Manager through the Exchange System Manager console.
Dr. Watson .NET support

Dr. Watson .NET is a new initiative by Microsoft to proactively gather information
about service crashes and outages that occur at customer sites. When a service
exception or crash occurs, the crash dump information is uploaded to
https://watson.microsoft.com. Upon successful upload, an event is logged in the
local application event log to inform you of the “bucket” number where this data
is logged.
Exchange 2000 SP2 includes support for Dr. Watson .NET in the following
services:
• Store.exe process (Microsoft Exchange Information Store)
• Mad.exe process (Microsoft Exchange System Attendant)
• ExMgmt.exe process (Microsoft Exchange System Management)
• CDOExm.dll (CDO for Exchange System Management)
• Exchange System Manager
• Exchange Directory Service extensions for the Active Directory Users and
Computers snap-in
Crashes that occur in the Exchange System Manager console and Directory
Service extensions for Active Directory Users and Computers result in a user
interface notification (see Figure 3). All other crashes do not produce a pop-up
menu.
Note By default, Dr. Watson .NET support is disabled. To enable Dr. Watson
.NET support, in Exchange System Manager, in server Properties, on the
General tab, select the Automatically send fatal service error information
to Microsoft check box. For Exchange 2000 to upload crash dump information to

the Dr. Watson server, ensure that all the necessary proxy settings are
configured correctly.
Figure 3 Pop-up notification when a crash occurs
Mailbox Attribute Cleanup Support

Exchange 2000 SP2 includes a new option called Remove Exchange Attributes
in Exchange Tasks on mailbox-enabled users. This option allows administrators
to forcibly remove Exchange attributes (such as HomeMDB, HomeMTA,
msExchHomeServerName, msExchADCGlobalNames, and so on) from that user.
Use this option in the following scenarios:
• The ADC service matches the incorrect Exchange 5.5 mailbox to the Active
Directory user.
• The mailbox for an Active Directory user points to an Exchange 2000

server/database that no longer exists.
• To reconnect a mailbox after disaster recovery.
The Remove Exchange Attributes option only appears in the Exchange Tasks
wizard within the Active Directory Users and Computers snap-in when the
Advanced Features option is selected within the MMC console.
Deleting Mailboxes When the Exchange Information Store Service is

Down
In Exchange 2000 SP2, you can now delete a mailbox even when the database or
home server is down.
Administrative Note Field Exposed in Columns

In Exchange 2000 SP2, you can now view the Administrative Note field as a
column in the Exchange System Manager console.

Warning Raised if Apply Now is Selected on a Recipient Policy
If an Exchange administrator selects the Apply Now option on a recipient policy,
a warning box appears verifying that the administrator understands the effect
selecting this option has.
Troubleshooting
Archive Sink
Exchange 2000 SP2 includes a transport event sink that you can install to log the
properties for all messages flowing through the transport. This event sink is
useful for troubleshooting SMTP and message conversion issues.
After Exchange 2000 SP2 is applied, you can locate the Archive Sink
documentation and installation code in <drive>:\Program Files\Exchsrvr\Bin. The
following files are in this folder:
• Archivesink.dll
• Archivesink_Readme.txt
• Archivesink_Setup.vbs
E2KDSInteg Tool
Exchange 2000 SP2 includes a new troubleshooting tool called E2KDSInteg.
E2KDSInteg is used for diagnosing problems with Exchange attributes (for
example, missing or corrupt attributes) on objects in the Active Directory
database.
The E2KDSInteg tool and its documentation are located on the Exchange 2000
SP2 CD in the \support\utils\i386\E2KDSInteg folder.
Note The E2KDSInteg tool must be manually expanded and run from
the command line.
SMTP Reinstall Tool

The SMTP Reinstall tool is useful in scenarios where the IIS SMTP component is
removed after Exchange 2000 is installed on a server. After the Windows 2000
SMTP service is reinstalled on the server, use SMTPReinstall.exe to re-register the
Exchange 2000 transport and event sinks with the SMTP service.
The SMTP Reinstall tool and its documentation are located on the Exchange 2000
SP2 CD in the \support\utils\i386\ folder.
Note This tool is not supported on Exchange 2000 clusters.
Migration
Mailbox Migration Support for Exchange 2000

In Exchange 2000 SP1, the Exchange Migration Wizard was extended to support
the migration of Exchange 5.5 mailboxes between organizations. In
Exchange 2000 SP2 this support is extended further to facilitate the movement of
Exchange 2000 mailboxes between organizations.

Note The Exchange Migration Wizard only supports inter-organization
mailbox moves.
Two-Step Migration (through a .pst file)

The Exchange Migration Wizard now supports a two-step migration process for
moving Exchange 5.5 and Exchange 2000 mailboxes between organizations. The
first step of the process copies the mailbox and its contents to a .pst file. The
second step of the migration process involves importing the contents of the .pst
file to a new mailbox.
Filter Messages to Migrate (date and subject)

The Exchange Migration Wizard now supports the filtering of messages, based on
date and subject, when moving Exchange mailboxes between organizations.
SETUP
/RemoveOrg Switch
The Update.exe program supplied with Exchange 2000 SP2 includes a new
command-line switch called /RemoveOrg. You can use this switch to remove all
Exchange organization information (Administrative Groups, Routing Groups,
server objects, and so on) from the configuration naming context in the Active
Directory database.
Only use the /RemoveOrg switch when you need to remove all Exchange 2000
information from the Active Directory database.
Outlook Web Access
Exchange 2000 SP2 includes significant improvements and enhancements to

Outlook Web Access. Most of these enhancements are only available in Internet
Explorer version 5.0 or later.
Table 1 lists the new features SP2 provides in Outlook Web Access and the clients
on which these features are available. Each feature is described, in detail, later in
this section.
Table 1 Outlook Web Access improvements

Feature Reach Client (for example, Rich Client (Internet
Netscape Navigator, Internet Explorer 5.0 or later)
Explorer 4.0 or earlier)
Contact Distribution Lists Yes – but no search in GAL Yes
Search No Yes
Log Off Page and Warning Yes Yes
Segmentation Yes Yes
New Mail Notification No Yes – Additional system
tray support for Internet
Explorer 5.5+
Calendar Reminders No Yes
New Calendar Controls No Yes
Improved Calendar Printing No Yes – If using Internet
Explorer 5.5, SP2 must be

installed
New Tree Control No Yes
Type-down Search No Yes
Enhanced Keyboard Navigation No Yes
Indent Messages when By No Yes
Conversation Topic is selected in
the View list box
Uplevel Help No Yes
Localized into Catalan Yes Yes
Contact Distribution Lists

This new feature allows users to create personal distribution lists in their Outlook
Web Access Contacts folder. After they create their list, users can add other
contacts by entering the contact’s one-off SMTP address or by selecting the
existing contact card entry. Users of Internet Explorer 5.0 or later can also search
and select contacts from the global address list (GAL).
After the Contact Distribution List is created, you can reference the list name
when composing new mail messages through Ambiguous Name Resolution (ANR).
Additionally, there is full interoperability between Contact Distribution Lists in
Outlook Web Access and Microsoft Outlook.
Search
Exchange 2000 SP2 provides a new Search icon for Outlook Web Access users.
The Search feature allows users to search for messages in their folders. Searches
(single folder and whole folder subtrees) can be based on the From, To, CC,
Subject and Message Body fields. Searches can also be performed on the
Calendar and Contacts folders; however, the Search feature is mainly designed
for searching through standard e-mail folders such as the Inbox.
Note If content indexing is enabled on the server running

Exchange 2000, Outlook Web Access searches leverage the full text
engine.
Log Off Page & Warning

The Log Off page and Warning features are designed for Outlook Web Access
users who regularly use kiosks. A new Log Off icon on the main Outlook bar
connects to a customizable .asp page that gives the user instructions about how
to log off their mailbox. The only way to destroy a user’s credentials is to close all
browser windows.
You can enable the Warning feature to warn the user if the browser window is
being redirected away from Outlook Web Access (either through the closing of a
window or by typing a different URL into the address bar). By default, the
Warning feature is turned off. To enable the Warning feature, use the following
registry parameter:
Path: HKEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Services \ MSExchangeWEB \ OWA
Parameter name: EnableLogoffWarning

Parameter value: 0x00000001
Segmentation
Outlook Web Access segmentation is a new feature in Exchange 2000 SP2. This
feature allows administrators to hide certain functionality from users. This is
useful in hosting environments where subscribers are charged based on their
functionality level.
You can set segmentation on a per-server or per-user basis. For per-server

segmentation, use the following registry parameter:
Parameter name: DefaultMailboxFolderSet
Parameter value: <see table>
If you set this parameter in the registry, all users homed on that server are
affected.
For per-user segmentation, extend the Active Directory schema with the .ldf file
supplied with Exchange 2000 SP2. This .ldf file is located in the
\support\owaschema folder. After you extend the schema, use a tool such as
ADSI Edit to set the msExchMailboxFolderSet attribute for each user. This is a
bit mask that details the functionality to which the user has access. If the
attribute is not set, then the user has full functionality. The bit mask works by
enabling functionality on a user account rather than denying features.
Table 2 lists the Outlook Web Access functions that can be segmented and the
bits that are required to enable the function.
Table 2 Outlook Web Access segmentation

Feature 512 256 128 64 32 16 8 4 2 1
Messaging 0 0 0 0 0 0 0 0 0 1
Calendar 0 0 0 0 0 0 0 0 1 1
Contacts 0 0 0 0 0 0 0 1 0 1
Tasks 0 0 0 0 0 0 1 0 0 1
Journal 0 0 0 0 0 1 0 0 0 1
Sticky Notes 0 0 0 0 1 0 0 0 0 1
Public Folders 0 0 0 1 0 0 0 0 0 1
Calendar Reminders 0 0 1 0 0 0 0 0 0 1
New Mail Notifications 0 1 0 0 0 0 0 0 0 1
IE5.0+ Rich Interface 1 0 0 0 0 0 0 0 0 1
All functionality 1 1 1 1 1 1 1 1 1 1
For example, to configure a user so that they have complete messaging

functionality, no Public Folder access, and are forced to use basic browser (that
is, non-rich) interface, set the following attribute on their account:

msExchMailboxFolderSet = 447 (decimal)
The value is 447 because a full compliment of functionality would involve a

setting of 1023. Then take off 512 to force the basic browser interface and 64 to
deny Public Folder access. The final result is 447.
When setting segmentation options on individual users, enter your value in

decimal form; it may take up to 15 minutes for the parameter to take effect.
When setting segmentation for the server (through the registry), enter your value
in hexadecimal form, and then restart all of the Exchange services.
Note Outlook Web Access segmentation is not designed to interoperate

with the full version of Microsoft Outlook. For example, if you deny
access to the Calendar folder through Outlook Web Access segmentation,
the Calendar folder will be missing in the folder list within the full
Outlook client, but the shortcuts will still be active (thus users can still
access the calendar). With clever configuration of the Outlook profile, it
is possible to emulate segmentation with the full version of Outlook;
however, masking folders is largely superficial.
New Mail Notification

With Exchange 2000 SP2, users of Internet Explorer 5.0 or later receive
notifications when new mail arrives in their Inbox. The notification architecture
uses a “subscribe and poll” method— the browser subscribes for changes in the
Inbox folder, and then polls on a frequency to check for those changes. For users
of Internet Explorer 5.0, the notification appears in the form of an icon on the
navigator bar. For users of Internet Explorer 5.5 or later, the notification appears
in the system tray in addition to on the navigation bar. The browser window does
not automatically refresh — users must click the notification to refresh the
window.
Consider the following information when using new mail notifications:
• If a message comes into your Inbox, but gets moved by a rule, a pop-up
notification appears. This is because the browser subscribed for changes to
the Inbox, and technically, a change occurred.
• If you manually refresh your Inbox and perform actions on new messages
(such as reply, delete and so on), you still receive a notification for those new
messages.
The default polling frequency for the browser is every 2 minutes. To adjust this
setting, use the following registry parameter:
Parameter name: NewMailNotificationInterval
Parameter value: <value in minutes>
Each client poll takes 0.064 megacycles on the server running Exchange 2000.
Therefore, on an 8-processor, 550MHz server with 3000 users, the following CPU
load is generated (assuming all clients polled simultaneously):
• 1 min poll – 7.2% CPU load

• 2 min poll – 3% CPU load
• 5 min poll – 1.4% CPU load
Each user can set various notification options using the Options button in their
mailbox. It is also possible to set these options programmatically. The notification
options are held on the http://schemas.microsoft.com/exchange/newmailnotify
attribute, which is held on the root node of each mailbox. Set the value to the
desired level of notification:
• =0: No new mail notification
• =1: Dialog but no sound
• =2: Sound but no dialog
• =3: Sound and dialog
Calendar Reminders
The new Calendar Reminder feature enables users to set alarms on calendar
appointments as a reminder. Similar to the new mail notification feature, the
underlying Calendar Reminder architecture is based on a subscribe and poll
method. By default, the poll occurs every 15 minutes (registry controlled), and
the browser takes a snapshot of the next 24 hours worth of reminders. Therefore,
subsequent polls of the calendar simply search for new and changed
appointments. This ensures that the reminder appears at the correct time,
independent of the poll.
To adjust the default polling frequency setting, use the following registry
parameter:
Parameter name: ReminderPollingInterval
Parameter value: <value in minutes>
There is complete interoperability between the meeting reminders in Outlook Web

Access and the full version of Outlook. Therefore, if you dismiss a reminder in
Outlook Web Access, you are not reminded again in the full version of Outlook.
Each user can use the Options button in their mailbox to set various reminder
options. It is also possible to set these options programmatically. The notification
options are held on the http://schemas.microsoft.com/exchange/enablereminders
attribute, which is held on the root node of each mailbox. Set the value to the
desired level of notification:
• =0: No reminders
• =1: Dialog but no sound
• =2: Sound and dialog
New Calendar Controls

Exchange 2000 SP2 includes the following improvements to the calendar
interface:

• Improved performance — browser reads free/busy bitmap instead of
searching through all the appointments in the month.
• Multi-day view (shift-click days).
• Double-click in the details pane to create a new item.
• Drag-and-drop in the details pane.
Improved Calendar Printing

Exchange 2000 SP2 introduces calendar printing from Outlook Web Access. To
experience the best results with calendar printing, in Internet Explorer, in
Internet Options, on the Advanced tab, select the print background colors
and images check box.
Note If you use Internet Explorer 5.5, you must upgrade to at least
Internet Explorer 5.5 SP2. If you do not upgrade, any attempt to print
the calendar will result in an error message.
New Tree Control

In Exchange 2000 SP2, the folder tree control is redesigned. Folder expansion is
now an asynchronous process, allowing you to expand folders more quickly, as
well as perform other actions in Outlook Web Access during the expansion.
Furthermore, there is a new icon set on the folder control to provide a more
pleasurable experience.
Another new feature of the tree control is to show the unread message count,
similar to the full version of Microsoft Outlook. Unread message counts appear for
folders in Mailbox as well as in Public Folders. However, the unread message
count is not designed to dynamically increase or decrease when changes occur in
the folder. To forcibly update the counter, you must perform an action in the
folder. Alternatively, you can right-click the folder, and then click Update Folder.
Type-Down Search
If a folder is sorted by Subject or From fields, you can highlight a single
message and type the first few characters of text to automatically move to the
correct point in the folder.
Enhanced Keyboard Navigation Support

Exchange 2000 SP2 includes enhanced keyboard support for Outlook Web Access
users. Keyboard shortcut keys such as HOME, END, PAGE UP and PAGE DOWN
now work in Outlook Web Access. Additionally, SP2 provides First Page and Last
Page buttons that allow you to quickly move between pages.
Indent Messages when By Conversation Topic is selected in the View List

Box
Prior to Exchange 2000 SP2, folders that used View By Conversation Topic did
not display all of the indents denoting the message thread. This issue has been
resolved in Exchange 2000 SP2.

Additional Resources
Web Sites
• Microsoft Exchange 2000 Server
http://www.microsoft.com/exchange
• Windows 2000
http://www.microsoft.com/windows2000
• MSDN Exchange Development
http://msdn.microsoft.com/exchange
White Paper
• Deploying Microsoft Exchange 2000 Server Service Pack 2 Clusters
http://www.microsoft.com/exchange/techinfo/deployment/2000/E2KSP2_Clus
ter.asp
Microsoft Knowledge Base Articles
The following Microsoft Knowledge Base articles are available on the Web at
http://support.microsoft.com/:
• Q316794, “XADM: Exchange 2000 SP2 Does Not Allow you to Restore
Exchange 2000 or Exchange 2000 SP1”
• Q311456, “XGEN: List of Bugs Fixed by Exchange 2000 Server Service Packs”
• Q300517, “Exchange 2000 Services Do Not Start After Windows 2000 SP2
Upgrade”
• Q270668, “XADM: Exchange 2000 Setup Fails with OxC103798”
• Q284204, “XCON: Delivery Status Notifications in Exchange 2000 Server”
For more information: http://www.microsoft.com/exchange
Did this paper help you? Please give us your feedback. On a scale of 1 (poor)
to 5 (excellent), how would you rate this paper?
mailto:exchdocs@microsoft.com?subject=Feedback: Microsoft Exchange 2000

Server Service Pack 2 Deployment Guide

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the
date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment
on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.
This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR
STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.
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.
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, email
address, logo, person, place or event is intended or should be inferred.
 2002 Microsoft Corporation. All rights reserved.
Microsoft, Active Directory, Outlook, Windows, and Windows NT 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.

Microsoft Exchange 2000 Server Service Pack 2 Deployment Guide

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Microsoft Exchange 2000 Server Service Pack 2 Deployment Guide

Transféré par

Droits d'auteur :

Formats disponibles

Microsoft Exchange 2000 Server

Service Pack 2 Deployment Guide

Published: February 2002

Table of Contents ................................................................................................. 1

Preparing for Exchange 2000 SP2 ........................................................................... 3

Applying Exchange 2000 SP2................................................................................ 11

Troubleshooting SP2 Upgrade Problems ................................................................. 13

Clustering Scenarios ........................................................................................... 15

Overview of New Features and Enhancements in Exchange 2000 SP2 ......................... 16

Additional Resources ........................................................................................... 37

For the latest information, please see http://www.microsoft.com/exchange

• Microsoft Exchange Server Development Team

• Microsoft Exchange Joint Development Program (JDP) management team

• Microsoft Exchange Beta Technology Support (BTS)

• Microsoft Exchange User Experience (UE)

Note This paper is intended for advanced-level Exchange 2000

• Enhanced Microsoft Outlook® Web Access

• Re-architected DSAccess component

• Enhanced Message Tracking Center

• Enhanced Mailbox Manager support

• Enhancements to the Exchange System Manager console, including two new

• Exchange 2000 = 4417.5

• Exchange 2000 Service Pack 1 = 4712.7

• Exchange 2000 Service Pack 2 = 5762.4

Preparing for Exchange 2000 SP2

Microsoft Knowledge Base Articles

Windows 2000 Prerequisites

Note There is a compatibility issue between Windows 2000 SP2 and

Microsoft Exchange 2000 Server Service Pack 2 Deployment Guide 3

Installing Multiple Service Packs

Installing Exchange 2000 SP2

• Exchange 2000 SP1.

Exchange 2000 SP2 Co-Existence

Active Directory Connector Custom Local.map and Remote.map

As a safeguard, use a tool such as LDP to export the contents of the

Microsoft Exchange 2000 Server Service Pack 2 Deployment Guide 4

Forest and Domain Preparation

When installing Exchange 2000 SP2, it is not necessary to run /ForestPrep or

Exchange 2000 SP2 Installation Considerations

• Update front-end servers to SP2 before updating back-end servers. If you do

• As a best practice, update servers running the Active Directory Connector

• As a best practice, update messaging bridgehead servers (at both ends of a

Exchange 2000 Conferencing Server SP2 Installation

As a best practice, you should upgrade all servers running Microsoft

Microsoft Exchange 2000 Server Service Pack 2 Deployment Guide 5

Q306860, Q312606, Q311304, Q305473, Q306514, Q307652, Q306122,

Manual Registry Changes

If you made manual changes to the registry on your servers running

If you attempt to install Exchange 2000 SP2 on a server that is configured to

To create an unattended installation script for updating your servers running

Microsoft Exchange 2000 Server Service Pack 2 Deployment Guide 6

2. Click Start, and then click Shut Down.

3. In Shut Down Windows, in the drop-down list box, click Restart.

To avoid a server restart after applying SP2

If you are prompted to restart at the end of the installation, it is important to do

Microsoft Exchange 2000 Server Service Pack 2 Deployment Guide 7

Event Type: Error

Event Source: ESE98

Event Category: Database Corruption

Event ID: 470

Information Store (2688) Database F:\EXCHSRVR\MDBDATA\PRIV3.edb is

Event Type: Error

Event Source: MSExchangeIS