Release Notes for Exchange Server 2010 SP2

Article
07/23/2014

Applies to: Exchange Server 2010 SP2

For important legal information, see Legal Notice later in this document.

Welcome to Service Pack 2 (SP2) for Microsoft Exchange Server 2010. This document contains the following sections:

Installing Exchange 2010 SP2
Setup
Database Schema Upgrades
Client Access Server Prerequisite Changes
Role Based Access Control
Outlook Web App
Mailbox Replication Proxy
Shadow Redundancy Promotion Feature
Legal Notice

Installing Exchange 2010 SP2

Consider the following when you deploy Exchange 2010 SP2:

Exchange 2010 SP2 makes updates to the Active Directory schema. To learn more about these schema changes, see Exchange Server Changes to the Active Directory Schema.
You can select an option that installs the required Windows operating system roles and features for each selected Exchange 2010 SP2 server role.
You can only install Exchange 2010 SP2 on computers running the Windows Server 2008 operating system with Service Pack 2 (SP2) and the Windows Server 2008 R2 operating system.

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

Setup

When you upgrade from a previous version of Exchange 2010 to Exchange 2010 SP2 and you’ve previously defined the execution policy of Windows PowerShell scripts using group policies, Setup will fail. After Setup fails, Exchange 2010 will no longer work on the affected server and you won’t be able to restart Setup.

This issue happens because a required service is stopped by Setup during installation. This service is needed to query Active Directory Domain Services to verify the execution policy of Windows PowerShell scripts that must run as part of Setup.

To avoid this issue, do the following:

Use the Group Policy Management Console to disable the group policy. The Windows PowerShell execution policy group policy objects must be set to Undefined.
Install Exchange 2010 SP2.
Re-enable the previously defined Windows PowerShell execution policy through the Group Policy Management Console.

For more information about this issue, or if you’ve already run Setup and have encountered an error, see Microsoft Knowledge Base article 2668686, Error message when you try to install Exchange Server 2010 SP2: "AuthorizationManager check failed".

Database Schema Upgrades

The database schema for Exchange 2010 has been updated in Exchange 2010 SP1. Because SP2 contains all the fixes included in SP1, when Exchange 2010 RTM Mailbox servers are upgraded to SP2, the databases are upgraded to the Exchange 2010 SP1 version of the database schema. This database schema upgrade process adds time to the overall service pack upgrade process. During the upgrade, the database is dismounted, and all mailboxes in that database are taken offline. If you're upgrading the Mailbox server from the release to manufacturing (RTM) version of Exchange 2010 to Exchange 2010 SP2, the database upgrade process could take an additional 30 minutes or longer per database. You can track the progress of the database upgrade process by examining event 1185 in the Application event log on the server you're upgrading. After a database has been updated to the Exchange 2010 SP2 schema, it can't be mounted on a RTM Mailbox server.

If you're upgrading from Exchange 2010 SP1 to Exchange 2010 SP2, the upgrade process takes less time, because there is no database schema upgrade. In addition, you can safely move a database between servers running Exchange 2010 SP1 and SP2. Even though you can move databases between mailbox servers running different service pack levels, you should complete the upgrade of all DAG members to the same service pack level without too much delay. We recommend that you minimize the amount of time you have your DAG members running different service pack levels.

Client Access Server Prerequisite Changes

Several new prerequisites have been added when installing the Client Access server role. Prior to installing Exchange 2010 SP2, you must install these new prerequisites on servers that have the Client Access server role installed. If the prerequisites aren't installed, Setup will fail.

To install the prerequisites on Client Access servers, do the following:

Windows Server 2008 SP2

Open Server Manager.
Select Roles.
Under Web Server (IIS), select Add Role Services.
In the Add Role Services wizard, on the Select Role Services page, select the following Windows features:
- IIS 6 WMI Compatibility
- ASP.NET
- ISAPI Filters
- Client Certificate Mapping Authentication
- Directory Browsing
- HTTP Errors
- HTTP Logging
- HTTP Redirection
- Tracing
- Request Monitor
- Static Content
Click Next and then Install.

Windows Server 2008 R2

On the Start menu, navigate to All Programs > Accessories > Windows PowerShell. Open an elevated Windows PowerShell console, and run the following command:
```
Import-Module ServerManager
```

Add the prerequisites by running the following command:

Add-WindowsFeature Web-WMI,Web-Asp-Net,Web-ISAPI-Filter,Web-Client-Auth,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Http-Redirect,Web-Http-Tracing,Web-Request-Monitor,Web-Static-Content

If you want Exchange to install the new prerequisites during Setup, you can use unattended mode. Run the following command:

Setup /Mode:Upgrade /InstallWindowsComponents

Role Based Access Control

When you first install Exchange 2010 SP2 on an Exchange 2010 server in your organization, some Role Based Access Control (RBAC) management role definitions are updated in Active Directory. If you have multiple Exchange 2010 servers and you attempt to manage these roles from an Exchange 2010 server that hasn't been upgraded to Exchange 2010 SP2, you might receive one of the following warnings:

Exchange Management Shell

WARNING: The object MyMailboxDelegation has been corrupted, and it's in an inconsistent state. The following validation errors happened:

WARNING: The property value you specified, "15", isn't defined in the Enum type "ScopeType".
Exchange 2010 Control Panel

There are multiple warnings. Click here to see more

The object MyMailboxDelegation has been corrupted, and it's in an inconsistent state. The following validation errors happened:

The property value you specified, "15", isn't defined in the Enum type "ScopeType".

To resolve the warnings, upgrade the server to Exchange 2010 SP2. The cause of these warnings doesn't prevent Exchange 2010 from functioning correctly and can safely be ignored until the server is upgraded to Exchange 2010 SP2.

Outlook Web App

If you’re using redirection for Outlook Web App and aren’t requiring Secure Sockets Layer (SSL), redirection will fail after the Client Access server is upgraded to Exchange 2010 SP2. To avoid this problem, after you’ve completed the upgrade to Exchange 2010 SP2, modify the Outlook Web App web.config file. For directions, go to “Use IIS Manager and Notepad to simplify the Outlook Web App URL when SSL isn’t required” in Simplify the Outlook Web App URL. You don’t have to make any changes in IIS Manager to prevent redirection from failing. You just have to modify the web.config file.

Mailbox Replication Proxy

When you upgrade to Exchange 2010 SP2, the Mailbox Replication Proxy (MRSProxy) service is disabled by Exchange if it was previously enabled. This happens because the way MRSProxy is enabled has changed in Exchange 2010 SP2 and the settings in the <Exchange Installation Path>\V14\ClientAccess\ExchWeb\EWS\web.config file are not migrated during the upgrade. Until MRSProxy is re-enabled, cross-forest mailbox move requests will not be processed.

In Exchange 2010 SP2, MRSProxy is enabled by using the MRSProxyEnabled parameter on the Set-WebServicesVirtualDirectory cmdlet. You must manually enable MRSProxy after you upgrade to Exchange 2010 SP2. MRSProxy must be manually re-enabled on each server where it was previously enabled. For more information about how to enable MRSProxy in Exchange 2010 SP2, see Start the MRSProxy Service on a Remote Client Access Server.

Prior to Exchange 2010 SP2, MRSProxy configuration was stored in the <Exchange Installation Path>\V14\ClientAccess\ExchWeb\EWS\web.config file. The settings stored in this file are no longer used by MRSProxy in Exchange 2010 SP2 and should not be changed.

Shadow Redundancy Promotion Feature

When you install Service Pack 2 for Exchange 2010, the value of the Shadow Redundancy Promotion feature is reset to False, and the setting is disabled.

If you enabled Shadow Redundancy in your Exchange 2010 SP1 organization, you must re-enable Shadow Redundancy after you install Exchange 2010 SP2. Note that other settings in EdgeTransport.exe.config are not reset when you install Exchange 2010 SP2.

Legal Notice

This document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it.

Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred.

This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes.

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