Topic Last Modified: 2007-01-08

Updated   February 7, 2007

© 2005-2006 Microsoft Corporation. All rights reserved.

About This Document

The release notes contain important information that you should know before you deploy and use Exchange Server 2003 Service Pack 2. Make sure that you have also read the Exchange Server 2003 and the Exchange Server 2003 SP1 release notes before you start.

For detailed information about Exchange Server 2003, see the Microsoft Exchange Server TechCenter.

When you install Exchange Server 2003 SP2, the Exchange Server 2003 SP2 online Help, which contains procedures that relate to new tasks for Exchange Server 2003 SP2, is installed automatically in the bin folder of the Exchange Server installation directory. Look for updated Help at Exchange Server 2003 SP2 Online Help.

Relevant Microsoft Knowledge Base Articles

The following Microsoft Knowledge Base articles contain important and complementary information to the release notes.

There is a change in how Microsoft Office Outlook® SP2 and Exchange Server 2003 SP2 handle meetings. The new design addresses disappearing meeting scenarios that were introduced by Outlook 2003 in cached mode. For detailed information, see the Microsoft Knowledge Base article 899919, "Developer information about the calendar changes in Outlook 2003 Service Pack 2, Exchange Server 2003 Service Pack 2 and later versions."

Upgrading to Exchange Server 2003 SP2

The following are important items to consider before you install SP2. Please read carefully and take the appropriate actions.

Make sure that, if you are installing SP2 for Exchange Server 2003, you are running either of the following operating systems: Microsoft Windows Server™ 2003 or Microsoft Windows® 2000 Server Service Pack 4 (SP4).
If you are running Windows Server 2003, it is recommended that you install Windows Server 2003 Service Pack 1 (SP1). Although SP1 is not required to use the new message hygiene features, it is required to allow for Simple Mail Transfer Protocol (SMTP) session tarpitting. SMTP session tarpitting involves slowing down Exchange Server responses to invalid SMTP commands or non-existent recipients on the RCPT TO: commands to counteract directory harvesting attacks (DHAs). For more information about SMTP session tarpitting, see the Microsoft Knowledge Base article 842851, "SMTP tar pit feature for Microsoft Windows Server 2003."
For information about an update rollup to Windows Server 2000 SP4, see "Update Rollup 1 for Windows 2000 SP4 and known issues." For more system requirements for Exchange Server 2003 (pre-SP1 and SP2), see System Requirements for Exchange Server 2003.
Each installed copy of Exchange Server must be licensed separately. This means, for example, if you are setting up two virtual computers (within Virtual Server 2005 or other virtual machine software), to run two instances of Exchange Server 2003, you will need two Exchange Server 2003 licenses. Additionally, for information about the latest support policy for Exchange Server running on a virtual machine, see the Microsoft Knowledge Base article 897615, "Support policy for Microsoft software running in non-Microsoft hardware virtualization software."
Before you apply Exchange Server 2003 SP2 to a new Exchange front-end server, make sure that you apply the required service packs and hotfixes to bring both the front-end and back-end servers to the same update level. For example, if you still have a back-end server that is running SP1, you must apply SP1 to your front-end server before you apply SP2.

For more information about this issue, see Microsoft Knowledge Base article 910119, "Users receive a "Loading" message when they use OWA to access their mailbox after they apply a hotfix or a service pack to Exchange Server 2003" at .
The upgrade to Exchange Server 2003 SP2 overwrites the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeWEB\OWA\ Level 1File Types and Level2FilesTypes registry entries. It you have customized these registry entries, you will have to re-apply the changes after the SP2 upgrade is completed.

Because Intelligent Message Filter is included in Exchange Server 2003 SP2, the installation of Exchange Server 2003 SP2 must create a new object within Active Directory® directory service as follows:

Cn=UCE Content Filter,cn=Message Delivery,cn=Global Settings,cn=<ORG NAME>cn=Microsoft Exchange,cn=Services,cn=configuration,dc=<root domain>

The account that you log on with to run the Exchange Server 2003 SP2 install, must have elevated rights to create this object — either Exchange Full Administrator or Exchange Administrator role at the organization level. The first time that you try to upgrade to a released or SP1 version of Exchange Server 2003, your permissions will be checked and a warning displayed if you do not have the correct rights level.

After the first upgrade is completed successfully, the system checks for the object and allows you to proceed with a more restricted permission set, such as Exchange Administrator role at the administrative group or higher.

For information about how to deploy Exchange Server 2003, see the Exchange Server 2003 Deployment Guide.

Required Hotfix

Make sure that you install the following hotfix before you install Exchange Server 2003 SP2.

Ensure that Hotfix 898060, "Installing security update MS05-019 or Windows Server 2003 Service Pack 1 may cause network connectivity between clients and servers to fail" has been installed on your system. You can determine whether this hotfix is installed by running the Microsoft Exchange Server Best Practices Analyzer Tool, which checks for the hotfix being installed, and then reviewing the output log. If you do not run the Exchange Server Best Practices Analyzer, you must manually verify that Hotfix 898060 is installed on your system. If this hotfix is not on your system, you must install it now. This hotfix is applicable only to Windows Server 2003 customers who applied security update MS05019 or Windows Server 2003 SP1.

Required Sender-ID Hotfix

Make sure that you install the following hotfix before you install Sender-ID in your environment.

Before you enable Sender ID on Exchange 2003 SP2 server, make sure that you apply the Windows Server 2003 hotfix that is referenced in Microsoft Knowledge Base article 905214 "Windows Server 2003 may stop responding when you enable Sender ID filtering on an SMTP virtual server in Exchange Server 2003 SP2." Windows 2000 Server is in extended support mode only. Please contact your Microsoft account representative for information about obtaining the hotfix for Windows 2000 Server. For more information about this issue in Windows 2000 Server, see the Microsoft Knowledge Base article 909426, "Windows 2000 Server may stop responding when you enable the "Sender ID Filtering" setting on an SMTP virtual server in Exchange Server 2003 SP2."

Updates to Exchange Server 2003 SP2 Online Help

The Exchange Server 2003 online Help has been updated for Exchange Server 2003 SP2 as follows:

  • ExAdmin.CHM   Contains the "How-To" topics that display in Exchange System Manager (ESM).

  • ExHelp.CHM   Contains the context-sensitive Help topic for most of ESM dialog boxes.

  • ContentFilterHELP.CHM   Contains the context-sensitive Help file for Sender ID and intelligent message filtering.

  • ExSMTPui.CHM   Contains the "How-To" topics for supporting SMTP in an Exchange Server environment.

Make a Full Backup of Server Before and After Upgrades

Immediately before and after you upgrade your servers to Exchange Server 2003 SP2, it is recommended that you make a full backup of the servers (system state, Exchange databases, and file system), so that you are assured of a valid backup if you require one. This is a best practice that should be followed for all kinds of system changes.

After an Exchange Server service pack has been installed, it cannot be uninstalled. If you must revert to the version of Exchange Server that was running before the service pack was installed, you will have to remove Exchange Server from the computer, reinstall Exchange Server, and then restore the Exchange databases from a backup. For more information about applying service packs, see the Microsoft Knowledge Base article 328839, "How to apply Exchange service packs and hotfixes."

For more information about performing an Exchange Server disaster recovery, see Exchange 2003 Disaster Recovery Operations.

Upgrade All Load-Balanced Front-End Servers to SP2 Together

If you run front-end servers in a load-balanced configuration, be sure that you upgrade all front-end servers to SP2 at the same time. To do this, take all your front-end servers offline, upgrade each server, and then bring the servers back online. When you upgrade all front-end servers to SP2 at the same time, the chances of having errors in mobile clients is minimized. If some of the front-end servers are running SP2 but others are running the original release version of Exchange Server 2003, mobile clients might receive synchronization key errors. These errors result when client requests are redirected from SP2 to released front-end servers. These errors will stop after all load-balanced front-end servers are running SP2.

Upgrade All Exchange Server 2003 Front-End Servers before Upgrading Exchange Server 2003 Back-End Servers

If your Exchange Server 2003 organization uses a front-end and back-end architecture, you must upgrade your front-end servers before you upgrade your back-end servers.

What's New in Exchange Server 2003 SP2

There are several new features in Exchange Server 2003 Service Pack 2 (SP2) that support mobility, anti-spam initiatives, and mailboxes (public folders and database size restrictions). The following is information about the new features in SP2.

Mobility Enhancements

There are some important mobility enhancements for both the mobile device user, and the mobility administrator.

To use the mobility enhancements in SP2, you need a mobile device that has Windows Mobile™ 5.0 and the Messaging and Security Feature Pack for Windows Mobile 5.0 installed. The server-based synchronization of Tasks is the only feature that does not require the feature pack.
  • Direct push is a new Exchange technology that maintains an open connection between the mobile device and the server. When new items arrive, they are automatically "pushed down" to the device.

  • Remote wipe is a new feature that enables administrators to delete sensitive data from a lost or stolen mobile device. The administrator receives an acknowledgement that the device has been wiped after the task has been completed.

  • Global address list (GAL) lookup enables users to receive contact information for users in the global address list from a mobile device. This feature helps users search for a person quickly, based on name, company, and so on.

  • Policy provisioning allows administrators to make supported policies, such as device passwords, more secure by enforcing them in one of two modes:

    • Allowing only devices that have policies to synchronize (Windows Mobile 5.0 and Microsoft Feature Pack)

    • Allowing all devices, including older devices, to synchronize

  • Support for certificate-based authentication

  • Use of S/MIME to sign and encrypt mail

  • Server-based synchronization of Tasks

Improvements in Message Hygiene

The anti-spam improvements are driven by the release of the integrated Version 2 of the Intelligent Message Filter, and Sender ID, which is an industry-standard framework. Following are the highlights of the initiatives around anti-spam.

  • Intelligent message filtering in the form of updated SmartScreen™ Technology (Microsoft research technology that is used to detect spam messages in Hotmail®, Exchange Server, and Office Outlook). This is achieved through Version 2 of the Microsoft Exchange Intelligent Message Filter that contains significant improvements in the anti-spam area for SP2.

    You must uninstall Intelligent Message Filter v1 before you can install Exchange Server 2003 SP2, which includes Intelligent Message Filter v2.
  • Sender ID filtering for addressing the problem of domain spoofing and phishing schemes by verifying the domain name from which the e-mail is sent.   Sender ID has been integrated with the other anti-spam features that can be enabled on the General tab of the SMTP Virtual Server properties dialog box. This extends Exchange System Manager (ESM) and provides a single point for anti-spam features. Also, Sender ID can be implemented on the Exchange server that is located behind the perimeter, and work with any gateway server, for example, Sendmail.

  • Anti-phishing.   The spam confidence level (SCL) score will be changed, based on the current Exchange store and gateway thresholds as configured by the administrator. Anti-phishing is incorporated in the SmartScreen functionality.

Increase in Database Size Limit

For the Exchange Server 2003 Standard Edition, the hard-coded licensing database size limit has been increased from 16 GB to 75 GB. The administrator will be able to set a protective database size limit (prevent unintentional database size growth). The default value will be 18 GB in SP2 for Standard Edition and the default of 18 GB can be overwritten by editing the "Database Size Limit in GB" registry key.

The database size calculation will be that of the logical database size — empty space is not counted. Limit checks will be performed regularly and controlled by the store process, not by Jet. Intervals for checking will be defined in the local registry and defaults can be overwritten by editing the registry. If there are no registry settings, the default time of 24 hours is used.

There will be an early warning threshold so that warnings will arrive at set intervals. Additionally, there will be better feedback to administrators when the database size limit is reached. Administrators will be able to manually mount databases in Exchange System Manager (ESM).

Improvements in Public Folder Management

Because of several enhancements, the public folders are now more manageable. The manageability includes minimizing the effect of replication storms. A replication storm occurs when too much data is replicated through the network, typically because of a change that affects many items or folders.

  • Log public folder deletions   The logging public folder deletions feature enables the administrator to track who has deleted public folders. Specifically, every time that a public folder is deleted, Exchange Server creates an event (viewable in Event Viewer) that includes information such as the name of the deleted public folder, the time that the public folder was deleted, and the name of the user who deleted the public folder.

  • Stop and resume public folder content replication   Within Exchange System Manager, administrators will be able to right-click the Organization object in Exchange System Manager, in the hierarchy, to stop public folder content replication, do any fixing (reconfiguring) required, and then resume the replication. Being able to easily stop all public folder replication helps alleviate the consequences of a public folder replication storm.

  • Synchronize public folder hierarchy   Synchronize the hierarchy (folders not content) to force hierarchy replication and bring a server's hierarchy in sync with the rest of the servers in the organization. The task will be accomplished in the ESM and is made available by the administrator right-clicking the appropriate top-level hierarchy and then selecting Synchronize Hierarchy. Currently, there is only a Resend changes selection, which just resends previously broadcasted data.

  • Propagate access control list (ACL) changes down the public folder hierarchy   Lets administrators better manage client permissions in public folders in a folder subtree. Through the ESM, an administrator can set permissions for a user or group and propagate the change to all folders in a public folder subtree. The subtasks are: add users, remove users, replace users, and modify a user's permissions. There is a new selection named Manage Settings that, when clicked, displays the Manage Public Folders Settings Wizard.

  • Propagate replica list changes down the public hierarchy   Enables administrators to add replica servers, remove replica servers, or substitute a replica server that has another server. You can do this for a selected public folder and all the folders under it. This change should address the issue of replication storms caused by unintended replica changes. Again, the new Manage Public Folders Settings Wizard will be invoked to step the administrator through the public folder management tasks.

Additionally, messaging is improved when you uninstall or remove a server and delete a public store (MDB). These tasks are currently performed by using the Exchange Installation Wizard or ESM Remove Server, or the Delete a Public Store task in ESM. To make these tasks less risky, there will be a new feature that will prevent the removal of a public store unless it has no date in it. There are also improvements to two dialog boxes to more intuitively help administrators in their tasks.

Improvements in Offline Address Book Performance

A new version of the offline address book (OAB 4.0) has been introduced in Exchange Server 2003 SP2.

You must have Microsoft Office Outlook 2003 Service Pack 2 (SP2) installed to use this new offline address book format.

In cached mode, with the improvements, there will be fewer situations that could cause a company-wide, full OAB download.

Specific features of OAB 4.0 include the following:

  • Significantly reduce the size of the OAB.

  • Differential OAB update files use a generic, binary compression technology (BinPatch).

  • You now can have customizable properties and indexes.

  • OAB indexing will be based on the locale setting (language and country) of the client. This enables users on the same server (with different local settings) to correctly view the OAB, sorted based on their locale setting and not the servers.

  • Improved diagnostic logging.

Changes to how DSProxy Referral Mechanism Works

In Exchange Server 2003 SP2, the DSProxy referral process now tries to provide an Outlook client that has a global catalog that belongs to the same domain as the mailbox-enabled user by using a new algorithm. The new algorithm examines all global catalog servers that are directly connected to the Exchange server Active Directory site and provides the client with a global catalog that resides in the same domain as the mail recipient, if possible. This means that Exchange can now refer clients to out-of-site global catalog servers if there are no mailbox home domain global catalogs available in the Exchange server Active Directory site. For detailed information about DSProxy in SP2, see Microsoft Exchange Server 2003 Technical Reference Guide.

Enabling or Disabling MAPI Access per User

Exchange Server 2003 SP2 adds functionality to enable administrators to completely turn off MAPI access for a given user, or to grant access to a user whose Microsoft Office Outlook is configured for cached mode, but to deny access otherwise. This functionality is valuable to providers of hosting services who want, as an example, their end users to connect to Exchange Server with Outlook Web Access, but not with Outlook.

The ProtocolSettings attribute is cached in the MBICache and in DSAccess, and these caches may delay the time that is required for a change in the ProtocolSettings to become effective.
Enabling this attribute may cause third-party applications not to work.

The ProtocolSettings attribute on the user object in Active Directory stores client access settings. This attribute is a multiple-valued string property, where each string applies to a different protocol. MAPI access can be restricted by manually adding the following string to the ProtocolSettings attribute using a tool such as ADSIEdit:


The eight § separators define exactly nine fields. The fields have the following meanings.


Specifies that this string contains settings that apply to the MAPI protocol


0 to block all MAPI access; 1 to determine MAPI access based on Bool2


0 for no effect; 1 to deny access to non-cached mode Outlook clients

Remaining 6 fields

Currently not used

If there is no MAPI string in ProtocolSettings, all MAPI clients are allowed.

If the MAPI string does not have the eight separators and conforms to the expected data types, the behavior is undefined.

The access restrictions specified earlier do not apply in the following cases:

  • The client is an Exchange component (for example, the mailbox moves work correctly regardless of the MAPI access settings for the mailboxes).

  • The client is doing delegate access to the mailbox.

How to Use the New Features

For information about how to use the new user interfaces and tasks, see the Exchange Server 2003 SP2 online Help. To download the Help, visit

Microsoft Exchange Intelligent Message Filter Version 2

Microsoft Exchange Intelligent Message Filter is integrated with the Sender ID feature in the Exchange Server 2003 Service Pack 2 (SP2). Note that, for Exchange Server 2003 SP2, Intelligent Message Filter is built into the product and is considered to be version 2. Version 1 of the Intelligent Message Filter was a stand-alone tool.

Intelligent Message Filter helps companies reduce the amount of unsolicited commercial e-mail (UCE), also know as spam, that can be received by users.

Installation Tips

If Intelligent Message Filter version 1 is detected as being on the target server computer when you start the upgrade to SP2, a flag is raised and you must uninstall version 1. After the SP2 upgrade, Intelligent Message Filter version 2 is automatically installed on the server. However, the administrator still must enable version 2 on the Virtual Server Instance (VSI).

Do not install Intelligent Message Filter version 1 after the upgrade to Exchange Server 2003 SP2. Version 2 has been installed automatically with SP2.

During the upgrade to Exchange Server 2003 SP2, the server will not be available. When the server becomes available again, the administrator must enable Intelligent Message Filter immediately. Or, the server must be taken offline and Intelligent Message Filter enabled, if more time is required. Otherwise the server will be subject to spam attacks.

The Intelligent Message Filter is not cluster-aware and cannot be enabled on an Exchange server that is a member of a server cluster. However, it can run on front-end servers and Exchange Simple Mail Transfer Protocol (SMTP) gateways that are members of a network load-balanced cluster. It can also run on non-clustered Exchange Server 2003 computers.

Intelligent Message Filter Updates

Included with Exchange Server 2003 SP2 is an update process for the Intelligent Message Filter version 2. You can now visit Try Microsoft Update today to obtain the latest update to the filter. New updates have been published two times a month on a first and third Wednesday. For complete information about schedule and availability, enabling updates, and much more, see the Microsoft Exchange Server Intelligent Message Filter v2 Operations Guide at

Custom Weighting Feature

The custom weighting feature in Intelligent Message Filter for SP2 lets administrators customize the behavior of Intelligent Message Filter, based on phrases that are in the body of an e-mail message, the subject line, or both.

How to Use the Custom Weighting File

There is no user interface associated with the custom weighting feature. Custom weighting is made available in the form of an XML configuration file that is read by Intelligent Message Filter upon initialization, and then reloaded any time the file changes. If the XML configuration file is not present when Intelligent Message Filter is started, you must restart the SMTP service. The custom weighting file, MSExchange.UceContentFilter.xml, should be located in the same directory as the MSExchange.UceContentFilter.dll and .dat files.

Sample XML File

The following sample XML file and the table of values demonstrate how this feature can be used, and how the behavior of Intelligent Message Filter can be customized.

Different document editors may save the XML file in different encoding formats. To make sure that the custom weighting file functions correctly, you must save the file in Unicode format.
<?xml version="1.0" encoding="UTF-16"?>
<CustomWeightEntries xmlns="">
     <CustomWeightEntry Type="BODY" Change="1" Text="foo1"/>
     <CustomWeightEntry Type="BODY" Change="-1" Text="foo2"/>
     <CustomWeightEntry Type="BODY" Change="5" Text="Special offer"/>
     <CustomWeightEntry Type="BODY" Change="-9" Text="Verlängertes Angebot"/>
     <CustomWeightEntry Type="SUBJECT" Change="MIN" Text="特別提供"/>
     <CustomWeightEntry Type="BOTH" Change="MAX" Text="Offre spéciale"/>

Table 1   Custom Weight values

Value Description

Type= BODY

Searches for a match in the displayed body of a message.


Searches for a match in the displayed subject of a message.

Type= BOTH

Searches for a match in both the subject and body of a message.


Defines what the effect of a match will be on the spam confidence level (SCL) score of a matched message.

Change can be any integer value. If the phrase is matched, the change will be added to the original SCL value. SCL values will be normalized to a 0 to 9 range (if they exceed that range because of custom weights).

Change can also use the MIN or MAX keywords. Any time a phrase with the MIN keyword is matched, the message is given an SCL of 0 regardless of any other weights. Any time a phrase with the MAX keyword is matched, the message is given an SCL of 9 regardless of any other weights. Any time there is both MIN and MAX matches for one message, the message is given an SCL of 0.


Custom weighting can accept any Unicode phrase up to 1,000 characters.


When the schema of the custom weighting file is broken or malformed, it will cause the filter of Intelligent Message Filter to fail loading.

If the custom weighting file does not exist, Intelligent Message Filter will continue to load and/or behave normally, without the use of the custom weighting feature.

After first creating a custom weighting file, the SMTP service must be restarted to pick up the file. When the filter has been loaded with a valid custom weighting file, any changes that you made to the file are immediately picked up.

Design Changes and Fixes for SP2

The following is a brief description of the design changes and fixes for Exchange Server 2003 SP2. This list includes the new events and error messages created for SP2.

Component/Area Affected Description


Compression is enabled for the traffic between the mobile device and the Exchange ActiveSync® virtual server. The administrator can disable the functionality.


Improvements to the user interface let users configure Sender ID and junk e-mail filtering.


The issue of having a cluster physical node name of exactly 15 characters that prevents the metabase update service from starting has been fixed.


Can now pause the SMTP service on a clustered server to take care of backlogged queues.


The DSAccess API has been changed to return a list of all servers in the topology with their home domain DNS names. This causes the DSProxy RFR service to return global catalogs only from the source directory of the mailbox of the client.

Offline Address Book

OAB version 4 has been implemented to help avoid company-wide, full OAB downloads

Database engine

Fields were added to the database header to track the total number of Error Code Correction (ECC) fix-ups and the total number of repairs a database undergoes.

DSAccess (LDAP logging)

A new event has been created for LDAP_REFERRAL. Level for this event is set to Max.

Web Client

Spelling checkers for Brazilian Portuguese and Iberian Portuguese have been added.

Web Client

The Logoff command has been fixed to include redirect URL information.


IMAP4 services no longer show the Inbox, Sent Items, Deleted Items, and Draft folders when they are marked as hidden.

Exchange System Manager

Message about the Exchange store not mounting has been improved by directing users to examine the Application log for events related to the error.

Exchange ActiveSync

Exchange ActiveSync has been enabled to use any SMTP address to access the mailbox.

Exchange ActiveSync

Performance counters implemented for IP-based up-to-date.

Exchange ActiveSync

An error message is added to the event log when the maximum number of Exchange ActiveSync users has been reached.

Exchange ActiveSync

A message is added to the Event log that alerts administrators about common server misconfigurations.

Collaboration Data Objects (CDO)

The accepting a meeting request or update behavior has been changed to match that of Outlook.


Administrators can now enable or disable MAPI access on a per-user basis.


The Manage Settings Wizard has had enhancements that enable administrators to make incremental changes to MAPI client permissions.


New wizard lets administrators add replica servers, remove replica servers, or replace a single replica server with another one. Should reduce incidence of replication storms.


The Virus Scanning API (VSAPI) version 2.5 now deletes infected messages when Intelligent Message Filter is invoked. For more information, see the Microsoft Knowledge Base article 883522, "E-mail messages that contain a virus remain in the SMTP local delivery queue after you configure Intelligent Message Filter in Exchange Server 2003."


Increase in mailbox storage size limits to 75 GB for Exchange Server 2003 Standard Edition.


Content conversion of inbound mail is subject to the 16-KB soft limit on named property creation.


A selection has been added in the ESM user interface to enable the administrator to stop and then to resume content replication.


The epoxy leak in envelope journaling has been fixed. For more information, see the Microsoft Knowledge Base article 885281, "You receive an "Out of virtual memory" error message after you enable the Envelope Journaling feature in Exchange Server 2003 SP1."


For the new Sender ID feature, a new IP Parsing Algorithm has been implemented to ensure that the new feature works correctly. The IP Parsing Algorithm has been adopted for connection filtering so that filtering can work behind the perimeter.


For Sender ID, Performance Monitor counters have been implemented. During Setup, these new counters will be registered. (Registry entries are created before the Performance Monitor counters are loaded.)

System Attendant

Memory leaks have been fixed in Mad.exe.

Management Pack

The ScriptContext.TargetFQDNComputer has been removed. The custom GetFQDN function should be used instead.

Error message

A new message was added for Error -551.

Error message

Message for Error -1018 has been improved with the addition of logical page numbers.

Error message

Change to Error 1216 to indicate solution to problem, instead of only advising to call Microsoft Product Support Services.

Eseutil (2 changes)

A feature was added to Eseutil to insert artificial 1-second pauses periodically during the physical consistency check to address performance problems when running consistency checks of VSS backups on a production server.

In Eseutil, option /K, a fix has been applied so that Eseutil counts the 1-bit error correction code (ECC) fixed pages.

Known Issues

Mobility   Administrators should be a member of the account operators group in order to add or remove users from the policy exemption list.

Mobility   For the new Direct Push technology to work optimally, the firewall timeouts that handle the connections to the Exchange server where Direct Push is enabled, must be increased. The minimum recommended time-out is 15 minutes. At Microsoft, we use 30 minutes.

Microsoft Exchange Intelligent Message Filter   Exchange Server 2003 SP2 does not create the registry key named ContentFilter under HKEY_LOCAL_MACHINE\Software\Microsoft\Exchange during an upgrade from Exchange Server 2003 or Exchange Server 2003 SP1, where Intelligent Message Filter version 1 was not previously installed. Therefore, to obtain an extended functionality (for example, change the Archive directory), you must manually create the HKEY_LOCAL_MACHINE\Software\Microsoft\Exchange\ContentFilter key and restart the SMTP service.

After the restart of SMTP, all the values created under this key are automatically picked up and no additional restarts of services are required. If you are upgrading the computer where Intelligent Message Filter version 1 was previously installed, no action is required because the registry key is preserved during the upgrade.

Microsoft Exchange Intelligent Message Filter   There is an error in the user interface in the Global Settings for Intelligent Message Filtering. Under Store Junk E-mail Configuration, the selection that reads Move messages with an SCL rating greater than or equal to, should only indicate "greater than."

Uuencode attachments   After you install Exchange Server 2003 SP2, uuencode (Unix to Unix encoding) attachments that are sent from non-Exchange servers are displayed as garbled text in the body of the e-mail message. For the cause, resolution, and more information, refer to the Microsoft Knowledge Base article 912433, "Uuencode attachments that are sent from non-Exchange servers are displayed as garbled text in the body of the e-mail message," at

Updated Documentation

The following sections have been updated in the What's New in Exchange Server 2003.

  • Administration Features in Exchange Server 2003

    • New in SP2: Enabling or Disabling MAPI Access for a Specific User

    • New in SP2: Enabling Direct Push Technology

    • New in SP2: Managing Security Settings for Mobile Clients

    • New in SP2: Remote Wiping of Mobile Devices

    • New in SP2: Global Address List Search for Mobile Clients

    • New in SP2: Certificate-Based Authentication and S/MIME on Mobile Devices

    • New in SP2: Tracking Public Folder Deletions

    • New in SP2: Manually Stopping and Resuming Replication

    • New in SP2: Synchronizing the Public Folder Hierarchy

    • New in SP2: Using the Manage Public Folders Settings Wizard

    • New in SP2: Moving Public Folder Content to a Different Server

  • Performance and Scalability Features of Exchange Server 2003

    • New in SP2: Improved Offline Address Book Performance

  • Transport and Message Flow Features of Exchange Server 2003

    • New in SP2: Step 3: Specifying the Servers to Exclude from Connection Filtering

    • New in SP2: Sender ID Filtering

    • New in SP2: Intelligent Message Filtering

    • Updated in SP2: Understanding How Enabled Filters Are Applied

  • Storage Features of Exchange Server 2003

    • New in SP2: Database Size Limit Configuration and Management

  • Schema Changes in Exchange Server 2003


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.

© 2005-2007 Microsoft Corporation. All rights reserved.

Microsoft, Active Directory, ActiveSync, Hotmail, Outlook, SmartScreen, Windows, and Windows Server 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.