Released: Update Rollup 5 v2 for Exchange 2010 SP2, Exchange 2010 SP1 RU8 and Exchange 2007 SP3 RU9

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 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:

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

  • 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

For DST Changes:

Exchange Team

Comments (97)
  1. Paul Bendall says:

    I for one find the product teams decision to fix security vulnerabilities only in Update Rollups completely unacceptable and at odds with many other products in the Microsoft product line. A security vulerability should be addressed by a small hotfix that addresses the vulnerability rather than part of a much wider rollup which includes additional functionallity and a much braoder change to the code base. For those in coprorate environments testing a large rollup is at odds with security patching.

    The number of re-issues for rollups in the last year or so also reinforces the need not to be an early adopter and effectively test updates which is at odds with covering an exploit.

    I wish you would review this methodology.


  2. Aaron A says:

    I agree with Paul and am very concerned with the quality assurance testing that goes into these roll-ups.  I have a policy that I don't touch Roll-ups for a month to wait and see if a recall is going to happen.

  3. GB FishServe says:

    I recently completed the transition from Exchange 2007 to Exchange 2010. My testing and planning included RU 4 and then RU4-v2.

    However, after reading of many problems experienced after either or these RUs, the majority of who roll-backed to RU3, I proceed with just RU3. As RU5 only just came out, I decided to wait a month or so for any fallout.

    The quality assurance of these RU is of some concern and this stage, will have to stick with RU3 until a stable RU is released.

  4. When compared to the original version, the following fix went MIA in EX2010SP2RU5v2:

    2748870 Declined meeting request is added back to your calendar after a delegate opens the request by using Outlook 2010

  5. deiruch says:

    Didn't work for me. Just wanted to let you guys know. Tried disabling Forefront manually, but that didn't help.


    CAQuietExec:  Error 0x80070001: Command line returned an error.

    CAQuietExec:  Error 0x80070001: CAQuietExec Failed

    CustomAction CA_CUSTOMER_PREPATCH_INSTALL returned actual error code 1603 but will be translated to success due to continue marking




    Action 23:33:19: CA_SAVEDATA_STOP_SERVICES. Stopping services

    CAQuietExec:  Error 0x80070001: Command line returned an error.

    CAQuietExec:  Error 0x80070001: CAQuietExec Failed

    CustomAction CA_SAVEDATA_STOP_SERVICES returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

    Action ended 23:33:31: InstallExecute. Return value 3.

  6. Nino Bilic says:

    @deiruch – what did you try installing, on which kind of server (roles etc.)?

  7. Bharat Suneja [MSFT] says:

    Note that it's no longer required to restart ForeFront service manually since Exchange 2010 SP2 RU4. See KB 2743871 Microsoft Exchange Transport service does not restart automatically after an Exchange update is installed.

  8. Doug says:

    Has this fixed the problem whereby moving mailboxes sits retrying 5 times every 60 seconds at the end of the move before stating that it failed to clean up the source mailbox. This was introduced in update 3 for SP2 and is extremely infuriating during migrations. Big thread on technet forums about it.

  9. deiruch says:

    @Nino: I tried installing Exchange2010-KB2785908-v2-x64-en.msp on Version 14.2 (Build 247.5). All roles are installed (Hub Transport, Client Access, Mailbox, Unified Messaging), though UM is not in use. Can't install KB2756485 (RU4-v2) because of the same problem. All other (previous) WU-distributed updates are installed. Everything on 2008R2 SP1. I checked kb981474 too, only LocalMachine is set to "RemoteSigned".

  10. PLEASE stop releasing these crummy updates!!! says:

    We've had three versions of rollup 8 (ex2k7) and 2 versions of rollup 4 (ex2k10). Rollup 5 was pulled as well. When does the madness stop?

    This is ridiculous beyond belief. There are too many bugs being found in these releases. As the first poster in this thread, Paul Bendall, points out – Microsoft needs to STOP with these rollups that add additional functionality. You're constantly breaking things constantly. Are things really this pathetic at Microsoft?

    Test your rollups and SP's THOROUGHLY before releasing them. This is crazy embarrassing.

  11. Mark says:

    Same issue as Deiruch, down to identical errors in the log files. Installing on  Hub, CAS & Mailbox standalone. No Forefront installed.

  12. Juergen says:

    Please stop releasing Security Updates only through RU´s!!!!!

  13. Exchange 2010 SP2 UR4 mailbox move to another DB on the same server with newly created databases gives warning/error:

    The Microsoft Exchange Mailbox Replication service completed request <mailbox> with warnings.

    Warning: Failed to clean up the source mailbox after the move.

    Error details: MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634)

    Is this solved with UR5v2?

  14. Come on people... says:

    all in all Exchange still works great and has broad functionality. Groupw#?! is even worse, believe me. What is really emberassing, is the fact that TMG 2010 is abandoned – this was a great mistake and sympathy for Microsoft is declining. Some other bad decisions will accelerate this process.

  15. ThommyG says:

    Someone has to stop this RU Versioning mess immediately! I can't belive that the biggest software company in the world makes such a poor job in QA. What's going on? Hey, wake up!

  16. Chris Knight says:

    Using an Update Rollup to deploy a security update is really poor practice, given the past history on the quality of Update Rollup releases. Please separate out security updates from Update Rollups.

  17. jhahnde says:

    Stop deploying security patches in combination with roll ups NOW!!! Security patches need to be applyed quickly – but roll ups needs testing AT MICROSOFT and on the customer side.

  18. Phil says:

    Re the disabling Forefront thing, see my blog post here:…/entry_199.html

    Simple, effective, one less thing to worry about, even if it isn't strictly needed anymore.

    On the subject of 'security updates in roillups only', I have some sympathy with Microsoft on this one.  It means just one security patch (in the rollup) and not a different patch for every flavour, e.g. one each for SP2, SP2 RU1, SP2 RU2, SP2 RU3, SP2 RU4, SP2 RU4-2, SP2 RU5, and SP2 RU5-2.  That's asking for trouble.

  19. GoodThings2Life says:

    I agree with everyone else here. What the hell is going on with the QA for Exchange development these days? UR's should be separate from security hotfixes, or the logic behind joining them should be explained clearly.

    If they must be joined, then higher levels of QA *must* be done before release. This constant pulling and re-issuing nonsense has got to stop. The number of re-releases over the past 3 years is absurd for a company of Microsoft's resources.

    I've had to adopt a policy of waiting 60-90 days to install these updates just so I'm not introducing major bugs into my environment. Unfortunately, it means I'm missing out on security fixes in the meantime.

  20. Andrew says:

    If releasing quality updates means delaying release of said update – then delay the release of the update!!!

    I used to look up to the Exchange team at Microsoft. They used to be the best coders in the world, hands down. Nowadays they seem to released half-finished code. The latest spat of versioning all the rollups is downright unacceptable. Looks like it is going to be even worse with 2013 because it won't integrate with current 2010/2007 installations, and there are features missing left and right (ex. message tracking missing from GUI, etc).

    Get your act together at Microsoft! Exchange is going way downhill nowadays and this is not acceptable. You need to push back any RTM until a proper job can be done testing your products. The onld joke of "you can't deploy a Microsoft product until at least SP1" is really ringing true lately.

  21. T.T. says:

    Calm down folks.

    With an email system such as Exchange that has the largest market share, it's impossible to test EVERY possible problem that may arise.

    I do think the security updates should be separate, but depending on the components in Exchange that is affected it may easier to streamline it through a UR.

  22. Paul N. says:

    I'm curious about the 5-try post-migration mailbox cleanup and the "Failed to clean up the source mailbox after the move." issues.  They've been around for a while now, and while the "Failed to clean…" message is potentially harmless, it's like "Crying wolf"; I'll ignore these messages and the ONE TIME I get a legitimate one it will go unnoticed.  

    The 5-try thing just adds additional time to a mailbox migration which is unnecessary and tedious.  

  23. Randall Twoman says:

    We're on Exchange 2007. Recently we decided to update to Rollup 8. Then, Microsoft recalled that rollup and issued a V2. We were like, okay, well, mistakes happen. Then they recalled that one and issued a v3. At this point we were all WTF is going on with QA at Microsoft? Now we find out that we can't buy Exchange 2007 or 2010 SA licenses anymore because 2013 has hit RTM. The catch is that we can't implement 2013 until 6 months from now when Microsoft decides to implement a patch that co-exists with their own products. We all (all 9 admins at my company) think Microsoft is losing it and the quality of their products are starting to decline.

    I'm sure within a week we'll hear that this new rollup 9 was recalled and a v2 of it was released as well. We're getting scared to deploy updates now. What is going on in Redmond that is causing all these problems?

  24. John says:

    Where is the rollup for Exchange 2010 SP3? What, no love for people running the latest service pack?

  25. Not a chance says:

    At the rate things are going lately, I fully expect to see these rollups removed and replaced in a few weeks with another incremental version update. Eventually MS will need to start implementing a new numbering scheme. I fully expect the future to bring "Exchange Service Pack 2, Rollup 9 version 3.4" or something along those lines. Seems like the Exchange team is completely FUBAR on their rollup testing Q and A.

  26. Exchange 2010 SP3 rollup 5 is missing from the list says:

    Is there a Rollup 5 available and you forgot to include it in the above list, are the updates already included in rollup 4v2 and we don't need to worry about it, or did you forget about the majority of your customers running the latest service pack and rollup?

  27. Riccardo Moretti says:

    Enough already, I agree with Paul Bendall

  28. Bharat Suneja [MSFT] says:

    @Exchange 2010 SP3 rollup 5 is missing from the list: Exchange 2010 SP3 is not released yet. The above list includes all Exchange versions + Service Packs currently supported – Exchange 2010 SP2, Exchange 2010 SP1, and Exchange 2010 SP3.

    Note, the vulnerability mentioned in security bulletin MS12-080 does not impact Exchange 2013, so there is no security update for Exchange 2013.

  29. I agree with Paul too! says:

    Microsoft should NOT be releasing rollups that introduce new features along with critical security updates. The constant releasing then pulling rollups is getting to the point where we are all starting to roll our eyes when a rollup is available wondering when they'll eventually pull it and re-release it again.

  30. R.T.B. says:

    Shouldn't Microsoft be spending all their time on fixing Exchange 2013 deficiencies, rather than continually playing the three card Monty rollup shuffle every few weeks?

    IMO Microsoft should stop everything they are doing and move up the Exchange 2007 and Exchange 2010 integration patches for co-existence with Exchange 2013. Then, they should focus all their effort on fixing all the items they left out of the RTM. The only thing that Microsoft should be doing with rollups now is fixing bugs, not implementing new features that have obviously not been tested thoroughly enough. Paul Bendall is exactly spot on correct.

  31. I don´t worry says:

    about security fixes in rollups or not – I protect lot's of Exchange Servers with TMG 2010 and it's worthmentioning pre-authentication and NIS-Protection. Believe me, have an eye on this!

  32. Ed Steward says:

    Oh great. Another round of patching the broken patches. Now, we have patches for the patches that fix the broken patches. Brilliant!

  33. John says:

    MS wants everyone on Office 365, but just 3 weeks ago Office 365 was DOWN 13 hours.

    Why not focus on giving us WORKABLE RUs for On-Premises instead of focusing on Office 365 so much………….

  34. TeFrog says:

    OK, whether we like it or not, wer'e stuck with the current release situation.

    I'm interested to hear from anyone who has actually installed the new Rollups and how they got on.


  35. Nightmare!!!!! DO NOT UPGRADE!!!!! says:

    TheExchange 2007sp3ru9 not finish install after 3 hours. Fortunate on a server with no mailboxes. Exchange IS and SA refuse to run errors in log. we are calling the phone with PSS.

    Way screw up Exchange RU! DO NOT UPDATE!!!!! WARNING!!!!!

  36. Same problem... says:

    We're having the exact same problem with RU5v2 that we had with the original RU5. The store.exe is crashing. Good thing we decided to test this on a restored VM. Microsoft, what is the problem with getting these rollups right? You are seriously sucking lately.

  37. Phil says:

    @Same Problem

    Not seeing any issues here with RU5 V2, so you may have some obscure local DB corruption issue?

  38. ahwc says:

    my concern for these Rollup is .net image takes way too long.  Anyway to speed that up?  

  39. Gary lee says:

    This update does not install. Gives an error. Anyone else have this issue?

  40. LMLIII says:

    Has anyone installed this rollup who is having the mailbox moving issue?  I am curious to see if this rollup addresses it or not.  I jsut opened a case with MSFT support and their email to me last night said that the only workaround is to roll back to RU2 and wait for SP3.  Something just isnt right here

  41. Kim B says:

    Do we still need to install MS12-080 if we already implemented the workaround  below?

    Set WebReadyDocumentViewingOnPublicComputersEnabled to $False

    Set WebReadyDocumentViewingOnPrivateComputersEnabled to $False

  42. WeetA says:

    For people having problems to install those rollups, verify that you didn't install Windows Management Framework 3.0 (Powershell 3.0)…/caution-kb2506146-and-kb2506143…/windows-management-framework-3-0-powershell-3-0-and-exchange.aspx

  43. Mr. Session Affinity says:

    @AHWC you can shutoff CRL checking through the browser (in IE Tools>Internet Options>Advanced under security section uncheck the box next to check for publisher's certificate revocation)

  44. ryan says:

    So, what do we do if we've installed the PS3.0 update? Do we need to remove that before we can install these new updates? Can we re-apply the powershell 3.0 update afterwards?

    This is just crazy that updates are being recalled and republished, updates are breaking other updates, and we have to manually disable certificate revocation checking. No offense, but this is crazy.

  45. TeFrog says:

    I've just installed Rollup 8 for Exchange 2010 SP1 on an SBS2011 server using WSUS, and it went fine.  Took about 15 minutes to do the update, then required a reboot to complete.  Good luck to anyone else.

  46. says:

    Wasn't this vulnerability in Webready document the same as Microsoft Security Advisory 2737111 ?

    Back then, the "fix" was to disabled the webreadyvieweing, works fine for my an my 4000 mailboxes. Gladly running Exchange 2010 SP1 UR6, and i have no intentions to put my exchange user base, to the mercy of bad quality and testing from Microsoft again, I was going to go to SP2 finally, until i saw we're back to issues instead of fixes..

    Come on Microsoft, i still have faith, but geez, it doesn't seem the high level managers are reading this blog, how can they let the coders release a patch that is supposed to improve the exchange environment, introducing issues different than the ones the patch is supposed to fix, and not once, which would be ok, not twice, (which should raise flags with Q&A managers, but as many times you guys have released an RU. Are the high level managers this blind at Redmon ? is anybody at redmon reading this blog, listening to us, and doing something to prevent this "little mistakes" ? Dear Microsoft,  we're beeing forced to install an Exchange RU and a security update in the same package, you bet is going to break stuff up. , this is unacceptable for us , should be unacceptable for Q&A at Microsoft, Please, Please fix this RU's once a for all, don't release another one until you guys get the next one straight.

    In the meantime, can we get away with the webreadydocument disabled ? my users don't mind this feature at all. And my environemnt would be happy i'm not installing another nightware Exchange RU

    This is the simple PS command i ran months ago, and it seems it would stay this way until who knows when.

    Get-OwaVirtualDirectory | where {$_.OwaVersion -eq 'Exchange2007' -or $_.OwaVersion -eq 'Exchange2010'} | Set-OwaVirtualDirectory -WebReadyDocumentViewingOnPublicComputersEnabled:$false -WebReadyDocumentViewingOnPrivateComputersEnabled:$false

  47. Yuhong Bao says:

    To the commenters here: Exchange never had GDR/QFE branching, so Exchange 2003 security updates are similar, just they do it at the file level instead of the product level.


    This has been asked MULTIPLE times now and no answer – HAS THE 5 RETRY UPON MAILBOX MOVES BEEN FIXED?  Or are MS even looking at it?  3 rollups later a major bug still exists and it affects mailbox moves.  How can this not be on a list of things to fix or at least acknowledge in a KB article?  Seriously?

  49. Nope says:


    It doesn't appear it has been fixed. I loaded the latest rollup in our lab, moved some test mailboxes, and still noticed the same retry problem. Apparently Microsoft is ignoring this issue/bug – or at least they have not placed very much importance on it being fixed.

  50. says:

    I'd say it has already almost been fixed. In your MSExchangeMailboxReplication.exe.config you can set the "MaxCleanupRetries" to 1 (instead of 5).

    We tried with 1 and 2.

    Result: Lots of move errors.

    So we switched back to 5.

    Why do you call it a "major bug"? Compared to what M$ is delivering at the moment (v2s, FW3.0) it's a negligible glitch…


  51. Brian says:

    For us this update broke OWA. Had to roll back to RU4v2 and recreate virtual directories. Tried recreating them before rolling back and that did not work

    Also the Move mailbox error still persists.

  52. I hate you, Microsoft! says:

    This is the second time we've had to uninstall a rollup. Just installed 5v2 and surprise, surprise, IIS appears to be royally screwed. Fortunately I took a snapshot right before the update and was able to restore. I would like to plead with people to test everything the Exchange team is releasing in a test environment before deploying it into production. Apparently the Exchange team can't figure out how to update servers without breaking them.

    What a complete disaster these rollups have become. The Exchange team sucks royally and need to get their sorry act together, FAST.

  53. Craig says:

    Update Rollup 5-v2 for Exchange Server 2010 Service Pack 2 has wrecked a customers OWA. Just a blank screen.

    Hopefully uninstalling will fix it.

  54. Larry Groman says:

    Same here. OWA completely stopped working after applying the version 2 rollup 5. Blank page. Any ideas on how to fix this problem?

  55. Mark W. Mathers says:

    We've had a number of issues lately with our Exchange. First, we had to uninstall the PS3.0 update. Now our IT dept is testing the Ex2k10sp2ru5v2 and everything seems okay except for the OWA. When we test going to the OWA, we just get back a blank page. All the certs are installed correctly and we didn't change anything other than apply the ru5v2 update. Uninstalling the update fixed the issue.

    Two questions:

    1. Is there a fix to this issue and/or a workaround to make OWA work?

    2. Will there be a 5v3 coming out to fix this problem?

  56. Bharat Suneja [MSFT] says:

    @Mark W. Mathers: Please contact Support. This is not a known issue at this time.

  57. Mark W. Mathers says:

    Dear Mr. Suneja, With all due respect there are at least 5 other people commenting on this forum with exactly the same issue. saying "this is not a known issue" is really insulting our intelligence. Are you really trying to tell us that nobody at Microsoft has seen this issue? We're the only ones? Comeon, that's not going to fly. Contacting Premier support will require hours of waiting for someone to call us back and more hours trying to resolve things. We don't have time for that. This is production. We just want it to work. So far 4v2 works and 5v2 does not. It's not up to us to beta test your updates and get them working. They should work right out of the box, which they don't

  58. Bharat Suneja [MSFT] says:

    @Mark W. Mathers: Sorry you're having trouble. Blog comments are a good way to provide feedback, but they can't replace the Support function. Support engineers can collect information about your environment, help you troubleshoot an issue and provide a resolution, escalate issues as required.

    There have been a few comments here, which do alert the product team and Support, and prompt an investigation, but given the installed base and wide variety of environments Exchange is installed in, it's not always possible to determine root causes without getting more details.

    If we knew for sure that every RU5 v2 installation produces a blank OWA page, you would already read about it here on EHLO and the RU would likely be removed – it does not matter how many versions of RU we already released.

  59. says:

    I've just done a new installation of Exchange 2010 SP2. When I checked my WSUS server for updates, it showed:

    "Update Rollup 4-v2 for Exchange Server 2010 Service Pack 2"

    "Update Rollup 5-v2 for Exchange Server 2010 Service Pack 2"

    Surely I shouldn't need both? I've just installed the new one (UR 5-v2), but when I check again for updates it still thinks that I need UR 4-v2.

  60. Bharat Suneja [MSFT] says:

    @JohnKirkHMR: Starting with Exchange 2007, Exchange Server updates have been cumulative. You can install the latest – it contains all fixes in previous updates. More in Servicing Exchange 2007.

  61. says:

    Bharat – thank you for your reply. Based on that, I think there's a bug in UR 5-v2. Looking at my WSUS server, UR 4-v2 supercedes UR 4 and UR 2. However, UR 5-v2 only supercedes UR 2. (All these version numbers apply to Exchange 2010 SP2.) Presumably UR 5-v2 should also supercede UR 4 and UR 4-v2, because they're cumulative. Since it's not marked that way, that means that my Exchange server thinks it still needs UR 4-v2. I can ignore it, but it would be better if it didn't show up in my list.

  62. Bharat Suneja [MSFT] says:

    @JohnKirkHMR: Thanks for letting us know – we'll have that checked.

  63. says:

    @Bharat Suneja ("Blog comments are a good way to provide feedback, but they can't replace the Support function"): Well then – please give us something else to replace MS support. Time is up.

    @Mark W. Mathers (et al): Thanks for sharing – we'll wait a bit…

  64. susan says:

    To Mark Mathers – they cannot fix what they cannot repro.  Comments on a blog do not equate to the ability to understand what is going on to fix an issue.

    Blogs are commentary… they are NOT case repro.  You have to open a support case.

    Email me at (take out the -) and I'll set up a case for you.

  65. Chuck Lavin says:

    How many dozens of hours does it take for a SBS 2011 server to install this Update Rollup 5-v2? The server was presented this update via WU at 11 p.m. LAST NIGHT. It will shortly be 7 a.m. and the server shows no sign of finishing this update any time soon.

    I had the same problem installing the Exchange 2010 SP2 update. Exchange was down for a full day while we waited for the SP to install — an installation that had also begun at 11 p.m.

    How can it take 10-12 times longer to install the update than it took to install the original package?

  66. says:

    @Chuck Lavin: Are you sure CRL checking is disabled?

  67. says:

    @Chuck Lavin: Are you sure CRL checking is disabled?

  68. DITSupp says:

    I also think there is a bug somewhere as I've installed RU5v2 and it's still telling me to install RU4v2 like @JohnKirkHMR.

    Also if you check the version of EMC it says: 14.02.0328.009 but after RU5v2 is installed it should be 14.02.0328.10. Bug or am I missing something? I was under the impression these were cumulative.

  69. Mickhael G. says:

    We applied 5v2 to one of our Exchange 2010 SP2, rolup 4v2 servers today running the CAS and HT roles. It literally took 4 hours to run. We did verify that the IE check certificates was unchecked (the update informs you of this condition if it isn't selected). After it ran, OWA stopped working. It just displayed a "page could not be displayed" error. The second (and fortunately active) CAS server did not experience any issue. Since we could not confirm the update was applied successfully, we uninstalled it (which fortunately only took like 10 minutes). A reboot later and OWA started working again. There is definately a problem with rollup 5v2. Do we need to update all of the CAS servers in the org in order to have OWA work? Why did applying the update take so long? What did we do wrong? We really want to get the latest updates installed, but we need OWA working.

  70. says:

    Sounds more and more like "wait for v3"…

  71. OWA blank page after installing the rollup5-v2 says:

    I also had OWA blank page after installing the rollup5-v2. from what i read, this also happened to others installing previous rollup.

    To fix the OWA blank page, I ran native script updatecas.ps1 on both our CAS server and OWA worked.


  72. Johnny on the spot says:

    From what I'm reading, can anyone confirm that we need to perform the following in order to successfully install Rv2:

    1. We need to not install the PS 3.0 update that is being offered. If we've installed that update, we need to uninstall it.

    2. We need to go into IE and change the certificate revocation checking.

    3. We need to plan on an extended multi-hour outage to install the rollup.

    4. If the OWA doesn't work, then we need to run updatecas.ps1 from the BIN directory to fix the issue

    5. We'll need to ignore our WSUS recommendations that will suggest we apply the older 4v2 update after installing 5v2.

    6. The patch still misses a number of needed fixes including the 5x mailbox issue.

    7. Even after we install the latest updates we still need to wait another 6 months in order to deploy Exchange 2013. We'll need to install SP3 for that functionality.

    Is that all correct? You'd think this would be simple, but it appears to be a complete boondoggle to get right.

  73. Bharat Suneja [MSFT] says:

    @Johnny on the spot: If you've installed RU5v2, you will not be able to install RU4. Understand Windows Update/MU is displaying that even after you install RU5v2.

    The OWA blank page issue is not the general experience. As of now, there are no escalations related to this issue. If you do experience it, please contact Support to troubleshoot.

    Having installed RU5v2 on a bunch of servers, I personally haven't seen an issue with CRL checking nor long install times or the OWA blank page issue.

    WRT coexistence with Exchange 2013, Exchange 2010 SP3 and Exchange 2007 RU for coexistence were earlier announced for a H1 2013 release and recently narrowed down to Q1 2013. You will not have to wait 6 months. See Exchange Server 2013 Reaches General Availability.

  74. Bry says:

    Doing a quick google for updatecas.ps1 implies that OWA breaking after this update is not specific to this update. Seems it has broken for a few people before with previous updates.

    So while it maybe an issue it seems to be more of a long standing one than being specific to this update

  75. julie says:

    @Bharat – Chalk up another OWA issue with the new 5 rollup. Escalation schmescalation I say. updatecas.ps1 made everything happy, but if it was a known issue requiring the updatecas.ps1 script to need to be run, why has the Exchange team not fixed it? Is every release going to contain weird updates and post installation tweaks to the updates just to get the updates to work correctly?

  76. XIII says:

    The update worked for us, but just to confirm what other people are saying it took a little over 3 hours to finish installing. This happened to both of our CAS/HT servers. We are going to run it on our MB servers in a DAG next. This is a ridiculously long install.

  77. says:

    Thanks everybody

    I ran native script updatecas.ps1

  78. says:

    HI all,

    just wanted to share my personal experience.

    We are in the middle of a 2007 -> 2010 migration now. Everything virtualized.

    When I installed the first 2 CAS/HT combined systems, i noticed the following:

    When installing Ru5v2, the machines give a s*** whether you enable or disable CRL checking, the only thing that really speeds up the process is to allow the machines unfiltered internet access. (We sniffed with wireshark, lots of traffic to M$). Internet acccess is easy for Edge, HT, CAS but later on when installing it for MBX it might get complicated.

    After installing RU5v2, OWA was broken, running the mentioned script updatecas.ps1 and rebooting both machines helped to fix it again.

    After said reboot, wsus is still offering us RU4v2.. Why haven't nobody at M$ noticed that? Aren't you using WSUS at home? Those servers where fresh installed.. somebody should have noticed that! I'm pretty sure that @JohnKirkHMR is right with his assumtions of which RU superseeds which… FIX THAT!

    When Installing the MBX systems, I noticed the following:

    You wait hours when the machines doesn't have inet connection… we tried with 4 servers.. no inet, no crl, and all combinations. Forget CRL settings, give full unfiltered internet access. In that case RU5v2 install took 14 mins.

    Also, WSUS wants us to install RU4v2 on all the MBX machines after RU5v2 installation.

  79. @Sebastian: Microsoft Update (and therefore WSUS also) always offers the previous RU for a time until the RU is made available on MU/WSUS instead of just manual download. Until the package is released to MU the service does not know there is a superseded update and it will offer the most recent one it knows about.

  80. AA says:

    Sebastian, you nailed it! It appears there is a major problem installing 5v2 if there is no Internet connection. We have 2 CAS/HT and 2 MB-DAG servers. The CAS/HT upgraded in less than 30 minutes. The first MB server took over 5 hours. We are planning to do the second MB tonight because at 5 hours we completely blew our maintenance window.

    What we are noticing is that the CAS/HT servers have a direct Internet connection and the MB servers do not. They have to route through the barracuda as a smart host. That would indicate that Sebastian is exactly correct when he says that the 5v2 rollup requires an active Internet connection to be available or you're going to spend hours and hours installing the update.

    So, my question to Microsoft is, do all rolllups and SP's require that all servers have direct Internet connections in order to install correctly now? Also we're seeing the 4v2 rollup appears now, but have told it to be ignored. I can see that causing confusion as well.

    Does anyone actually test these updates before posting them to the Internet? You'd think after the "v2" release things would be working right, but there still seem to be bugs and problems.

  81. Quazar says:

    RUs became bigger threat than virusses and other attack as RUs causing more problem and risk. If there is a security issue, it should be fixed with a dedicated patch. I start considering these releases MS attacks to our systems.

  82. susan says:

    @Brian Day — no we really mean that once you install the latest update WSUS and MU offer up the prior one.  It's a detection issue that several folks are reporting along with Sebastian above.

    Stand up an Exchange server and patch it, you'll see what he's talking about.

  83. says:

    @Susan: I saw the same behavior on one of our test Exchange servers.  I installed RU5v2 and the server was still offering two previous Rollups via our WSUS server.  I hid them to keep them from installing.  I can't find them this morning, after our winter break.

  84. says:

    P.S.  We've had two Exchange servers hang on reboot after uninstalling KB2506143.  Consoles show them stuck on the "Preparing to Configure Windows…  Do Not Turn Off Your Computer" screen.  We just reset them, and on one servers so far, it is back working fine and with KB2506143 removed.

  85. Petri X says:

    Did you made any changes to the prepare-moverequest.ps1 script, especially for the attribute copy process. Because now the script copies x500 address to source object and it is not anymore able to find local objects, but creating new object all the time. With cross forest scenarios.

  86. Petri X says:

    Forget my last comment, thanks :)

  87. Mary L says:

    Has any one who applied either RU4V2 or RU5V2 had any issues with blackberry devices where there is a burst of messages after a brief delay in them getting to the devices?

  88. pesospesos says:

    just did another 2007 to 2010 migration and we are back to sp2 because ru5v2 sent the indexing into a hellish spiral.  need to get at least ru4 installed to fix the iphone reply flag issue right?  so is there any compelling reason to install 5 or should we stick to 4?  not that 4 doesnt' have plenty of issues…

  89. Chris says:

    Doing an install of Ex 2010 (for a 2007 upgrade). I installed a fresh server, fully updated it, installed Ex 2010 SP2 with the UR5v2 .msp in the updates folder and all went ok….. until I run Windows update again and find UR4v2 sitting in the list. Checked Programs list and UR5v2 indeed installed. I then uninstalled UR5v2 thinking it may have been a problem with installing it as part of the installation of Exchange. Ran Windows update again after a reboot and both UR4v2 and UR5v2 are sitting in Windows updates to be installed. (same problem as a few people on this thread). I'm letting Windows update do it's thing and so far it has installed UR5v2 and it is now trying to install UR4v2. I thought UR5v2 should supersede all other update rollups?

    After reading the comments in this thread, I am now very concerned at the state of Exchange patch testing and confused as to what UR level I should actually install.

  90. Chris says:

    Update from last post…..

    Both UR5v2 and UR4v2 seem to have installed now and are showing up under the Updates section in Programs and Features.

    However, because UR5v2 installed first, then UR4v2 installed after, I am wondering if UR4v2 install has replaced some of the UR5v2 files? MSFT please comment!

  91. Paul N. says:

    @Brian –

    The newest Update Rollups do supercede old ones.  Windows Update is goofy in the way it detects Exchange URs.  As a matter of fact, you NEVER want to install Exchange Update Rollups via WU because if there is an issue with another running .NET application you'll never know about it, whereas if you install from the .MUP you'll get a message about a process running that is preventing libraries from being updated.  

    In all, there is no need to have RU4 and RU5.2 installed.  Since you may have issues with the order they were installed I would advise removing both, rebooting, then ONLY install 5.2.  

    Good luck.  

  92. 127 says:

    anyone knows why these do not overrule (by WSUS and MU)

    2010 SP2 UR4-v2 (UR5-v2 decripted as rollup UR2 only)

    2010 SP1 UR7-v2 (UR8 decripted as rollup UR6 only)

    2007 SP3 UR8-v2 (UR9 decripted as rollup UR6 only)

  93. Perfomance Problems... says:

    We're having massive Performace Problems with our Server and Outlook Clients, after installing RU5-V2 on our CAS and MB Servers.

    The store.exe is having very high CPU Utilization and the Clients are "hanging" or showing the pop-up "Outlook is trying to retrieve Data from…."

    We are running the Servers in an VM 5.0 Environment and already increased the RAM on the MB Sever to 32 GB and added up to 4 CPU Cores … but still having Problems during the day.

    Is anybody else having these Problems ?

    We're already thinking about removing the RU5-V2 next weekend again …

  94. Ray P says:

    In the prereqs, it says we need to remove any previous Exchange updates installed? Do we really have to go and unsistall any exchange updates and RUs before? Has anyone done this or not? what is the difference and why is it a "prerequisite"?

  95. Bharat Suneja [MSFT] says:

    @RayP: No. Update rollups are cumulative and subsequent rollups can be installed without having to remove previous ones.

    What the
    section in KB 2785908:

    To apply this update rollup, you must have Exchange Server 2010 SP2 installed.

    Note Remove all interim updates for Exchange Server 2010 SP2 before you apply this update rollup.

    Interim updates are any hotfixes Support may have provided you to fix a specific issue (between rollups). Interim updates need to be removed. Most customers are not likely to have any interim updates installed.

  96. VLuu says:

    I have been experiencing high CPU on our CAS servers affecting users retrieving free/busy and mail delivery for MAC users. The IIS application pool MSExchangeServicesAppPool is the culprit in my case, consuming the CPU. Do have a ticket open with MS Support but no resolution yet.

  97. Reid_G says:

    Update Rollup 6 for Exchange 2010 SP2 released today.

    Will there be a new blog post for comments or should we continue our success and failure stories for RU6 here?

Comments are closed.

Skip to main content