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:
I have gone through your links for “How to patch a CAS array” & ” How to patch a Database Availability Group” But I’ve not found any article so far related to “How to patch a Hub transport server”. Please let me know if any.
CAS Array members and DAG members have special steps required. Standalone Hub Transport servers have no special steps required. Just patch and reboot them one at a time. If you have a load balanced SMTP service then you may need to drainstop/disable them on the load balancer first.
hello and good evening, i am looking for a solution to my problem, who can help me?
i use the exchange2010 (server2011 SBS). since SP2 i can`t receive file attachments with an imap4 emailprofile in outlook2010 or an other emailclient like thunderbird.
i get the error subscribed folders. only textmails i can receive with imap.
Been trying to install this for a couple of months in test environment, which also has System Center 2012 and Server 2012 DCs and management consoles.
The Exchange server is still running 2008 R2, but with .NET 4 and probably WMI 3. The RU 4 is announced as installed in updates but Windows update keeps trying to install it again.
When I try to uninstall it tells me it has failed to remove RU2!
Should I just wiat for RU5?
Unable to intall RU4, I get the following error when I try to execute the exe file. Any idea what might be wrong.
I do see Update Rollup 3 in the installed updates list.
The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch.
The server is a Edge server which I’ve installed from scratch in the following order:
1. Exchange 2010 w/ SP1
2. Exchange 2010 SP2
3. Exchange 2010 SP2 RU 4.
The version matches with Exchange 2010 SP2. It’s just as if RU4 is ignored.
Got the same issue. After install of SP2 RU4 exchange still displays version 14.2 build 247.5 being installed.
That’s normal. From Microsoft:
“After you install an update rollup for Exchange 2010, the version of Exchange Server isn’t updated to show that the update rollup is installed.”
Correct, but it also doesn’t show in Programs and Features under Control Panel.
That I can’t explain, as it is showing up fine on mine. Do you see any of the other update rollups you previously installed listed there?
If you click on view installed updates it will show you the Update rollup.
I’ve installed SP2 RU3 and I see the installed update in Program and Features but the EMC still shows the SP2 version number 14.2 Build 247.5. Does the EMC show only the major version and not RU versions?
After installing SP2 RU4 on Exchange 2010 SP2 install running on Windows 2008 R2 Enterprise. If I look in Control panel, programs, view installed updates there is no reference to the Rollup being installed. I rebooted just to make sure, again no bueno. Any ideas??
I’m seeing the rollup updates just fine on my servers. I click on “View installed updates” and they’re at the top of the list in a group called “Exchange Server 2010 – Software Updates”
No idea why you wouldn’t be seeing them. Do you see other software updates in that list?