Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Description of Update Rollup 4 for Microsoft Exchange Server 2010 Release To Manufacturing
Article ID: 982639 - View products that this article applies to.
Microsoft has released Update Rollup 4 for Microsoft Exchange Server 2010 Release To Manufacturing (RTM). This article describes the following information about the update rollup:
Issues that the update rollup fixesUpdate Rollup 4 for Exchange Server 2010 RTM fixes the issues that are described in the following Microsoft Knowledge Base articles:
(http://support.microsoft.com/kb/979342/ )An attachment is not visible when an Exchange Server 2010 user opens a signed mail message by using Outlook 2003
(http://support.microsoft.com/kb/979517/ )You cannot send a message to a Dynamic Distribution Group in a mixed Exchange Server 2007 and Exchange Server 2010 environment
(http://support.microsoft.com/kb/979790/ )An IMAP4 client crashes when accessing an Exchange Server 2010 mailbox
(http://support.microsoft.com/kb/979801/ )An error message is generated in Exchange Server 2010 when you use Exchange Troubleshooting Assistant
(http://support.microsoft.com/kb/979810/ )You cannot connect an Exchange Server 2010 mailbox by using a MAPI client
(http://support.microsoft.com/kb/979848/ )Event ID 1066 is logged and you cannot move a mailbox from an Exchange Server 2003 server to an Exchange Server 2010 server
(http://support.microsoft.com/kb/979862/ )Event ID 4999 and Event ID 7031 are logged when you move a mailbox to an Exchange Server 2010 server
(http://support.microsoft.com/kb/979921/ )You cannot replicate a public folder from one Microsoft Exchange Server 2010 server to another, and Event ID 3079 is logged on the target server
(http://support.microsoft.com/kb/980149/ )The Add-MailboxDatabaseCopy command fails when it is used to add a database copy to a Database Availability Group in an Exchange Server 2010 environment
(http://support.microsoft.com/kb/980353/ )A MAPI application that is used to access Exchange Server 2010 mailboxes crashes when the application accesses an address book
(http://support.microsoft.com/kb/980354/ )"MAPI_E_INVALID_PARAMETER" error message when you copy email messages from an Exchange Server 2010 mailbox
(http://support.microsoft.com/kb/980364/ )Microsoft Exchange Transport service on an Exchange Server 2010 server crashes when a certain message is processed
(http://support.microsoft.com/kb/980701/ )An Exchange Server 2010 mailbox user receives a NDR error message when the user sends an email message to multiple internal users
(http://support.microsoft.com/kb/980852/ )The RpcClientAccess process on an Exchange Server 2010 server crashes when you access a mailbox by using a MAPI application
(http://support.microsoft.com/kb/981033/ )Error message when you expand the Microsoft Exchange On-Premises node in the EMC of Exchange Server 2010
(http://support.microsoft.com/kb/981961/ )Event ID 4033 is logged and the Free/Busy replication from an Exchange Server 2003 server to an Exchange Server 2010 server fails
(http://support.microsoft.com/kb/982209/ )Some embedded messages are corrupted when they are contained in a message that is sent from an Exchange Server 2010 mailbox address
(http://support.microsoft.com/kb/982378/ )A delegate receives only one meeting request when someone sends a meeting request to several principals in an Exchange Server 2010 RU1 or later environment
(http://support.microsoft.com/kb/982944/ )The msExchVersion attribute value of a user is stamped incorrectly after you run the Enable-MailUser cmdlet to mail-enable the user
(http://support.microsoft.com/kb/983200/ )The .xls file as an attachment is empty when you access an Exchange Server 2010 mailbox by using OWA
(http://support.microsoft.com/kb/983631/ )"redirect it to people or distribution list" rule does not work on an Exchange Server 2010 mailbox address
(http://support.microsoft.com/kb/2084061/ )A user intermittently fails to access an Exchange Server 2010 mailbox after the mailbox is moved
Update rollup information
To download and to install Update Rollup 4 for Exchange Server 2010 RTM, visit the following Microsoft Update Website:
http://update.microsoft.comNote Microsoft Update can detect Update Rollups on Exchange Server 2010 Mailbox servers that are part of a database availability group (DAG). But Microsoft recommends that you use the following article to manually install updates on these servers:
Installing Update Rollups on Database Availability Group Members
You may want to deploy Update Rollup 4 for Exchange Server 2010 RTM to multiple computers that are running Exchange Server 2010 RTM. Or, you may want to deploy Update Rollup 4 for Exchange Server 2010 RTM to Mailbox servers that are part of a database availability group (DAG). The update rollup is also available from the Microsoft Download Center.
The following file is available for download from the Microsoft Download Center:
Download the Exchange2010-KB982639-EN-x64 package now.Release Date: June 10, 2010
Important information for customers installing the update on computers 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
(http://crl.microsoft.com/pki/crl/products/CodeSigPCA.crl)website. 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 resolve this problem, turn off “Check for publisher’s certificate revocation” on the server that you are upgrading.
1. In Internet Explorer, select Tools , select Internet Options , and then click the Advanced Tab.
2. In the Security section, click to clear the Check for publisher's certificate revocation check box.
3. 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 for Outlook Web App users about Outlook Web App customization
When you apply an update rollup package, the update process will copy over the Outlook Web App files if needed. If you have changed the Logon.aspx file or other Outlook Web App files, the customizations will be overwritten to make sure that Outlook Web App is updated correctly. After you apply the update rollup package, you must re-create Outlook Web App customization in Logon.aspx.
We recommend that you always make a backup copy of any customized Outlook Web App files before you apply the update rollup. For more information about Outlook Web App customization details, visit the following Microsoft Website:
General information about Outlook Web App customization detailsIf you are a CAS Proxy Deployment Guidance customer, and if you have deployed CAS-CAS proxying, 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 Website:
General information about CAS-CAS proxying
The following list contains prerequisites for the Update Rollup 4 for Exchange Server 2010 RTM:
The required services are automatically stopped and then restarted when you apply this update rollup.
To remove Update Rollup 4 for Exchange Server 2010 RTM, use Add or Remove Programs in Control Panel. Then, remove update 982639.
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:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates