Microsoft has released a series of update rollups for Exchange Server 2010 SP1 and SP2, and Exchange Server 2007 SP3. From the MS Exchange Team blog:
Today the Exchange CXP team released the following update rollups to the Download Center. All three releases cover Security Bulletin MS12-080. Because this is a security release, the updates will also be available on Microsoft Update.
- Update Rollup 5-v2 for Exchange Server 2010 Service Pack 2
- Update Rollup 8 for Exchange Server 2010 Service Pack 1
- Update Rollup 9 for Exchange Server 2007 Service Pack 3
Update Rollup 5-v2 for Exchange Server 2010 SP2
This update contains a number of customer reported and internally found issues. For a list of updates included in this rollup, see KB 2785908 Description of Update Rollup 5 version 2 for Exchange Server 2010 Service Pack 2. We would like to specifically call out the following fixes which are included in this release:
- 2748766 Retention policy information does not show “expiration suspended” in Outlook Web App when the mailbox is set to retention hold in an Exchange Server 2010 environment
- 2712595 Microsoft Exchange RPC Client Access service crashes when you run the New-MailboxExportRequest cmdlet in an Exchange Server 2010 environment
- 2750847 An Exchange Server 2010 user unexpectedly uses a public folder server that is located far away or on a slow network
Before you rush to install them (and really you should test them first) I recommend you read the comments on that post to check for any reports of issues from other customers.
You should also be aware of issues being reported for customers who have installed the WMF 3.0 (PowerShell v3.0) updates on their pre-2013 Exchange servers. Exchange MVP Michael B Smith covers the issues here.
In every article of Exchange 2010 SP2 RU I see this remark: Note Remove all interim updates for Exchange Server 2010 SP2 before you apply this update rollup.
Do they expect us to remove RU1, RU2, RU3, RU4 before we apply RU5 or are they talking about updates that were installed between RU versions that were not a part of those RU’s ?
No, the rollups don’t need to be removed.
Interim updates are individual hotfixes that solve specific bugs or problems. Generally you’ll know if you have interim updates installed because MS Support will direct you to install one for a problem you’re having.
Hi, after install update rollup 9 for exchange server 2007 sp3, team LAN in my HP server is disable and I can’t reenable and the DHCP server fail, i can’t unistall the update, can you help me?
Those seem like unrelated issues to me so I can only recommend you log on to the server console and troubleshoot the teamed NICs.
Hi Dan,
Did you also happen to install Windows Management Framework 3.0 as well? That can cause problems.
http://blogs.technet.com/b/exchange/archive/2012/12/14/windows-management-framework-3-0-on-exchange-2007-and-exchange-2010.aspx
BEWARE: Attempting to install Update Rollup 9 for Exchange Server 2007 Service Pack 3 has broken my Exchange Server. I am running this on a virtual machine instance of MS Windows 2008 Small Business Server. The installation stops prematurely with an error. I have tried it multiple times through MS Update as well as downloading the package to my desktop and installing from there. Now all Exchange services show as “Disabled” in Services. I am desperate for some help if there is anyone who has a solution.
I also cannot run the Exchange Management Console and am also unable to uninstall the Rollup 8-v2 through Control Panel. I get errors all around.
Dan, Are you running Forefront on the SBS Server at all? The below excerpt may also apply to UR9
http://technet.microsoft.com/en-us/library/jj820238(v=exchg.80).aspx
If you are using Microsoft Forefront Security for Exchange Server, you must disable Forefront Security for Exchange Server before you install Update Rollup 8 version 2 for Exchange 2007 SP3. To do this, run the fscutility /disable command.
After you install the update rollup package, you must re-enable Forefront Security for Exchange Server. To do this, run the fscutility /enable command.
Note:
If you do not disable Forefront Security for Exchange Server before you install the update rollup, the Information Store service and the Transport service do not start.
I’m curious to what issues there are with Powershell 3.0 and Exchange 2010. I’ve had this combination in my test environment for a few days now and everything appears to be working together nicely. However, I did try to upgrade my test environment to rollup 5v2 but it keeps failing permaturely with “Unable to install because a previous Interim Update for Exchange Server 2010 has been installed. Please use Add/Remove Programs to uninstall the Interim Update before running this setup again.” I havent installed any Exchange hotfixes but i had a feeling it was because i installed Powershell 3.0. This article confirms that now, but still curious to what else breaks.
Its not supported. That doesn’t necessarily mean there are known issues (though there may be), but at the very least it means not yet tested and so there is no support statement about it yet.