Earlier last year, we announced that Exchange 2010 Service Pack 3 would be coming in the first half of 2013. Later, we updated the timeframe to Q1 2013. Today, we're pleased to announce the availability of Exchange Server 2010 Service Pack 3, which is ready to download.
Service Pack 3 is a fully slipstreamed version of Exchange 2010. The following new features and capabilities are included within SP3:
NOTE: Exchange 2010 SP3 allows Exchange 2010 servers to coexist with Exchange 2013 CU1, which is also scheduled to be released in Q1 2013. Customers can test and validate this update in a representative lab environment prior to rolling out in their production environments as an important coexistence preparatory step before introducing Exchange Server 2013 CU1.
In addition to the customer reported issues resolved in previous rollups, this service pack also resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:
Note: Some of the following KB articles may not be available at the time of publishing this post.
2552121 You cannot synchronize a mailbox by using an Exchange ActiveSync device in an Exchange Server 2010 environment
2729444 Mailboxes are quarantined after you install the Exchange Server 2010 SP2 version of the Exchange Server 2010 Management Pack
2778100 Long delay in receiving email messages by using Outlook in an Exchange Server 2010 environment
2779351 SCOM alert when the Test-PowerShellConnectivity cmdlet is executed in an Exchange Server 2010 organization
2784569 Slow performance when you search a GAL by using an EAS device in an Exchange Server 2010 environment
2796950 Microsoft.Exchange.Monitoring.exe process consumes excessive CPU resources when a SCOM server monitors Exchange Server 2010 Client Access servers
2800133 W3wp.exe process consumes excessive CPU and memory resources on an Exchange Client Access server after you apply Update Rollup 5 version 2 for Exchange Server 2010 SP2
2800346 Outlook freezes and high network load occurs when you apply retention policies to a mailbox in a mixed Exchange Server 2010 SP2 environment
2810617 Can't install Exchange Server 2010 SP3 when you define a Windows PowerShell script execution policy in Group Policy
2787500 Declined meeting request is added back to your calendar after a delegate opens the request by using Outlook 2010
2797529 Email message delivery is delayed on a Blackberry mobile device after you install Update Rollup 4 for Exchange Server 2010 SP2
2800080 ErrorServerBusy response code when you synchronize an EWS-based application to a mailbox in an Exchange Server 2010 environment
For more details, see Description of Exchange Server 2010 SP3.
Here are answers to some frequently asked questions.
Q. Does Exchange 2010 SP3 include the fixes in Exchange 2010 SP2 RU6? A. Yes. Service Packs are cumulative - they include all fixes included in previous RUs and service packs. Although Exchange 2010 SP2 RU6 was released on the same day as Exchange 2010 SP3, fixes in RU6 are included in SP3.
Q. Does Exchange 2010 SP3 include the security fix mentioned in Microsoft Security Bulletin MS13-012? Yes, fix for the vulneraiblity in MS13-012 is included in Exchange 2010 SP2 RU6, and (as stated above) fixes from SP2 RU6 are inclued in SP3. We recommend reviewing the related security bulletin before applying an update that contains security fixes.
Q. Why release RU6 for SP2 at all if all fixes are included in SP3? Exchange 2010 SP2 is a supported service pack (see Exchange Server Support Lifecycle). Customers typically deploy update rollups quickly but take longer to deploy service packs.
Q. Is Exchange 2010 SP3 compatible with WMF 3.0/PowerShell 3.0? A. Exchange team has validated and supports Exchange 2010 SP3 running on Windows Server 2012, which comes with PS 3.0 by default. Please note that even when running on Windows Server 2012, Exchange 2010 SP3 will still use only PowerShell 2.0 functionality. Exchange team has not validated Exchange 2010 SP3 running on earlier server OSes (2008, 2008 R2) with WMF3 / PS3 installed, and we therefore do not recommend that configuration.
Q. Does Exchange 2010 SP3 require an Active Directory schema update? A. Yes, as mentioned in Exchange 2010 SP3 Release Notes, an Active Directory schema is required.
Q. Can I install Exchange 2013 RTM in my Exchange 2010 organization after upgrading to Exchange 2010 SP3? A. As mentioned in the post, coexistence of Exchange 2013 in an Exchange 2010 SP3 org requires Exchange 2013 CU1, also scheduled for release in this quarter (Q1 2013).
Q. It's great that Exchange 2010 SP3 is supported on Windows Server 2012! Can I upgrade the OS my Exchange Server's running on from Windows Server 2008/2008 R2 to Windows Server 2012 after installing SP3? A. No. Upgrading the operating system after Exchange Server installation is not supported. You would have to uninstall Exchange, upgrade the OS, then reinstall Exchange. Or install Exchange 2010 SP3 on a fresh Windows 2012 install.
Q. Is MRM 1.0 supported on Exchange 2010 SP3? A. Yes, MRM 1.0 (Managed Folders) is a supported feature in Exchange 2010. We replaced MRM 1.0 management support in EMC with MRM 2.0 (Retention tags) in Exchange 2010 SP1. You can still use the Shell to manage MRM 1.0.
Q. Will I be able to restore and mount database backups created before a server is upgraded to SP3? A. Yes. When you restore and mount the database, it will be updated.
Q. Does Exchange 2010 SP3 add support for Active Directory Rights Management Services (AD RMS) in Cryptographic Mode 2? A. Yes, Information Rights Management (IRM) features in Exchange 2010 SP3 support AD RMS running in Cryptographic Mode 2.
Q. Is Exchange 2010 SP3 supported with <My great third-party Exchange add-on/tool>? A. Please contact the partner / third-party software vendor for this info. We recommend testing in a representative non-production environment before you deploy in production.