Release Notes for Exchange Server 2010 RTM

Exchange 2010 adds several new features to the Exchange family. For detailed information about these new features, see What's New in Exchange Server 2010.

Consider the following when you deploy Exchange 2010:

You can only install Exchange 2010 on computers running Windows Server 2008 Service Pack 2 (SP2) and Windows Server 2008 R2.
Although it isn't a recommended configuration, single-label DNS domain names are now supported for use with Exchange 2010.
If you're running the Beta release of Exchange 2010, you must uninstall the Beta before you install the release to manufacturing (RTM) version of Exchange 2010.

For detailed information about the requirements and steps for installing Exchange 2010, see the following topics:

This section outlines the known issues related to the following Exchange 2010 components:

Client Access
Edge Transport and Hub Transport
Mailbox
Unified Messaging
Exchange Management Shell and Exchange Management Console
High Availability

Known Issues with Client Access

This section covers the known issues related to the Client Access server role.

Outlook Client Configuration

When you upgrade your organization to Exchange 2010, your clients running Outlook 2007 or later versions will automatically be compatible with the change to RPC Client Access, since they support RPC encryption by default. Outlook 2003 doesn’t use RPC encryption, however, and RPC Client Access requires it by default. If you haven't turned off RPC encryption, your users will need to configure Outlook 2003 for RPC encryption or you'll need to use a Group Policy to force Outlook 2003 to use RPC encryption.

Symptoms of this problem include the following error messages:

Cannot start Microsoft Office Outlook. Unable to open the Office window. The set of folders could not be opened.
Unable to open your default e-mail folders. The information store could not be opened.

If your users are using Cached Exchange Mode, Office won't display an error, but will start in disconnected mode.

For more information about this issue, including workarounds, see Outlook Connection Issues with Exchange 2010 Mailboxes.

In addition, UDP notification support was removed from Exchange 2010. As a result, Outlook 2003 can only use polling notifications in online mode. This will result in a slight delay in updates to item status (30 seconds on average with up to a one-minute delay) when changes are made to items in a mailbox accessed by Outlook 2003. There are two workarounds for this issue:

Use Outlook 2003 in Cached Exchange Mode.
Adjust the polling interval on the Client Access server. This will impact the performance of the Client Access server.

To configure Outlook 2003 to use RPC encryption, use the following steps.

Click Tools > E-Mail Accounts > View or Change an Existing Account.
Select the account and click More Settings.
Select the Security tab.
Select Encrypt data between Microsoft Office Outlook and Microsoft Exchange Server.
Click OK.

For more information about this issue, see E-mail messages take a long time to send and receive.

Entourage Client Issues

Entourage 2008 for Mac and previous Entourage clients can't connect to Exchange 2010. These clients use WebDAV to connect to a user's Exchange mailbox. WebDAV support has been removed in Exchange 2010.

To connect to an Exchange 2010 mailbox with Entourage, you must use Entourage 2008, Web Services Edition. This is a free update to Entourage 2008.

Configuring Exchange Web Services to Manage SSL Offloading

Secure Sockets Layer (SSL) is enabled by default on Exchange Web Services virtual directories. If you want to enable SSL offloading, you must disable SSL on each Client Access server in your organization.

If you don't have an SSL offloading device and you want to maintain secure communication between client and server, SSL must be enabled on each Client Access server in your organization.

Important:
You can't use the Shell to enable or disable SSL. If you enable or disable SSL on an Exchange Web Services virtual directory, you must make the configuration change in both Internet Information Services (IIS) Manager and the Exchange Web Services web.config file.

For more information, see Understanding Exchange Web Services Virtual Directories and Enable or Disable SSL on Exchange Web Services Virtual Directories.

Exchange Mobile Phone Notifications for Daily Agenda

If a user creates an event on their calendar that has no location specified and the event was created on the mobile phone, the Daily Agenda that's supposed to be sent to the mobile phone won't be sent, and a non-delivery report (NDR) will be returned for that day's agenda. Also, if a user creates a daily event on their calendar from their mobile phone without a location specified, the daily agenda will never be sent to the user's mobile phone.

To resolve this issue, advise the user to remove the calendar entry or add a location to the entry.

Known Issues with Edge Transport and Hub Transport

This section covers the known issues related to the Edge Transport and Hub Transport server roles.

The parameter set and the examples for the Export-Message cmdlet displayed in the Shell Help are incorrect. Specifically, when you run Get-Help Export-Message -Parameter * in the Shell, the set of parameters returned include the Path parameter, which is obsolete for Exchange 2010. The corresponding examples also include the Path parameter and are invalid.

For the correct parameter set and examples, see the online version of the topic Export-Message. For more information, see Export Messages from Queues.
The code example in Import an Edge Subscription File to an Active Directory Site is incorrect. It uses the FileName parameter, which isn't valid when importing an Edge subscription file. Instead, use the following code to import an Edge subscription file:
New-EdgeSubscription -FileData ([byte[]]$(Get-Content -Path "C:\EdgeServerSubscription.xml" -Encoding Byte -ReadCount 0)) -Site "Default-First-Site"


New-EdgeSubscription -FileData ([byte[]]$(Get-Content -Path "C:\EdgeServerSubscription.xml" -Encoding Byte -ReadCount 0)) -Site "Default-First-Site"

Known Issues with Mailbox

If you have archives provisioned, you must delete them before you install Exchange 2010 RTM.

Known Issues with the Exchange Management Shell and Exchange Management Console

When you install Exchange 2010 into an existing Exchange 2007 organization, and you run commands on an Exchange 2007 server, the EMC or the Shell may return a series of errors that could cause you to take actions that may result in data loss and downtime. Specifically, the Exchange 2007 administrative tools may return errors stating that Exchange 2010 objects (including databases and several virtual directories) are corrupted. These Exchange 2010 objects are not corrupted.

Important:
You must manage Exchange 2010 objects from an Exchange 2010 server.

Errors that may be returned include:

Object <type of Exchange 2010 object> has been corrupted and it is in an inconsistent state. The following validation errors have occurred:
Object cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.
Exchange has detected an inconsistency in the Active Directory configuration for the following virtual directory(ies). This can happen if Exchange ActiveSync virtual directories were deleted in IIS Manager. Please verify that you have access to the metabase on the servers listed below. In order to fix this inconsistency, run the following command, which will remove references to these virtual directories from Active Directory:

Remove-ActiveSyncVirtualDirectory -Identity "Microsoft-Server-ActiveSync (Default Web Site)

Known Issues with High Availability Features

This section covers the known issues related to high availability features:

During an administrator-initiated switchover, it's possible that the dismount process can generate a spurious rollback error, resulting in the database copy becoming Failed and Suspended. If this happens, you can resolve the issue by resuming replication to the copy, which will return it to a Healthy state.
Due to a race condition, the database and checkpoint file could possibly become out of sync, causing the Microsoft Exchange Replication service (MSExchangeRepl.exe) to crash repeatedly on startup. If this happens, examine the Event log entries to determine which database was being processed. Locate the checkpoint file for that database and delete it. Then restart the Microsoft Exchange Replication service, which should start successfully.
Page corruptions detected during a background scan can repeatedly cause the Microsoft Exchange Information Store service (Store.exe) to crash. Specifically, store crashes in ErrJetInitStatusCallback when a page-patching callback is issued on the background maintenance thread. If this happens, correct the problem by suspending and reseeding the database copy that corresponds to the page patching event.
Under certain and rare circumstances involving the catalog index, switchovers and failovers can possibly take minutes to complete. During this time the database will remain in a mounting state. If this happens, simply wait for the database to mount.
Using the Set-MailboxDatabaseCopy cmdlet to update the activation preference for a database copy may result in a range error, causing the update to fail. If this happens, remove the affected copies and add them back. This will result in the ActivationPreference value being reset for the copy.

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. 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.

Microsoft, MS-DOS, Windows, Windows Media, Windows Mobile, Windows NT, Windows PowerShell, Windows Server, Windows Vista, Active Directory, ActiveSync, Entourage, Excel, Forefront, Internet Explorer, Outlook, PowerPoint, SharePoint, SmartScreen, Visual Basic, Xbox, Xbox 360, the Xbox sphere logo, Zune, and the Zune logo are trademarks of the Microsoft group of companies.

All other trademarks are property of their respective owners.

Thesaurus’s content based on dictionário de Sinónimos from Porto Editora, Lda.

Portions of security system based on BSAFE® and TIPEM® software from RSA Data Security, Inc.

The following components are licensed to Microsoft in object code form by Stellent Chicago Sales, Inc.:

Components – Version 8.0

Outside In ® HTML Export Version 8.0

Platforms Supported – Version 8.0:

Windows Intel (32 bit binaries)

Windows® 2000/XP/Server 2003

Windows Itanium (64 bit binaries)

Windows.NET ® Server 2003 Enterprise Edition for Itanium

Windows AMD (64 bit binaries)

Windows Server 2003, Enterprise Edition for AMD Opteron

Features Available in Exchange 2010

Installing Exchange 2010

Known Issues