This update is no longer available. To fix the issues that are described in this article, install the latest Microsoft Exchange Server update from the following Microsoft Learn article:
Exchange Server build numbers and release dates
Microsoft provides download files only for N-2 versions for an Exchange Server cumulative update (CU), where "N" is the latest CU. The latest CU can be used to recover servers that are running Exchange Server. This includes servers that have a previous CU installed.
Microsoft has released Update Rollup 2 for Microsoft Exchange Server 2010. The update rollup was released on February 18, 2010. This article contains the following information about the update rollup:
The issues that the update rollup fixes
How to obtain the update rollup
The prerequisites to install the update rollup
Issues that the update rollup fixes
Update Rollup 2 for Exchange Server 2010 fixes the issues that are described in the following Microsoft Knowledge Base (KB) articles:
977633 Certain third-party IMAP4 clients cannot connect to Exchange Server 2003 mailboxes through an Exchange Server 2010 CAS server
979431 The POP3 service crashes when a user connects to a mailbox that is migrated from an Exchange Server 2003 server to an Exchange Server 2010 server through the POP3 protocol
979480 Users cannot receive new messages if they access mailboxes that are moved to another Exchange Server 2010 RU1 server by using IMAP4 clients
979563 Exchange Server 2010 Push Notifications does not work
979566 A 0x85010014 error is generated when linked mailbox users try to synchronize their mailboxes with mobile devices in a CAS-CAS proxying scenario in Exchange Server 2010
980261 This fix introduces the supports for Exchange Server 2010 page patching when a "-1022" disk I/O error is generated
980262 Event ID 2156 is logged on a computer that is running Exchange Server 2010
Update rollup information
To download and install Update Rollup 2 for Exchange Server 2010, visit the following Microsoft Update Web site:
http://update.microsoft.comNote Microsoft Update cannot detect update rollups on Exchange Server 2010 mailbox servers that are part of a database availability group (DAG).
You may deploy Update Rollup 2 for Exchange Server 2010 to multiple computers that are running Exchange Server 2010. Or, you may deploy Update Rollup 2 for Exchange Server 2010 to mailbox servers that are part of a database availability group (DAG).
The following files are available for download from the Microsoft Download Center:
Download the Exchange2010-KB979611-EN-x64 package now.
Important information for customers who install the update rollup on computers that are not connected to the Internet
When you install the update rollup on a computer that is not connected to the Internet, you may experience long installation times. Additionally, you may receive the following message:
"Creating Native images for .Net assemblies."
This behavior is caused by network requests that connect to the http://crl.microsoft.com/pki/crl/products/CodeSigPCA.crl Web site. The network requests look up the certificate revocation list for each assembly that native image generation (NGen) compiles to native code. However, the Exchange Server is not connected to the Internet. Therefore, each request must wait to time-out before it moves on. To fix this problem, turn off the “Check for publisher’s certificate revocation” security option on the server that is being upgraded. To do this, follow these steps:
In Internet Explorer, select Tools, select
Internet Options, and then click the AdvancedTab.
In the Security section, click to clear the Check for publisher's certificate revocation check box.
Click OK to close the Internet Options dialog box.
We recommend that you clear this security option in Internet Explorer if the computer was in a tightly controlled environment. When setup is complete, recheck the “Check for publisher’s certificate revocation” check box.
Important information about Outlook Web App customization for Outlook Web App users
When you apply an update rollup package, the update process overwrites the Microsoft Outlook Web App (OWA) files if it is necessary. If you change the Logon.aspx file or you change other OWA files, customizations are overwritten. Then, OWA is updated correctly. After you apply the update rollup package, you must re-create OWA customization in the Logon.aspx file. We recommend that you make a backup copy of customized OWA files before you apply the update rollup. For more information about OWA customization, visit the following Microsoft Web site:
Customize the Outlook Web App Sign-In and Sign-Out Pages
If you are a Client Access server Proxy Deployment Guidance customer, and if you have deployed Client Access server to Client Access server (CAS-CAS) proxying, you must apply the update rollup to the Internet-facing Client Access servers.
Note Make sure that you apply the update rollup to the internet-facing Client Access servers before you apply the update rollup to the non-Internet-facing Client Access servers.
For other Exchange Server 2010 configurations, the order in which you apply the update rollup to the servers is not important. For more information about CAS-CAS proxying, visit the following Microsoft Web site:
Understanding Proxying and Redirection
The following list contains prerequisites for the Update Rollup 2 for Exchange Server 2010:
Install Exchange Server 2010 on the computer before you apply this update rollup.
Remove all interim updates for Exchange Server 2010 before you apply this update rollup.
The required services are automatically stopped and then restarted when you apply this update rollup.
To remove Update Rollup 2 for Exchange Server 2010, click Add or Remove Programs in Control Panel. Then, remove the update rollup.
For more information about terminology that Microsoft uses to describe software updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates