Released: Update Rollup 5 for Exchange 2010 Service Pack 3 and Update Rollup 13 for Exchange 2007 Service Pack 3

The Exchange team is announcing the availability of the following updates:

Exchange Server 2010 Service Pack 3 Update Rollup 5 resolves customer reported issues and includes previously released security bulletins for Exchange Server 2010 Service Pack 3. A complete list of the issues resolved in this rollup is available in KB2917508.

Exchange Server 2007 Service Pack 3 Update Rollup 13 provides recent DST changes and adds the ability to publish a 2007 Edge Server from Exchange Server 2013. Update Rollup 13 also contains all previously released security bulletins and fixes and updates for Exchange Server 2007 Service Pack 3. More information on this rollup is available in KB2917522.

Neither release is classified as a security release but customers are encouraged to deploy these updates to their environment once proper validation has been completed.

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

The Exchange Team

Comments (66)
  1. Nino Bilic says:

    @Siddique – the needful has been done. Note that we know that articles are not showing up for some, working on that.

  2. @Rowbby, you’re welcome. I’m personally unaware of any plans for additional changes in that area.

  3. Anonymous says:

    I appreciate CDugger13’s post above. That allowed us to pre-emptively collect the list of users who had access to other mailboxes, cross-reference it to their Outlook 2010 build, and deploy Outlook 2010 SP2 as-needed prior to our SP3 UR5 deployment. No issues reported by those users. I’m personally using Outlook 2013 15.0.4569.1503 and I can still access the same three shared mailboxes I had prior to the SP3 UR5 upgrade.

  4. @Rowbby, please check out the update made to the supportability matrix today. If you don’t yet see the 2012 R2 line then the content delivery network may still be replicating the change. Exchange 2010 SP3 RU5 or later will be supported with 2012 R2 DCs as well as the 2012 R2 DFL/FFL.

  5. Anonymous says:

    Does the RU5 for E2010 SP3 apply on Windows Server 2008 SP2 (not R2)?
    The download page does not mention it within the Supported Operating System. I guess this is just a miswriting.

    If not, which policy should be annouced to the customers having no plan to upgrade soon the OS of their Exchange server at the moment:
    -stick to RU4?
    -which support?


  6. Nino Bilic says:

    @ Anonymous – thank you, we are aware that articles are still in the process of settling in the publishing system. Should be resolved soon.

  7. Anonymous says:

    @John DArcy — We run Outlook in cached mode; however, we have disabled caching of shared mailbox folders ( Do you know if the Category View issue will affect the shared mailboxes folders since they are not cached, even though the rest of the mailbox is? We have quite a few users that have these shared mailboxes automapped…

    @Brent Alinger [MSFT] — Can you provide any clarification on the question above.

  8. Anonymous says:

    Not sure what happened, but I was able to fix the issue with advanced search by running the “ResetSearchIndex.ps1” script on all 34 of my databases. Not ideal, but not the end of the world either. — Dulce

  9. Anonymous says:

    Any news about Exchange Server 2010 SP4?

  10. Anonymous says:

    Same problem at Outlook 14.0.7116.5000 (32-bit)
    So Outlook 2010 SP2

  11. Anonymous says:

    Caution if you still have clients running Outlook 2010RTM or SP1!!!

    Has anyone else experienced an issue with Outlook 2010RTM/SP1 and Auto-mapped mailboxes after updating to Update Rollup5? Exact Error is “The set of folders cannot be opened. The attempt to log on to Microsoft Exchange has failed.”

    Users can no longer open any mailbox that is auto-mapped when using a client version Outlook 2010RTM or SP1. Using Outlook 2007/2013 functions OK. If you have the end-user manually add the mailbox to Open additional mailboxes it will show twice within Outlook, one will open and one will not work.

    When I pulled UR5 off the CAS the clients functioned normally again. Opened case with M$ and found there is a compatibility issue with Outlook 2010RTM/SP1 and Update Rollup 5 and the problem was resolved by updating the Outlook 2010 client to SP2.

  12. Released: Update Rollup 5 for Exchange 2010 Service Pack 3 and Update Rollup 13 for Exchange 2007 Service Pack 3
    thank you

  13. Anonymous says:

    Hi, we also have this problem of not opening a shared mailbox in outlook 2007 sp3. So it seems that this problem is more wide spread.

  14. @fr, in my lab Exchange 2010 SP3 RU5 is not requiring IE11 compatibility mode to show the Automatic Reply configuration area. I made sure the “use compatibility mode for intranet sites” setting was disabled in IE11 before testing.

  15. @Frank, trust me… you would know you had an IU if you had one. :) An Interim Update is a ‘mini’ update provided directly to a specific customer for a specific critical issue they may be experiencing if the fix is not yet publically available yet will be in the next public update. You can leave RU4 installed and install RU5 right over it.

  16. Anonymous says:

    How about the categories view bugfix? UR5 didnt seem to cover this one. Is this in the works? Thanks

    Folder views are not updated when you arrange by categories in Outlook after you apply Exchange Server 2010 Service Pack 3 Update Rollup 3 or Update Rollup 4

  17. Nino Bilic says:

    @JB-RI – fixed, thank you!

  18. Anonymous says:

    We will be updating from SP2UR4v2 to SP3UR5 mid-April. Does Microsoft maintain a public list of known issues which are either 1) previously reported and not yet fixed after SP3UR5 and/or 2) new bugs in the SP3UR5? The only known new issue I can find on SP3UR5 is the category view. If there are such lists, where can I view them?

  19. @Malcom – Yes it is supported. See the system requirements for WMF4.0 –

  20. Anonymous says:

    We’re also having the issue for Outlook 2013 Version:15.0.4605.1003

  21. Anonymous says:

    Hi yes i agree to what #cdugger13 said, its same issue we are facing, Please fix this ASAP, we have number of users facing this issue. Auto-mapped Mailboxes are not working since we updated to rollup 5, Error is, “The set of folders cannot be opened. The attempt to log on to Microsoft Exchange has failed.” in outlook client when user tries to access that auto-mapped mailbox.

  22. Anonymous says:

    Thank you for your input, Jason. We often seem to be “lucky” this way. I am going to look into various possibilities. It was just very coincidental – applied the update and advanced search stopped working right.

    I did some more testing here and I see that we do get results in advanced search – but no results after the update. Any results are messages received before the update. So if “Smith, Joe” sent me two messages, one on Friday the 28th before the update, and one on Saturday March 1 after the update, if I search on FROM:SMITH advanced search only displays the one from Friday. A regular search gives both.

    If anyone has any thoughts on how I might fix this, I am open to suggestions. Thanks, Dulce (pcpix)

  23. It would have been nice if the Internet Explorer 11 compatibility fix could have been included in the Exchange 2007 update. I know Exchange 2007 is now beyond mainstream support, but since non-security updates are clearly still being released, something that would improve usability on systems running IE11 would have been appreciated by those of us still stuck on 2007 with client systems running the new browser.

    Since users can only add entire domains to Compatibility View via the IE GUI, it also affects some of our other web-based apps, which break since they aren’t designed to work with the old version of IE that is emulated. Adding the specific OWA sub-domain via group policy is not an option in our environment, nor is documenting the local group policy setting and expecting end-users to be able to do that on their own.

    I would ask that Microsoft reconsider this since Exchange 2010 and 2013 were supplied with a server-side fix and 2007 will realistically be in use in many places for years to come.

  24. Anonymous says:

    I applied RU5 to my Exchange 2010 SP3 system on Saturday. I had no issues with the actual installation.

    Yesterday, some of my more savvy users reported that the advanced search feature in Outlook 2010 no longer worked properly. An ordinary search for “Smith, Joe” works fine, but of course brings back every message referencing “Joe Smith” including those where the name is in the body of the message. However, when an advanced search for FROM:Smith is performed, the results stop on Friday, the day before I applied the update. Nothing received after that appears in the advanced results, only in the basic results.

    Is anyone else seeing this? Any ideas on how to fix it? I only updated one of my database servers, so my temporary solution was to move all the databases to a different database server (at RU4) and now the search works. The two database servers are identical in every way, including installed Microsoft updates, except for RU5.

    Thanks for any help.

  25. Anonymous says:

    KB2917508 appears blank when trying to be viewed. Please fix.

  26. JB-RI says:

    Both the links point to the 2007 patch

  27. adam says:

    Great stuff! We’re pleased that we can start deploying 2012 R2 Domain controllers in production and then commence our Exchange 2010 -> 2013 migration. Did you find any incompatibilities with 2012 R2 DCs and previous Exchange 2010 updates? I know of at least two companies with this unsupported setup.

  28. Siddique says:

    Link for Update Rollup 5 for Exchange Server 2010 Service Pack 3 opens up download link of Update Rollup 8 for Exchange Server 2010 Service Pack 2. Please do the needful.

  29. Tim says:

    Is the Chile DST change included in 2010 patch or did this miss the window?

  30. Frank says:

    The KB article states: Important Remove all interim updates for Exchange Server 2010 SP3 before you apply this update rollup.

    What is considered an interim update? Does that mean uninstall RU4 first?

  31. fr says:

    Does UR5 include a fix for IE11 still requiring compatibility view on certain settings pages in OWA such as Automatic Replies?

  32. Rowbby says:

    Will there be an update for Exchange 2010 to support deployments on Windows Server 2012 R2 DCs? Can understand Exchange 2013 compatibility was the higher priority, but as it’s still in mainstream support would be good to know if Exchange 2010/Server 2012 R2 is coming or is a firm no.

  33. Rowbby says:

    @Brian: Thanks for the reply. In the supportability matrix for “supported operating system platforms”, the only X for Window Server 2012 R2 is Exchange 2013 SP1. I’m interested in Exchange 2010 installations on Server 2012 R2, not just coexistence. The matrix (unless I’m seeing the old one) seems to indicate that combination is still not a possibility. Just wondering if that’s final (i.e. support will not come in the future). Thanks!

  34. Rowbby says:

    @Brian: Ok, so officially Exchange 2010 installations on Server 2012 R2 are not and will be never supported? Just looking to get some final clarity as I’ll move ahead with Exchange 2013 if it’s decided that Exchange 2010 will never be supported on 2012 R2. Thanks again!

  35. @Rowbby – We have no plans to support Windows Server 2012 R2 as the OS used for Exchange Server 2007 or 2010 deployments.

  36. Jason says:

    Just installed RU5 in my 2010 SP3 test env. Confirmed that IE11 looks good now. Doesn’t require compatibility mode for setting out of office replies. I don’t use the test environment for anything much. Our prod env is still on 2010 SP2 RU5v2.

  37. fr says:

    @Brian & @Jason thanks for confirming

  38. malcolm says:

    While the supportability matrix for Exchange 2010 SP3 UR5 shows that Powershell 4.0 is now supported, there is no other document, including KB2917508, which details it as a new available option. Can we get details on its support and inclusion? As much as I like Powershell, this minor tidbit did not escape me, but I’d really like confirmation that it’s not a typo – one tiny checkbox in a supportability matrix is the only place it is mentioned, and not in the KB. Thank you!

  39. 127 says:

    when we can expect These UR on WSUS ?
    As well will be WMF 4 be released on WSUS later on now ?

  40. Anonymous says:

    I second John DArcy’s question. I haven’t installed RU 3 or later because of this (and other) issues. It looks like most of the others have been finally ironed out, but this one would generate too many trouble calls.

  41. @John Darcy – We are still working on a fix for the issue identified in KB2925273.

    @127 – RU5 will be available via Microsoft Update on March 11th.

  42. Oli says:

    We are still waiting for a fix for this really annoying EAS sync bug:
    Issue 1.9 – An appointment does not update when you use Outlook in cached mode and room mailbox is an attendee

    Please promote [REG:113111310943037] Callback:IPhone Calendar Sync Problem with Outlook

    Any news?

  43. Jason says:

    Anyone have 2010 SP3 RU5 in production env yet? Any major issues, concerns, etc?

  44. @127 – The Microsoft Update release date has been pushed to 3/22 due to a schedule change.

  45. Geezbill says:

    “Setup Wizard for Update Rollup 5 for Exchange Server 2010 Service Pack 3 (KB2917508) ended prematurely” any ideas?

  46. Dulce says:

    This may or may not be related to Exchange 2010 SP3 update Rollup 5 – I deployed it on Saturday. No installation problems on Exchange, but now some of my more savvy users are reporting that the advanced search function in Outlook no longer works. In other words, a basic search for mail from Smith, Joe will bring up any mail related to Joe Smith including mail where he is mentioned in the body of the message, etc. An advanced search using the From:Smith function only brings up mail dating back before the update. We are using Outlook 2010.

    Is anyone else seeing this? I need to do more research to see if it is related, but it is very coincidental. Any ideas on the best way to fix it?

    Thank you!

  47. Jason says:

    PCPIX, I'm not seeing that same issue in my 2010 SP3 RU5 test env. I'm using a 2010 Outlook client as well. Normal search works fine. Search Tools > Advanced Find and searching anything returns the results. Tried testing search words in the subject field, FROM:, etc. All seem to be OK.

  48. Jason says:

    PCPIX, I sent another email to my test env. and was still able to see it via advanced search (so it was sent after the upgrade). I also tried Outlook in cached and non-cached mode. Still works. Our test env is pretty simple and no where near as complicated as our prod env.

  49. James K. says:

    PCPIX: You may want to look at rebuilding your search index to see if that fixes the issue. I’d just perform it on one of your databases and if you see it is resolved, proceed to the rest.

  50. D2theZ says:

    Well I have been unable to get this update to install yet in my environment. Checking the log it indicates a 1023 error with an additional code of 1603. I have searched on this but so far any mentioned fixes have yet to work. I additionally consulted the LOG file and it seems to indicate I need to uninstall an interim update (we currently have Ex 2010 SP3 Rollup 4). Does anybody this I should try uninstalled a previous rollup to get a new rollup to apply?

  51. Scott says:

    The Support Matrix shows that there is no support for 2012 R2 domain/forest functional levels with Exchange 2007 … any plans for that?

  52. 127 says:

    not arrived @WSUS yesterday

  53. PZ says:

    did an update from 2010 SP3 RU2 to RU5 – now got those category issues.. and another one – Shared mailboxes that are Auto-Mapped in outlook – NOT accessible. ” Cannot Expand Folder. The set of folders cannot be opened. The attempt to log on to Microsoft Exchange has failed.” Re-adding permission doesn’t work… Manually adding mailbox in outlook works fine…
    users are beginning to freak out…

  54. kc says:

    guys, I applied sp3 and then Rollup 5 oever the weekend, everything went well with no issues. This morning, Monday 3-17-14, some of the users reported that their Outlook “tasks” are deleted. I checked mine and it’s all gone. Any ideas what happended?

  55. 127 says:

    both UR arrived on WSUS yesterday

  56. Tim says:

    Updates installed this am and now OWA and active sync aren’t working. Is there anything documenting these issues?

  57. Phil says:

    @JimCass – the category view bug is in Exchange 2010 SP3 RU4 too

  58. Pikehunter says:

    So, just for clarification, can Exchange Server 2010 with SP3 Update Rollup 5 be installed on a Server 2012 R2 system? Brent from MSFT below says it can’t. Prabhat, MS Exchange MVP below that says “yes”.

    Brent Alinger [MSFT] 26 Feb 2014 4:56 AM #
    @Rowbby – We have no plans to support Windows Server 2012 R2 as the OS used for Exchange Server 2007 or 2010 deployments.

    “Microsoft also released Exchange 2010 service pack 3 Rollup update 5 and Exchange 2007 Service pack 3 Rollup Update 13 so that Exchange 2010 and 2007 can be installed on Windows 2012 R2.”

  59. EDDIE says:

    Installing RU5 messed up Content Filtering, as SCL’s werent getting stamped on headers after the rollup. Make sure you re-run AntispamAgents.ps1 after installing RU5.

  60. jan says:

    After install SP3 Rollup 5 we have a problem with outlook 2010 clients with additional boxes, the additional box did not open and give a “can expand the folder, can not open folders the set. The login attempt failed with Microsoft Exchange”,
    i tested there is no problem when use File, open other user, it works OK.

  61. Tai says:

    Is there any news about Exchange Server 2010 SP4 ?

  62. Tai says:

    Any news about Exchange Server 2010 SP4?

  63. Blaine says:

    Even though the system requirements for WMF4 state that it supports Exchange 2010 SP3 RU5, my PowerShell console crashes anytime I run an Exchange cmdlet with the following error: The type initializer for ‘Microsoft.Exchange.Diagnostics.ExTraceConfiguration’ threw an exception. I can only run Exchange cmdlets if I force PowerShell to run at version 2.

  64. Erik says:

    There is a problem with this update. Auto-mapping of secondary mailboxes isn’t working anymore.

  65. Cody says:

    Please, just slipstream it into SP4 for 2010. SP3 has a lot of issues that were addressed in the rollups.

  66. MK says:

    Exchange 2010 Move Requests stuck as Queued after SP3 RU4 install> When will this be fixed.

Comments are closed.

Skip to main content