Microsoft Releases RU3 for Exchange 2010 SP2

It’s only been a few weeks since we saw the release of RU2, but on May 29th Microsoft released RU3 for Microsoft Exchange Server 2010 SP2. This latest update rollup package includes a number of important fixes for Exchange servers; 42 to be more precise, and considering 42 is the answer, this is an RU you won’t want to skip.

As with all update rollups, RU3 includes all patches since the release of the service pack. They are cumulative, so if you missed out on RU1 or RU2, consider 3 a lucky number and make this the RU you test and deploy, especially if you are a Unified Messaging shop or planning on or already in a hybrid deployment with Office 365 or other hosted Exchange infrastructure.

RU3 can be downloaded from this link and is covered in KB 2685289. The 33MB download contains fixes for several issues with Exchange 2010. Some of the highlights include fixes for

  • 2689810 Meeting Requests bodies get rendered in plain text in Outlook when created via Exchange Web Services.
  • 2700705 RpcClientAccess crashes with SocketException when UDP push notification is enabled.
  • 2705425 Memory Leak in UMWorkerProcess.exe.
  •  2586828  The EdgeTransport.exe process consumes 100 percent of CPU resources on an Exchange Server 2010 Edge Transport server
  • 2589233  Meeting requests bypass the requirement for delegate approval and instead book resource mailboxes automatically in an Exchange Server 2010 environment
  • 2648263  You cannot open routing log files on Exchange Server 2010 Hub Transport servers in a mixed Exchange Server 2003 and Exchange Server 2010 environment
  • 2667120  MSExchangeAutodiscoverAppPool application pool crashes on an Exchange Server 2010 Client Access server when you try to view the free/busy information about a user in a trusted domain
  • 2671128  RPC Client Access Cross-Site connectivity issues occur in an Exchange Server 2010 environment
  • 2673591  Crash occurs in the Autodiscover application pool in an Exchange Server 2010 environment
  • 2684583  You cannot delete an empty folder in a .pst file by using Outlook in an Exchange Server 2010 environment
  • 2689810  A meeting request that you send from an EWS application is in plain text format instead of HTML format when an attendee opens the request by using Outlook in online mode
  • 2695011  Junk Email settings do not work as expected after you migrate or move a mailbox to an Exchange Server 2010 SP1 Mailbox server
  • 2695022  The E-mail Signature text box is not editable in Outlook Web App when you use Google Chrome in an Exchange Server 2010 environment
  • 2695836  You cannot move a mailbox in an Exchange Server 2010 environment that has a message size limit configured
  • 2698927  Resource mailbox that has AutoAccept configured does not process a meeting request that contains custom code or script in Exchange Server 2010
  • 2698960  You cannot move some users’ mailboxes from one Exchange Server 2010 mailbox database to another
  • 2699582  Error message when you play a voice mail by using Outlook 2007 in an Exchange Server 2010 environment
  • 2705425  UMWorkerProcess.exe consumes large amounts of memory when you try to listen to voice messages by using Outlook Voice Access in an Exchange Server 2010 environment
  • 2705555  The Set-Mailbox cmdlet takes a long time to complete configuration in an Exchange Server 2010 environment
  • 2705647  A user cannot log on to a mailbox that is full by using Outlook Web App in an Exchange Server 2010 environment


As with previous RUs and Service Packs, follow the normal deployment order of:

  1. Client Access Servers (all servers in a CAS array consecutively)
  2. Hub Transport Servers
  3. Unified Messaging Servers
  4. Mailbox Servers
  5. Edge Transport Servers (which can actually be done whenever, but it makes sense to leave them to last just for consistency).

Again, I recommend launching the update with the following syntax to create a full log of the install.

Exchange2010-KB2685289-x64-en.msp /lvx pathtologfile.txt [enter]

And just like previous RUs, there are some special considerations for the following.

Mailbox servers in DAGs

Exchange 2010 SP2 servers with the mailbox role that participate in Database Availability Groups (DAGs) will not detect this update as available when running Windows Update. You will need to manually deploy this update to those servers.

CRL Checking

As is usual for Update Rollups, should you have an Exchange server without Internet access, you will likely experience very long installation times as the server tries to check the Certificate Revocation List for the .Net assemblies. You can avoid this issue by setting Internet Explorer so that it doesn’t check for certificates that have been revoked. To do this, follow these steps:

  1. In Internet Explorer, select Tools, select Internet Options, and then click the Advanced Tab.
  2. In the Security section, click to clear the Check for publisher’s certificate revocation check box.
  3. Click OK to close the Internet Options dialog box.

OWA Customizations

If you have implemented any customizations for Outlook Web App, such as altering the logon.aspx or other pages, installing RU2 will overwrite these files. Make a backup of them first, and you can then replace the custom files after the update is complete.

CAS-CAS Proxying

As with previous updates, users of CAS-CAS proxy setups will want to patch the Internet facing CAS servers before you patch the internal ones.

While I will always recommend that customers stay current on their patching, UM and hybrid customers really do want to deploy this rollup patch. The fixes for both Unified Messaging and mailbox moves make this an important update for everyone.

Written by Casper Manes

I currently work as a Senior Messaging Consultant for one of the premier consulting firms in the world, I cut my teeth on Exchange 5.0, and have worked with every version of Microsoft’s awesome email package since then, as well as MHS, Sendmail, and MailEnable systems. I've written dozens of articles on behalf of my past employers, their partners, and others, and I finally decided to embrace blogging and social media, so please follow me on Twitter @caspermanes if you enjoy my posts.


  1. Christian Yarving · June 10, 2012

    Maybe I’ve just been lucky, but I tend to jump on RU’s because they leave a window for the individual patches to be tested in multiple environments before they’re added into the full rollup. I don’t feel safe deploying every single update as they happen, but when a rollup hits, I don’t waste much time in getting it installed.

  2. Rodnie Tannly · June 11, 2012

    This is good! So many of those patches have long been awaited for, especially since I’ve come across some of the annoyances involved without those patches.

    Just like when employees miss a meeting they clearly want to attend but just wasn’t able to schedule it to set up a reminder, many a time are the tools blamed or even the administrators of the tools (me!) for missing something.

    Most tools should never replace a good sense of organization, a sharp memory and a good personal system. But, heck, people would always want to blame it on their calendars, or their emails or sometimes, their IT.

Leave A Reply