Blog Post

Exchange Team Blog
1 MIN READ

Released: Update Rollup 3 for Exchange 2010 Service Pack 2

The_Exchange_Team's avatar
The_Exchange_Team
Platinum Contributor
May 29, 2012

Earlier today, the Exchange CXP team released Update Rollup 3 for Exchange Server 2010 SP2 to the Download Center.

This update contains a number of customers reported and internally found issues. See KB2685289 Description of Update Rollup 3 for Exchange Server 2010 Service Pack 2 for more details.

Note: Some of the following KB articles may not be available at the time of publishing this post.

In particular we would like to specifically call out the following fixes which are included in this release:

  • KB2689810 Meeting Requests bodies get rendered in plain text in Outlook when created via Exchange Web Services.
  • KB2674445 Need the function to check ACL consistency during moving mailbox.
  • KB2700705 RpcClientAccess crashes with SocketException when UDP push notification is enabled.
  • KB2705425 Memory Leak in UMWorkerProcess.exe.
  • KB2698976 MRM Assistant doesnt process a mailbox with a contact created in other tenants.

General Notes:

For DST Changes: http://www.microsoft.com/time.

Note for Forefront Protection for Exchange users  For those of you running Forefront Protection for Exchange, be sure you perform these important steps from the command line in the Forefront directory before and after this rollup's installation process. Without these steps, Exchange services for Information Store and Transport will not start after you apply this update. Before installing the update, disable ForeFront by using this command: fscutility /disable. After installing the update, re-enable ForeFront by running fscutility /enable.

Exchange Team

Updated Jul 01, 2019
Version 2.0

50 Comments

  • @Fred M: Check out today's post by RS4:

    http://blogs.technet.com/b/exchange/archive/2012/05/30/rpc-client-access-cross-site-connectivity-changes.aspx

    Client Access Cross-Site Connectivity Changes

  • That 'disable Forefront' thing is so old had, so tedious done manually, when it can be done in a script instead.  So I fixed the (buggy) example script from an earlier Exchange Team blog post and made it more resilient:

    <a href="http://www.rebee.clara.net/blog/archives/2012/05/entry_199.html">Disabling Forefront for Exchange 2010 when Installing Exchange Service Packs and Hotfix Rollups</a>

    Enjoy

  • Many thanks to the Exchange team for releasing this update. It actually fixes a number issues we were experiencing and/or want to proactively avoid as we expect to encounter them very soon.

    Of special note for my team are the following:

    Synchronization of an organizational forms library fails when you use Outlook in Cache mode in an Exchange Server 2010 environment (this is HUGE as this has been an issue since we migrated to Exchange 2010).

    http://support.microsoft.com/kb/2572029

    You cannot access a mailbox for several hours after you disconnect and then reconnect the mailbox in an Exchange Server 2010 SP2 environment (we routinely have to run clean-database to remediate this issue).

    http://support.microsoft.com/kb/2682047

    You cannot create a mailbox or mail-enable a mailbox for a disabled user account in an Exchange Server 2010 environment (this is a welcome modification so we can cut down on the back and forth with our customers)

    http://support.microsoft.com/kb/2706523

    Thanks again!

  • @ Markus - no, it is not. The language pack was a one-off release to solve some specific issues. We do not update language packs via roll ups.

  • Is the language pack for SP2 released 6 days ago included in this rollup package ?

  • 2671128 - RPC Client Access Cross-Site connectivity issues occur in an Exchange Server 2010 environment

    Surprised this isn't highlighted because if I understand correctly, this is a big deal for people who've been missing the old Exchange behavior when moving mailboxes between servers at different sites - the Outlook profile will finally be updated properly now.

    --

    Anything coming for SP1?

  • @Tony V: When the download goes live and we publish the post, the KBs are not replicated and thus may not be available. We include a note indicating "Some of the following KB articles may not be available at the time of publishing this post.". In due course, they become available. For example, I can now access KB 2685289 as linked.

  • @Renzo - Windows Server 2012 has not been released to the web and thus is not supported in production environments unless you are in the appropriate TAP.  

    Ross

  • When is the support for Windows 2012 ready? Now, when you have DC running this, OWA does not work....

  • KB link seems invalid.  Searching for 2685289 doesn't bring up anything either