Update Rollup 4 (UR4) for Exchange Server 2010 SP2 released
Microsoft has released the following update rollup for Exchange Server 2010:
- Update Rollup 4 for Exchange Server 2010 SP2 (KB2706690)
If you’re running Exchange Server 2010 SP2, you need to apply Update Rollup 4 for Exchange 2010 SP2 to address the issues listed below.
Remember, you only need to download the latest update for the version of Exchange that you’re running.
Here is a list of the fixes included in update rollup 4:
- 2536846 Email messages sent to a mail-enabled public folder may be queued in a delivery queue on the Hub Transport server in an Exchange Server 2010 environment
- 2632409 Sent item is copied to the Sent Items folder of the wrong mailbox in an Exchange Server 2010 environment when a user is granted the Send As permission
- 2637915 “550 5.7.1” NDR when an email message is sent between tenant organizations in a multi-tenant Exchange Server 2010 environment
- 2677727 MRM cannot process retention policies on a cloud-based archive mailbox if the primary mailbox is in an on-premises Exchange Server 2010 organization
- 2685001 Retention policies do not work for the Calendar and Tasks folders in an Exchange Server 2010 SP1 environment
- 2686540 Journal report is not delivered to a journaling mailbox in an Exchange Server 2010 environment
- 2689025 Performance issues when you use the light version of Outlook Web App in an Exchange Server 2010 environment
- 2698571 Some email messages are not delivered when you set the MessageRateLimit parameter in a throttling policy in an Exchange Server 2010 environment
- 2698899 Add-ADPermission cmdlet together with a DomainController parameter fails in an Exchange Server 2010 environment
- 2700172 Recipient’s email address is resolved incorrectly to a contact’s email address in an Exchange Server 2010 environment
- 2701162 User A that is granted the Full Access permission to User B’s mailbox cannot see detailed free/busy information for User B in an Exchange Server 2010 environment
- 2701624 ItemSubject field is empty when you run the Search-MailboxAuditLog cmdlet together with the ShowDetails parameter in an Exchange Server 2010 environment
- 2702963 The “Open Message In Conflict” button is not available in the conflict notification message in Exchange Server 2010
- 2707242 The Exchange Information Store service stops responding on an Exchange Server 2010 server
- 2709014 EdgeTransport.exe process crashes intermittently on an Exchange Server 2010 server
- 2709935 EdgeTransport.exe process repeatedly crashes on an Exchange Server 2010 server
- 2713339 Multi-Mailbox Search feature returns incorrect results when you perform a complex discovery search in an Exchange Server 2010 environment
- 2713371 Throttling policy throttles all EWS applications in Exchange Server 2010
- 2719894 The Microsoft Exchange RPC Client Access service consumes 100 percent of CPU resources and stops responding on an Exchange Server 2010 Client Access server
- 2723383 Incorrect time zone in a notification when the Resource Booking Attendant declines a meeting request from a user in a different time zone in an Exchange Server 2010 environment
- 2724188 A subject that contains colons is truncated in a mixed Exchange Server 2003 and Exchange Server 2010 environment
- 2726897 Event 14035 or Event 1006 is logged when Admin sessions are exhausted in an Exchange Server 2010 environment
- 2743871 Stop ForeFront services in RU setup so no manual steps are required
Update Rollup 4 for Exchange Server 2010 SP2 also resolves the issue that is described in Microsoft Security Bulletin MS12-058: Vulnerability in Microsoft Exchange Server WebReady document viewing could allow remote code execution: August 14, 2012
Download the rollup here.
Installation Notes:
If you haven’t installed Exchange Server yet, you can use the info at Quicker Exchange installs complete with service packs and rollups to save you some time.
Microsoft Update can’t detect rollups for Exchange 2010 servers that are members of a Database Availability Group (DAG). See the post Installing Exchange 2010 Rollups on DAG Servers for info, and a script, for installing update rollups.
Update Rollups should be applied to Internet facing Client Access Servers before being installed on non-Internet facing Client Access Servers.
If you’re installing the update rollup on Exchange servers that don’t have Internet access, see “Installing Exchange 2007 & 2010 rollups on servers that don’t have Internet access†for some additional steps.
Also, the installer and Add/Remove Programs text is only in English – even when being installed on non-English systems.
Hi Pat,
We no longer need to run boring fscutiliy command, eventually the Exchange team has integrated it “2743871 Stop Forefront services in RU setup so no manual steps are required” http://support.microsoft.com/kb/2743871
Yeah, thanks. I was actually reading about that and realized I missed it when I used my template for the post.