The release notes may have been updated since Microsoft® Exchange Server 2003 Service Pack 1 (SP1) shipped. For the most current information, see the version of this document posted on the Web at http://go.microsoft.com/fwlink/?LinkId=21277.
The most current version of the Exchange Server 2003 RTM Release Notes are also available on the Web at http://go.microsoft.com/fwlink/?LinkId=21277.
© 2004 Microsoft Corporation. All rights reserved.
About This Document |
Back to Top |
The release notes list important information you should know prior to deploying and using Exchange 2003, including known issues.
For detailed technical documentation about Exchange 2003, see the Exchange 2003 Technical Documentation Library at http://go.microsoft.com/fwlink/?LinkId=21277.
Upgrading to Exchange 2003 SP1 |
Back to Top |
Immediately before and after you upgrade your servers to Exchange 2003 SP1, you should make a full backup of your servers. Making this backup will ensure that you have a valid backup of your servers should you require one. Making a full backup of servers is considered a best practice for all upgrades.
If you are running front-end servers in a load-balanced configuration, upgrade all front-end servers to SP1 together. Upgrading all front-end servers simultaneously minimizes errors for mobile clients. If some of the front-end servers are running SP1 but others are running the RTM version of Exchange 2003, mobile clients might receive sync key errors. These errors result when client requests are redirected from SP1 to RTM front-end servers.
Because it is unlikely that all front-end servers can be simultaneously upgraded to SP1, you should expect a short period of time during which mobile users will receive sync key errors. These errors will stop after all load-balanced front-end servers are running SP1.
The Exchange 2003 Help has been updated for Exchange 2003 SP1. To download and install these Help updates, go to the Exchange Technical Documentation Library at http://go.microsoft.com/fwlink/?LinkId=21277 and follow the link for Exchange 2003 SP1 Online Help.
Site Consolidation Tools for Exchange Mixed Mode |
Back to Top |
If you are running Exchange in mixed mode (meaning that coexistence is established between Microsoft Exchange Server 5.5 and Exchange 2000 Server or Exchange 2003), several new features and tools in Exchange 2003 SP1 help you migrate data, distribution lists, and custom recipients as part of a site consolidation effort.
Before you begin a site consolidation process, you should familiarize yourself with the recommendations and known issues documented in Planning an Exchange Server 2003 Messaging System at http://go.microsoft.com/fwlink/?LinkId=21766 ("Planning for Site Consolidation" chapter) and the Exchange Server 2003 Deployment Guide at http://go.microsoft.com/fwlink/?LinkId=21768 ("Consolidating Sites in Exchange 2003" chapter).
Known Issues for Exchange 2003 SP1 |
Back to Top |
This section describes known issues for Exchange 2003 SP1. These issues may impede your ability to successfully deploy and use Exchange. You should familiarize yourself with all of the known issues listed here prior to installing the software.
Known issues are listed according to Exchange component within the following sections:
Administration |
Back to Top |
When Exchange 2003 SP1 is running on Microsoft Windows® 2000 Server SP4 (or later) or Microsoft Windows ServerTM 2003, Exchange System Manager (Exchange Sytem Manager.msc) creates objects in the computer's global namespace. As a result, any administrator who is using Exchange System Manager must have the Create Global Objects (SE_CREATE_GLOBAL_NAME) right on the server. By default, local administrator accounts have this right. However, if the user's account has Exchange View Only Administrator rights but does not have local administrator rights on the computer, the user receives an error. This situation mainly occurs when a user uses Terminal Services to access Exchange System Manager on another server for which the user is not a local administrator.
To avoid this error, you can either add the user to the local administrators group, or you can grant the Create Global Objects right to the user. To grant this right, log on to the local computer using an account that is a member of the Administrators group, and then grant this right to the user account in Local Security Settings.
The Create Global Objects right does not exist in Windows 2000 SP3 (or earlier) or Windows XP operating systems. For these operating systems, no action is necessary.
When you are running Exchange 2003 SP1 on Windows Server 2003 with more than 1 GB of RAM, it is recommended that you set the SystemPages registry key to zero. This recommendation contrasts with the recommendation for Windows 2000 Server, which is to set SystemPages to a value between 24000 and 31000.
The recommended memory settings for Exchange 2003 SP1 on Windows Server 2003 with more than 1 GB of RAM are as follows:
If you set SystemPages to the Windows 2000 Server recommended value of between 24000 and 31000, an Event 9665 will appear in the event log.
Clients |
Back to Top |
After upgrading a back-end server to Exchange 2003 SP1, the attachment block list will include files with the extension, ".xml" or files with MIME content types of "application/xml" and "text/xml."
In SP1, changes were made to the way in which MHTML attachments are displayed in Outlook Web Access. As a result, to save an MHTML attachment as an .MHT file in Microsoft Internet Explorer, you must open the attachment, click File, click Save As, and then select Web Archive, single file (*.mht).
An optional feature in SP1 allows users to enter their SMTP addresses in the URL to explicitly log onto Outlook Web Access. For example, a user can enter the following URL to access his or her mailbox that has user@example.com as either the primary or secondary proxy address:
This option is enabled by default. Note that the SMTP address may not be the same as the users user principal name (UPN). If the user attempts to log on explicitly by using the UPN, but the UPN does not match the users SMTP address, the user will be asked to authenticate.
If your users' UPN addresses are the same as the SMTP proxy addresses, you should be aware of the following potential privacy issues:
If your users are using either the Arabic or Hebrew Language Packs for Windows, Internet Explorer 6.0 or greater will provide the best experience for Outlook Web Access. Additionally, these users will only be able to access the premium version of Outlook Web Access from the logon page.
Because of a fix to GNU zip (gzip) compression in Exchange 2003 SP1, a full directory service to metabase replication is required after you install SP1. In environments where there are large numbers of recipient policies or HTTP virtual servers and virtual directories, the directory service to metabase replication could take a long time; during this time, gzip cannot be used.
Mobility |
Back to Top |
In Exchange 2003 SP1, Exchange ActiveSync requires Windows 2000 Server SP4 or later because of new dependencies on WinHTTP. Exchange SP1 Setup does not include a prerequisite check to block installation on servers running Windows 2000 Server SP3 or earlier versions. Therefore, you will be able to install Exchange SP1 on these servers, but Exchange ActiveSync will not work; all sync requests will fail and users' devices will display "HTTP 500" errors. Before you install Exchange 2003 SP1, ensure that servers running Windows 2000 are also running SP4 or later, and that the latest updates are installed.
If some of the front-end servers are running SP1 but others are running the RTM version of Exchange 2003, mobile clients may receive sync key errors. These errors result when client requests are redirected from SP1 to RTM front-end servers.
To minimize errors for mobile clients, if you are running front-end servers in a load-balanced configuration, upgrade all front-end servers to SP1 together. However, because it is unlikely that all servers can be simultaneously upgraded to SP1, you should expect a short period of time during which mobile users will receive sync key errors. These errors will stop after all load-balanced front-end servers are running SP1
If you install Exchange 2003 SP1 on a server that is running the .NET Framework 1.1 SP1 and Device Update 4.0 for ASP.NET Mobile Controls, Outlook Mobile Access will stop functioning. This situation occurs because installing Exchange 2003 SP1 removes Device Update 3.0 even though Device Update 4.0 is already installed. With Device Update 3.0 removed, Outlook Mobile Access cannot function properly. To fix this problem, manually uninstall Device Update 4.0 and then reinstall Device Update 4.0.
If you disable Outlook Web Access for users, you also prevent users from being able to use Outlook Mobile Access to access their information.
Users cannot use Outlook Mobile Access to send messages to Contact Distribution Lists.
Tools |
Back to Top |
The XDR-Fixup tool fixes Exchange attributes in Active Directory after you use the Windows Server 2003 domain rename tools. However, XDR-Fixup does not update search filters you may have created to define the membership of a recipient policy, address list, or query-based distribution group. Search filters will continue to reference the old domain name. To work around this issue, after you rename a domain, manually re-create the search filters for recipient policies, query-based distribution groups, and address lists.
Copyright |
Back to Top |
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.
© 2004 Microsoft Corporation. All rights reserved.
Microsoft, Outlook, 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.