Microsoft has released Update Rollup 4 for Exchange Server 2010 SP2.
Important: please read Tony Redmond’s column here when you are considering the deployment of this update rollup.
From the Microsoft Exchange Team blog:
On August 13th 2012, the Exchange CXP team released Update Rollup 4 for Exchange Server 2010 SP2 to the Download Center.
This update contains a number of customer reported and internally found issues. See KB 2706690 Description of Update Rollup 4 for Exchange Server 2010 Service Pack 2 for more details.
In particular we would like to specifically call out the following fixes which are included in this release:
Note: Some of the following KB articles may not be available at the time of publishing this post.
- New updates for August DST – Exchange 2010 – SP2 RU4 – Display name for OWA.
- 2685001 Retention policies do not work for the Calendar and Tasks folders in an Exchange Server 2010 SP1 environment
- 2686540 Exchange 2010 Messages are not delivered to Journal Mailbox
- 2701162 Granting Full Mailbox Access Does Not Allow Full Details of Free/Busy To Be Displayed
- 2724188 Information loss due to unexpected subject modification while copying a message in Outlook
- 2743871 Stop Forefront services in RU setup so no manual steps are required
This update rollup also includes the fix for the following security vulnerability:
2743246 MS12-058: Vulnerability in Microsoft Exchange Server WebReady document viewing could allow remote code execution
Download Exchange Server 2010 SP2 Update Rollup 4 here.
Deploying Exchange Server 2010 SP2 Update Rollup 4
The standard order of deployment for Exchange Server updates applies.
- Client Access servers, starting with the internet-facing ones. See this article for how to patch a CAS array.
- Hub Transport and Edge Transport servers
- Mailbox servers. See this article for how to patch a Database Availability Group.
- Unified Messaging servers
You can also use Exchange MVP Andy Grogan’s RUPS tool to assist with the deployment.
In what will surely be a relief to many customers running Forefront Protection for Exchange this update rollup also includes this patch:
2743871 Stop Forefront services in RU setup so no manual steps are required
Update: Microsoft has stated that the new behavior is included in Update Rollup 4
Because the KB article content isn’t live at the time of this writing it is not clear whether this means installing UR4 itself will still require the Forefront services disabled/enabled, or whether the UR4 installer includes that new feature.
If not, then at least this should be the last time that you need to remember to disable/enable FPE when installing update rollups.
Before installing the update, disable ForeFront by using this command: fscutility /disable. After installing the update, re-enable ForeFront by running fscutility /enable.
Or use the CustomPatchInstallerActions.ps1 script detailed here: