Release Notes for Exchange Server 2010 |

[This is pre-release documentation and subject to change in future releases.]

Topic Last Modified: 2009-04-08

See the "Legal Notice" section later in this document for important information.

Welcome to the Beta release of Microsoft Exchange Server 2010. This document contains the following sections:

- Features available in Exchange Server 2010
- Installing Exchange Server 2010
- Known issues
- Legal notice

# Features Available in Exchange 2010

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

# Installing Exchange 2010

For detailed information about the requirements that you must meet and procedures that you must follow when you install Exchange 2010, see the following topics in the Exchange 2010 online Help:

- Exchange 2010 System Requirements
- Exchange 2010 Prerequisites
- New Installation of Exchange 2010

### Installation Overview

Consider the following when you deploy Exchange 2010:

- Exchange 2010 is only supported for installation on Windows Server 2008.
- Transition Prerequisites Every site that has an Exchange 2010 server must have at least one Windows Server 2003 Service Pack 2 global catalog server, and Active Directory within the forest must be Windows Server 2003 forest functional level.
- Install server roles in order The first server role that you should install is the Client Access server role. After you have at least one Client Access server role computer running within the Active Directory site, you can install the other server roles in the following order:
  - Hub Transport Server role
  - Unified Messaging Server role
  - Mailbox Server role
  - Edge Server role
- Single-label DNS domain names are not supported for use with Exchange 2010. For additional information about single-label DNS names, see Microsoft Knowledge Base article 300684, Information about configuring Windows for domains with single-label DNS names.
- In the RTM version of Exchange 2010, a new feature known as RPC Client Access will require your users to connect to their mailboxes through a Client Access server rather than directly though a Mailbox server. For the Exchange Server 2010 Beta, using the new RPC Client Access feature is optional. It is important that you plan whether you are going to use this feature when planning your Exchange 2010 Beta installation. For more information, see "Known Issues in Client Access" later in this document.
- Unified Messaging language packs now include two .msi files instead of one. To install the Unified Messaging language pack, do the following:
  1. Download both .msi files to the same directory.
  2. Run Setup.com /AddUMLanguagePack:<culture> /s:<path to the directory>
     For example, to install the French language pack, run Setup.com /AddUMLanguagePack:fr-FR /s:D:/LangPack

# Known Issues

Known issues are described in the following sections:

- Client Access Issues related to the Client Access server role.
- Mailbox Issues related to the Mailbox server role.
- Unified Messaging Issues related to the Unified Messaging server role.
- Exchange Management Shell and Exchange Management Console Issues related to the Shell or EMC.
- Help Documentation Issues related to the documentation.

### Known Issues in Client Access

Following are the known issues related to the Client Access server role:

RPC Client Access

- In Exchange 2010, a feature known as RPC Client Access has been added that allows your users to connect to their mailboxes through a Client Access server rather than directly though a Mailbox server. RPC Client Access improves the client experience with Exchange 2010 High Availability and enables other functionality like Calendar Repair, Copy on Write, and Archiving.
- For the Exchange 2010 Beta release, RPC Client Access will be enabled only if the Client Access server role is not installed on the same computer as the Mailbox server. This means that at least at two Exchange server computers are required to enable RPC Client Access. Support for using the RPC Client Access feature in environments where the Client Access server role and the Mailbox server role are installed on the same computer will be supported in a later release of Exchange 2010.
- To load balance RPC Client Access, there are the following additional requirements:
  - You must create a new DNS record, which should only be accessible internally, for the load balancer. If you are also using Client Access server HTTP load balancing, the DNS record for RPC Client Access should be different than the DNS entry that you are using for Client Access server HTTP load balancing.
  - Windows Network Load Balancing (NLB) or a third-party network load balancer.
- You can enable Outlook Anywhere with the RPC Client Access feature. However, if both of the following conditions apply, additional steps are required to configure it successfully.
  - RPC Client Access is being load balanced
  - Client affinity is not guaranteed
    For a description of the additional changes that are necessary if both conditions apply, see How does Outlook Anywhere work (and not work)? in the Microsoft Exchange Team Blog.
    If only one or neither of the conditions described above applies, you can configure Outlook Anywhere by following the usual configuration steps that you use. For information about Outlook Anywhere and how to deploy it, see Understanding Outlook Anywhere in the online Help.
- For information about the Set-RpcClientAccess, Set-ClientAccessArray, and other related cmdlets that you use to manage this feature, see Client Access Cmdlets in the online Help.

To ensure that all the features listed below function correctly, don't turn on the RPC Client Access feature in the Exchange 2010 Beta. If you do not deploy RPC Client Access, the RPC endpoint will remain on the Mailbox server as it did in Exchange 2007. The following is a partial list of the features that are not supported if you enable RPC Client Access in your Exchange organization.

For e-mail clients that are running any version of Outlook, you must consider that the following additional features are not supported when RPC Client Access is enabled:

- Public Folder functionality through the RPC Client Access endpoint is not supported. All public folder requests will be redirected to the server running the Mailbox server role.
- Permanent deletion of items (from the dumpster)
- Category view/sorting by categories
- Delegate access
- Cached Exchange Mode-specific: Sync progress, recovery from failed item syncs
- Online Mode-specific:
  - Copy Folder
  - Various folder views
  - Expanding/Collapsing of groups for various folder views

For e-mail clients that are running Outlook 2003, you must consider that the following additional features are not supported when RPC Client Access is enabled:

- Non-Unicode .pst file access
- Updating Out of Office settings

The RPC Client Access feature has had limited test coverage with clients running e-mail programs other than Outlook. Therefore, if you deploy this feature, consider that users who are not running Outlook may experience other limitations.

- Kerberos authentication is not supported if you have deployed RPC Client Access in a load-balanced array over HTTP.

### Known Issues in Mailbox

Following are the known issues related to the Mailbox server role:

- The following tasks must be run using the Exchange Management Shell (Local PowerShell) and not by using the Exchange Management Shell (which uses Remote PowerShell) or the Exchange Management Console (which also uses Remote PowerShell):
  - Add-DatabaseAvailabilityGroupServer
  - Start-DatabaseAvailabilityGroup
  - Stop-DatabaseAvailabilityGroup
  - Restore-DatabaseAvailabilityGroup
  - Import-Mailbox
  - Export-Mailbox
- Extensible Storage Engine (ESE) streaming backups are not supported in Exchange 2010. To perform an online backup of databases, you must use an Exchange 2010-aware VSS-based backup application.
- Import-Mailbox and the PST export function of Export-Mailbox have not been tested with Microsoft Outlook "14".
- The disaster recovery tools in the Exchange Management Console Toolbox (Database Recovery Management and Database Troubleshooter) are not functional in this release.
- A switchover operation using the Move Active Mailbox Database wizard in the Exchange Management Console will fail if the content index catalog is not healthy, even if database copy is healthy. To work around this issue, use the Move-ActiveMailboxDatabase cmdlet with the -SkipValidationChecks parameter in the Exchange Management Shell.
- Setup /m:RecoverServer cannot be used to recover a server that is a member of a database availability group (DAG). To recover a server that is a member of a DAG:
  - Remove any mailbox database copies that exist on the server being recovered by using the Remove-MailboxDatabaseCopy cmdlet.
  - Remove the server being recovered from the DAG by using the Remove-DatabaseAvailabilityGroupServer cmdlet.
  - Open a command prompt, and using the original setup media, run Setup /m:RecoverServer.
  - When the Setup recovery process has completed, add the server being recovered to the DAG by using the Add-DatabaseAvailabilityGroupServer cmdlet.
  - After the server has been added back to the database availability group by using the Add-MailboxDatabaseCopy cmdlet, you can add mailbox database copies to the server by using the Add-MailboxDatabaseCopy cmdlet.

### Known Issues in Unified Messaging

Following are the known issues related to the Unified Messaging server role:

- Auto Attendant The Exchange Management Console does not include the setting to configure the "leave a voice mail for" option.
  To configure this option, you must use the Set-UMAutoAttendant cmdlet to set up the auto attendant custom menu key mapping. For more information and examples, see "Use the Shell to configure UM auto attendant key mappings" in Configure Key Mapping Entries for UM Auto Attendants in the online Help.
- Call Answering Rules Find Me (a feature that is exposed by Call Answering Rules) does not currently work correctly for Unified Messaging-enabled users who are also Enterprise Voice-Enabled for Microsoft Office Communications Server 2007 Enterprise Edition and doesn't impact users on Office Communications Server 2007 Standard Edition.
- Receiving Incoming Faxes The ability to receive incoming faxes is disabled in the Exchange 2010 Beta. Exchange 2010 Unified Messaging servers can no longer receive an incoming fax and send it to a UM-enabled user. In the RTM version of Exchange 2010, a Unified Messaging server will send the incoming fax call to a dedicated fax server and the dedicated fax server will receive the incoming fax call, create the e-mail message for the fax, and send it to the UM-enabled user.
- Set-UMServer cmdlet Although you can successfully run the Set-UMServer cmdlet with the parameters ExternalHostFQDN and ExternalServiceFQDN, those parameters do not affect a Unified Messaging server's functionality.
- Protected Voice Mail Changing the Unified Messaging mailbox policy setting to protect authenticated voice mail has no effect on Unified Messaging mailboxes that are associated with the UM mailbox policy.
  In the EMC, there is an option to set the Protected voice mail from authenticated callers to None, Private, or All. Similarly, for the Shell cmdlet Set-UMMailboxPolicy, there is a parameter ProtectAuthenticatedVoiceMail to change this setting.
  In the Exchange 2010 Beta, changing this setting has no effect on Unified Messaging mailboxes. The Unified Messaging server will treat this setting as None. For more information about Unified Messaging mailbox policy settings, see Configure Unified Messaging Mailbox Policy Properties in the online Help.
- Voice Mail Preview Voice Mail Preview is not supported for interpersonal voice messages.
  This feature will be provided only for voice messages that are created by call answering. Voice Mail Preview will not be available for interpersonal voice messages, which are created when a UM-enabled user signs in to their mailbox using Outlook Voice Access, records a voice message, and sends it to one or more recipients.

### Known Issues in Exchange Management Shell and Exchange Management Console

After Exchange 2010 is installed in a lab that also includes Microsoft Exchange Server 2007 servers, running commands on the Exchange 2007 server, the EMC, or Shell can produce a series of errors that could cause you to take actions that could result in data loss and downtime. Specifically, the Exchange 2007 administration tools indicate that Exchange 2010 objects (including databases and several virtual directories) are corrupted. However, the Exchange 2010 objects are not corrupted.

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

The types of errors that you may receive are as follows:

- 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 the 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 in Help Documentation

- Inactive Links Some links to topics within the online Help documentation are inactive (they appear as bold text). These are usually links to topics that are not yet included in this version of the Help documentation but will be available when we release Exchange 2010.
- Exchange Management Shell quick reference The Exchange Management Shell quick reference file, accessed by using the 'quickref' command in the Shell, provides commonly used commands and explanations for each command. The quick reference file hasn't been updated for Exchange 2010 and therefore contains commands that may no longer work in Exchange 2010. The quick reference file may also contain references to features that no longer exist in Exchange 2010, such as storage groups. The quick reference file will be updated prior to the final release of Exchange 2010.

# Legal Notice

This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release. This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document. Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use or the results from the use of this document remains with the user. 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.

© 2009 Microsoft Corporation. All rights reserved.

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 either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

All other trademarks are property of their respective owners.

"Portions Copyright © 2006 World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/"

WebReady Document Viewing technology: Outside In® HTML Export © 1991-2006 Stellent Chicago, Inc. All rights reserved.

Danish speller: Copyright © Lingsoft, Inc. 2005.

Two-Level Compiler: Copyright © Xerox Corporation 1994.

All rights reserved.

Dansk stavekontroll: Copyright © Lingsoft Ab 2005.

Two-Level Compiler: Copyright © Xerox Corporation 1994.

Alle rettigheder forbeholdt.

German speller: Copyright © Lingsoft, Inc. 2005.

Two-Level Compiler: Copyright © Xerox Corporation 1994.

All rights reserved.

Deutsche Rechtschreibprüfung: Copyright © Lingsoft, Inc. 2005.

Two-Level Compiler: Copyright © Xerox Corporation 1994.

Alle Rechte vorbehalten.

Norwegian (bokmål) speller: Copyright © Lingsoft, Inc. 2005.

Norwegian works: Copyright © J. W. Cappelens Forlag A·S 1996, 1997:

Norsk ordbok: Bokmål: Copyright © J. W. Cappelens Forlag A·S 1996.

CAPLEX: Copyright © J. W. Cappelens Forlag A·S 1997.

Two-Level Compiler: Copyright © Xerox Corporation 1994.

All rights reserved.

Norsk (Bokmål) stavekontroll: Copyright © Lingsoft Ab 2005.

Norske verk: Copyright © J. W. Cappelens Forlag A·S 1996, 1997:

Norsk ordbok: Bokmål: Copyright © J. W. Cappelens Forlag A·S 1996.

CAPLEX: Copyright © J. W. Cappelens Forlag A·S 1997.

Two-Level Compiler: Copyright © Xerox Corporation 1994.

Alle rettigheter forbeholdt.

Norwegian (nynorsk) speller: Copyright © Lingsoft, Inc. 2005.

February 1998 electronic version of Nynorskordboka: Copyright © University of Oslo and The Norwegian Language Council 1998.

Two-Level Compiler: Copyright © Xerox Corporation 1994.

All rights reserved.

Norsk (nynorsk) stavekontroll: Copyright © Lingsoft Ab 2005.

Februar 1998 elektronisk versjon av Nynorskordboka: Copyright © Universitetet i Oslo og Norsk Språkråd 1998.

Two-Level Compiler: Copyright © Xerox Corporation 1994.

Dei nemnde rettshavarane har alle rettar.

Finnish speller: Copyright © Lingsoft, Inc. 2005.

Two-Level Compiler: Copyright © Xerox Corporation 1994.

All rights reserved.

Suomen oikeinkirjoituksen tarkistus: Copyright © Lingsoft Oy 2005.

Two-Level Compiler: Copyright © Xerox Corporation 1994.

Kaikki oikeudet pidätetään.

Swedish speller: Copyright © Lingsoft, Inc. 2005.

Two-Level Compiler: Copyright © Xerox Corporation 1994.

All rights reserved.

Svensk stavningskontroll: Copyright © Lingsoft Ab 2005.

Two-Level Compiler: Copyright © Xerox Corporation 1994.

Alla rättigheter förbehålles.

"Portuguese Spell Checker © 1995-2005 Priberam Informática, Lda. All rights reserved."

Revisor Ortográfico e Hifenização para Língua Portuguesa, Versão 8, Itautec Philco SA, 2004

Tesauro para Língua Portuguesa, Versão 8, Itautec Philco SA, 2004

Revisor Gramatical para Língua Portuguesa, Versão 8, Itautec Philco SA, 2004

Speller for Brazilian Portuguese, Version 8, Itautec Philco SA, 2004

Controllo ortografico (con tecnologia Cogito) © 1994-2006 Expert System Modena. Tutti i diritti riservati.

Spelling checker (with Cogito technology) © 1994-2006 Expert System Modena. All rights reserved.

Hebrew Speller ©2005 Melingo. All rights reserved.

Outside In® HTML Export Version 8.0 Copyright © Stellent Chicago Sales, Ins.