Released: Update Rollup 2 for Exchange 2010 Service Pack 2

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

This update contains a number of customer-reported and internally found issues since the release of SP2 RU1. See KB2661854: Description of Update Rollup 2 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.

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

  • KB2696913 You cannot log on to Outlook Web App when a proxy is set up in an Exchange Server 2010 environment
  • KB2688667 High CPU in W3WP when processing recurrence items who fall on DST cutover
  • KB2592398 PR_INTERNET_MESSAGE_ID is the same on messages resent by Outlook
  • KB2630808 EwsAllowMacOutlook Setting Not Honored
  • KB2661277 Android/Iphones stuck with 451 during Cross forest proxy in datacenter
  • KB2678414  Contact name doesn't display company if name fields are left blank

Note that this fix will not cause the CAS to CAS OWA proxying incompatibility with Exchange 2007 as discussed here. No additional updates are required on Exchange 2007 for proxying to work once Exchange 2010 SP2 RU2 is installed.

General Notes:

For DST Changes:

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

Comments (44)
  1. Simon says:

    Note for Forefront Protection for Exchange users: We still don't care enough about you to add two lines to the setup script. Instead you have to do it manually. Or you can install the update via Microsoft Update and you'll be in for a funny surprise.

  2. franc1 says:

    Does this rollup also fix the 'The Active Directory entry for mailbox <mailboxname> contains an invalid locale for attribute MsExchUserCulture: nl-NL. ' error that was introduced after installing the updated Dutch language pack for SP2?

  3. Greg Taylor [msft] says:

    @ Franc – no, it does not, we have afix for that on the way though I can assure you.

  4. Riccardo Moretti says:

    Hey Microsoft…. could you not detect for your own software and automatically run the command fscutility /disable????, Now I cannot even get WUS to do this….

    Annoyed! and feeling unappreciated as a FF customer

  5. turbomcp says:

    Enough with crying about forefront:)

    cant you create a batch that stops 3 services and runs fsutility, tie the whole thing to sccm if itsreally so hard for you guys:)

    trust me one of the promosing features of 2013 will be that thing:) and its not to make it easier just to shut up the winners here:)

    its microsoft it takes time:)

  6. says:


    is it possible that i have conneciton problems from my Outlook 2010 to the Exchange Server 2010 with SP1 RU2 installed? Everything was working fine up to the moment i installed this update.

    Now i can not connect from inside the network to the Exchange. Outlook WebApp works perfectly.

  7. Daniel Sheehan says:

    @Kerschi – this is RU2 for SP2, not SP1.

    As for "is it possible that i have conneciton problems", that's entirely possible. Basic trouble shooting steps would need to be performed to determine the root cause, including closing and re-opening Outlook and/or rebooting your desktop.

    If you continue to have problems I suggest you go to the TechNet forums to post your issue in detail and ask for assistance.

  8. CheeseWithMyWhine says:

    I just wanted to post and complain about having to disable Forefront before installing this…all the cool kids are doing it.  It's sooooooooooooo hard and takes soooooooooooooooo long to do it!

  9. invalid characterset and transport server crashes says:

    is the error in Rollup package 1 fixed by this rollup package.

    If Exchange determines a mail encoded with invalic.characterset then this mail isn´t discarded like in older versions but the transport service crashes in Exchange 2010 Sp2 RU 1.

  10. Nathan Raper says:

    Has anyone else had any difficulty installing SP2 RU2? I've attempted an install on two separate fresh servers and it fails on both – rolling back… I've tried at patch level of SP2 *and* SP2 w/ RU1…

  11. says:

    @Nathan: you have to install it from an elevated (run as administrator) cmd.

    I did forget this step too with RU1 and the error message does not explain anything ;)

  12. Almost funny to see that after two service pack and several rollups, the problem with retention policies on junk mail and/or deleted items still are there. I understand this could be difficult to fix, but have Microsft even acknowledged the problem?

  13. sog says:


    Just a simple question:

    Does this Rollup contains all patches included in previous Rollup 1 for Exchange 2010 Service Pack 2?

    I'm about to install new instance of EX2k10 SP2 and wan't to make sure if placing only RU2 packet in updates folder of exchnage install files will be get newly Installed Exchange up to date out of the box.

    Thanks for confirmation.

  14. @sog, yes Rollup Updates are cumulative of all previous RUs for that service pack. You can put this into the .Updates folder for new Exchange server installs so it is automatically installed, but upgrades from SP1 to SP2 with an RU in the .Updates folder will not work.

  15. Sven J says:

    This RU takes about 3 times more time to install than pervious RU's and requires restart.( At least for in my enviroment).

    But installation went fine and everything seems to be working as it should be.

  16. says:

    Hey Exchange Team,

    will this UR fix the [8004010F-501-8004010F-0] Syncronize Error in an Exchange 2010 and Outlook 2010 enviroment as discribed here?…/79b40a4b-ea8f-4fd9-b060-70dd8ba4b4ba Since the last UR we get this Error on all Clients. One Comment says UR 2 for SP2 will fix it and i cant find anything what confirms it. Can you help? Thank you!

  17. YB says:

    After successfully (at least no errors was presented) installing rollup 2 for Exchange 2010 SP2 the version number shown is Version 14.2 (Build 247.5). The update shows up in "Programs and features" as installed. According to that article:…/ the version should be  Version 14.2 (Build 298.4).

    Can someone from the team elaborate a bit on that?

  18. Karsten says:

    @YB: For a unknown reason MS does not show the RU Version in the GUI at the list of Servers. On the Website You linked you can find the following Sentence:

    This Script  can be used to find Exchange 2007 and Exchange 2010 build numbers in your environment

    "This Script" is a link to a scipt that tells you the number you are looking for ( in a file it produces (results.csv).

  19. Arjan Mensch says:

    I didn’t need to restart, it did take a very long time starting services at the end of the update.

    Make sure you stop services like Backup Exec Remote Agent, McAfee Groupshield..

    Note to all Dutch users: The localization bug that appeared in SP2 is NOT fixed. This bug was mentioned with the release of SP2 and again with the release of RU1 (…/released-update-rollup-1-for-exchange-2010-service-pack-2.aspx).
    RU2 does NOT fix this issue.

    Any ETA on a fix for this annoying issue? I actually have customers that made me roll back SP2 for this :S

    Other than that: Chees on the updates / fixes!

  20. Ken says:

    This update has brought the Management Console to a crawl on my servers.  It takes 5 minutes to get it to actually open and be usable and then you have to wait again to access mailboxes and other info.

    And I agree about the Forefront script.  How hard would it be to include that?

  21. Greg Taylor [msft] says:

    @ Arjan – we are still working on the invalid locale error, it's a fairly difficult issue to fix it turns out, but we are still working on it. Sorry for the continued delay.

  22. Is this still a supported approach for dealing with the Forefront issues around update rollups? And if so, why not mention it in the release announcements such as this one?

  23. ewe says:

    Great… Update crashed somwhere and all services stay disabled – hooray for unattended update-nights -.-

  24. Oliver Meier says:


    ist it only a Dutch Problem oder other languaes too?

    We have a german Exchange 2010 SP2 RU1/2 and have the following problem:

    The Active Directory entry for mailbox /DC=net/DC=domain/OU=Branch/OU=Office/OU=Benutzer/OU=OLSig/CN=Max Mustermann contains an invalid locale for attribute MsExchUserCulture: de-DE.

    All new Mailboxes are in English even though they have been initialized in German. Is these any solution jet?


  25. Greg Taylor [msft] says:

    Oliver – so the updated language pack was only ever required for those with the Dutch OWA issue. It fixed that issue. It also unfortunately introduced the event log error issue you are seeing, so if you installed the language pack you would see the issue. We have a fix for this in the works, the format will be a new language pack download I expect.

  26. Oliver Meier says:

    Greg, thy for the fast answer.

    So I see it correct that the error in our System was caused by the language pack.

    Is it normal that we do not thereby be able to create new mailboxes in German. All new mailboxes have English folder names.

    When can we expect with the new language pack?


  27. Greg Taylor [msft] says:

    Any language setting other than en-us will cause the errors to be thrown. Sorry.

    we're still working on the revised language pack, I can't give you any more specific dates or times than that.

  28. Oliver Meer says:

    OK, thx, so we have to wait.

    Can it be that the errors have been since SP2.

    We have updated all our Exchange servers to SP2, and only one of the MBX server had this error in the event log.

    Thereupon, we then have only tried to correct the situation in which we have installed the language pack?


  29. Greg Taylor [msft] says:

    The updated lang pack is not needed for anyone not using Dutch. More, if the updated lang pack is installed only on the CAS, it fixes the Dutch issue and the errors aren't logged. The issue occurrs when the lang pack is installed on the mailbox role. It does not need to be (unless of course you have multi-role then you clearly have no choice).

  30. Oliver Meier says:

    Yes, I understand, we didn´t needed the language pack update, because we don´t have Dutch Language.

    But we had the problem since the SP2 installation, and not only since installing the language packs.

    We only tried to install the language pack to fix the error.

    Are you sure, that the error only appears since the language update?

    Thx a lot for your help.

  31. Greg Taylor [msft] says:

    I can only repro the issue after installing the language pack. We have had no other reports of the issue, without the updated language pack being installed.

  32. TH says:

    I'm trying to enable the included fix described in kb2661294. But I don't have the registry key Admin.   (HKEY_LOCAL_MACHINESOFTWAREMicrosoftExchangeServerv14Admin). Should I create the key first if it doesn't exist?

  33. says:

    Greg, many thanks for the info.

    Where can we learn fastest when there is a new Lanugage Pack?

  34. Bill Coulter says:

    We had to uninstall RU1 for SP2 because of kb2693078. RU1 eventually showed up in Microsoft Update. Today we installed RU2. After restarting and manually triggering check-for-updates in Microsoft update, it still wants to install RU1. Can you guys do anything about that or is Microsoft update just a complete mess and unfixable?

  35. Greg Taylor [msft] says:

    Oliver – I'll try and re-post here when we make the update available, or write a new post.

  36. Richard says:

    If you want to find the exact build here's a PS command to run

    GCM exsetup |%{$_.Fileversioninfo}

    Then compare the output with the list located at…/exchange-server-and-update-rollups-builds-numbers.aspx

  37. Oliver Meier says:

    Hallo Greg,

    do you have any news for me?

  38. Eelco says:

    Can we get some feedback about this? There is comming a lot of calls about this from our customers.

  39. tom says:

    Hey Bill,

    i have the same Question:

    Why Windows Update offer me RU1 after Installation RU2? It seems there is something buggy in the Versionchecking from WindowsupdateClient.

    We Jumped from SP2 to RU2, without installing RU1

  40. Greg Taylor [msft] says:

    We're finishing up the testing on the new language pack. Once complete (and assuming no problems) we'll be releasing it. I'll post again when I have a link (unless someone beats me to it).

  41. tork247 says:

    when will RU2 be released on Windows Update?

  42. Oliver Meier says:

    Thx Greg for the Info.

    Is there any news for us?


  43. wil says:


    You may also check how to send SMS from MS Exchange 2010 with Ozeki NG SMS Gateway


Comments are closed.

Skip to main content