Update Rollup 9 for Exchange Server 2007 Service Pack 1 has been released

We have released Update Rollup 9 for Exchange Server 2007 Service Pack 1 (KB 970162) to the download center. The release of the rollup via Microsoft Update will happen on July 28.

The majority of changes in this rollup are bug fixes. Here are a few that I would like to call out:

  1. KB 969911 - This is bug likely to affect customers who have deployed the Messaging Records Management feature and have specified a storage limit for a managed folder. After a move mailbox, the property which marks the folders as managed is not preserved.
  2. KB 968621 - Store stops responding under certain conditions when scheduled backup is canceled and online maintenance is in progress.
  3. KB 945877 - Performance improvements to eseutil when it verifies the checksum of transaction logs.
  4. Support for Windows Server 2008 R2 Domain Controllers in the environment (Note: Exchange Server 2007 itself is not supported to be installed on a Windows Server 2008 R2 system.
  5. KB 968715 - This bug is likely to affect customers who have deployed CAS-CAS proxying. When a user selects This is a public or shared computer or This is a private computer on the Outlook Web Access logon page, this value is not maintained  between the CAS servers when the request is proxied. This bug will most likely affect customers with Internet facing CAS sites which proxy the requests to internal sites. Now the bug was that we defaulted to private access irrespective of the option selected by the user. Outlook Web Access has the following features which allow the administrator to control access of users depending on the logon type.:

After deploying this rollup, the logon type will now be correctly maintained between CAS servers if the request is proxied.
Administrators should watch out for scenarios where they have configured different behavior based on the logon type and required users to select the private computer option to access files, but users were able to access files without selecting the private computer option due to this bug. These users will now be unable to do so because we fixed the bug.

KB 970162 has more details about this release and a complete list of all fixes included in this rollup.

The release of Exchange Server 2007 Service Pack 2 (SP2) is just around the corner (slated for release in this quarter). SP2 will include all fixes in this Update rollup as well as the fixes contained in all prior rollups. We'll be posting more information on when future update rollups can be expected for Exchange 2007 SP2 as well as information about the patching improvements these rollups will bring.

Finally, I would like to call out our Exchange Software Updates forum. The forum is available to provide answers to questions about fixes contained in this rollup, help if you encounter issues when deploying the rollup, or if you just want to ask other forums users if you should take the plunge and install the rollup. We have engineers monitoring the forum to assist you.

- Exchange Customer Experience team

Share this post :

Comments (42)
  1. Zohaib Hafeez says:

    Please correct URLs

  2. jeremy says:

    I’m assuming this article refers to Windows Server 2008 R2.  Are we going to be calling them Windows 7 servers now or is this a typo?


    An error message is returned when you run the Get-Recipient command in the Exchange Management Shell that uses a Windows 7 domain controller

  3. Korbyn says:

    Bugga.  I thought RU8 was the last one before SP2 came out, which I last heard was supposed to be the first week in Aug.

  4. Pat Richard says:

    Just a note that the link about SP2 is a bad link. It should be http://msexchangeteam.com/archive/2009/05/11/451281.aspx

  5. Exchange says:

    Fixed the link badness – thanks for reporting!

  6. gerard says:

    Again, with this update as with previous ones, not all services were restarted on our Edge server, so I always reboot that server after applying update rollups, even though this shouldn’t be necessary.

  7. tony says:

    I have a Windows Server 2008 x64 server running Exchange Server 2007 x64. The Windows Server is also a Domain Controller. When Windows Server 2008 R2 comes out will I be able to upgrade the server to R2? What’s this thing about Exchange 2007 not supported on R2?

  8. ananth says:


    We will get KB 961551 corrected to remove references to code names. Thanks for pointing it out.


    If you would like us to troubleshoot, we will be happy to do. We will need the log from the ServiceControl Powershell script. If you are ok posting it, then open up a thread on http://social.technet.microsoft.com/Forums/en-US/exchangesoftwareupdate/threads/ and we will take a look to see if we can identify/fix the issue so that it does not happen in future rollups.


    Exchange Server 2007 will not be supported to run on Windows Server 2008 R2. So for the system which is running Windows Server 2008 + Exchange Server 2007, you cannot upgrade it to Windows Server 2008 R2.

    If you have a domain controller which does not run Exchange, you can upgrade it to Windows Server 2008 R2 since it is supported scenario to run against Windows Server 2008 R2.

  9. pesospesos says:

    Exchange 2007 SP2 will not run on Win2008r2?  Will any future ex2007 update allow it to run on win2008r2?

  10. Jason says:

    Curious why Exchange 2007 (even SP2) won’t be supported on 2008 R2, can you elaborate a little?  Since there will be an upgrade path from Exchange 2007 to 2010 when it becomes available, will it be possible/supported/recommended to update 2008 to R2 after first updating Exchange?

    I know most people would just point out that if that’s even a consideration we should be looking at raising another server and migrating to that, but it’s a small group and we just upgraded from Server 2003/Exchange 2003 to 2008/2007 less than a few weeks ago.  We got SA when sorting out the licensing since everything new was just around the corner again.

  11. Ashleigh Watson says:

    We have just been given the go ahead to deploy Windows 2008 R2 (when it arrives!). The architecture designs also include Exchange 2007. I am somewhat mystified by the comment: "Note: Exchange Server 2007 itself is not supported to be installed on a Windows Server 2008 R2 system".

    Is there are a particular reason for this, i.e. the schema of Windows 2008 R2 is so radically different from Windows 2008?



  12. ananth says:


    We welcome your comments on Exchange Server 2007 running on Windows Server 2008 R2. We will have a blog post or other similar communication around details about this and around upgrade scenarios involved with Windows Server 2008 R2. I will post a comment when that is available.

  13. Nick Lowe says:

    Comment from Elvis Wei, a Microsoft employee:


    Both are not released yet…

    Exchange 2007 SP2 is expected to be available in the second half of 2009. For Windows Server 2008 R2, we will have a longer time to wait.

    Windows Server 2008 R2 supports Exchange 2007 SP2.




  14. Exchange says:

    Nick Lowe,

    There will be a clarification posted to that thread on the forum – thanks for bringing it up…

    Please see last comment from Ananth regarding the latest relevant information. We WILL have more on this soon.

  15. pesospesos says:

    thanks guys, looking forward to the clarification.

    personally, I plan to move to ex2010 asap making the point moot for me — however my concern is that DPM v3 will be required to back up ex2010.

    This is disturbing because it would appear that history is repeating itself – yet another exchange release with no way of backing it up.

    Is there a plan to have dpm2007 updated to support ex2010 at its launch?  Because dpmV3 appears to be lated for release in 2010…

    please clarify how the team expects ex2010 backups to happen!



  16. Lord Melch says:

    I presume at present you can install Windows 2008 R2 Hyper-V with Exchange 2007 in a Winndows 2008 Guest (CAS/HT roles)

    Are we waiting for Exchange 2007 SP2 to allow Windows 2008 R2 support ?

  17. Lord Melch says:

    Has anyone tried installing this ? My LAB PC’s just sit at the Computing Space Requirements screen, and get no futher – have been left overnight !

  18. Lord Melch says:

    Belay that last comment – all servers install bar one – still fighting with it. No obvious error messages, just sits at "Computing Space Requirements"

    Once installed how can you check what Rollup version a server is running ?

  19. Lord Melch says:

    W2K8: Control Panel – Programs and Features – Installed Updates ;-)

  20. Waseem says:

    Has anyone installed Rollup 9.0, is there any issues, please let me know I am planning to update my server by this weekend.

    Thanks in advance!

  21. Lord Melch says:

    Worked fine on MOST of the Lab servers – some as per my post above just sit at "Computing Space Requirements"

  22. Ryan Spooner says:

    Does anybody know when Rollup 9 will be pushed through WSUS channels? I installed Rollup 9 manually on my Exchange Server, however when I switched Windows Update back to WSUS it prompted me to install Rollup 8 and this keeps failing presumably because a later version is installed. I have told it to ignore Rollup 8 for now, but it then offered me Rollup 7, then 6, then 5, etc.

    Having Rollup 9 available through WSUS would fix this issue. When’s it coming down that channel?

  23. ananth says:

    The rollup shipped through WSUS today.

  24. ananth says:

    The rollup shipped through WSUS today.

  25. TheMasta says:

    After u9 installation the http ssl service was disabled and not running. So the default website (owa etc.) ist not working!!! That’s really bad, you know!?! So i testet it twice – and the u9 is disabling the http ssl service. Dos anybody know why?

  26. Dan_IT says:

    it will NOT INSTALL FOR ME! it gives me an error code 80070643. There is no documentation on this code. I have installed and uninstalled 3 times now, with restarts between each.

    HELP!!! I REALLY NEED OUR ENTOURAGE WORKING!!!!! EMAIL ME dan@zeropointusa.com

  27. nick says:

    After installing RU9 on our 2007 SP1 servers with only the EDGE role on them, our transport rules stopped fucntioning correctly.  Removed RU9 through the uninstall process and they started working again.  Just a heads up for anyone else using transport rules.

  28. Abe says:


    I think I am having the same issues as Nick. Will have to look at removing up9 off to fix the issue.

  29. xC0000005 says:

    Nick, Abe – can you give me an example of rules that worked before and ceased functioning afterwards?  Does the fallback action fire or does it appear to be a complete failure to trigger the rule?

  30. Waseem says:

    Anyone who installed RU 9 on production server and have issues?

    Please share your experience.

  31. pesospesos says:

    if you are having problems with ru9, please post on the support forums provided above.  i have installed ru9 on my primary server and SCR target server without issue.

    Can someone from the team chime in with an update re: backup strategy for ex2010, since it would appear that DPM will not support it until v3 next spring?



  32. ryan says:

    rollup 9 messed up my OWA site. I have never made any customizations, but now the images show red x’s and some styling of the UI is missing. I have run the powershell commands to remove and recreate the owa site, with no resolution. Any ideas?

  33. tomasz1 says:

    Any news yet on what UR9 breaks in SBS 2008?

  34. Ed says:

    Rollup 9 also messed up my owa site…i cannot even view it. Its a coexisting environment of Exchange 2007 SP1 on Server 2008 DataCenter SP2 and Exchange 2003 on Server 2003 SP2. I’m uninstalling to test..

  35. Ed says:

    FYI – Uninstalling Rollup 9 fixed OWA

  36. Baz says:

    Rollup 9 also messed up my OWA.  Cannot access via IE, strangley can access via Firefox but layout is totally screwed.  As above I am looking to uninstall Rollup 9 but when I goto Control Panel > Programs and Features the link to "View installed updates" does not work, anyone know of another way to remove Rollup 9?  Cheers

  37. tomasz1 says:

    I gave UR9 a try on SBS 2008 last night. It didn’t screw up OWA and everything seems to work fine (for now).

  38. brad says:

    OWA with custom theme got messed up here too.

  39. nick says:

    xC0000005 –

    We have a rule that blocks mail coming in on external interface (from the internet) that has our internal domain name listed in the sender.  (i.e. anyone sending us mail from outside our organization purporting to be FROM our domain name).  That continued working fine.  However, we also have an exception in that rule that says if the "FROM:" in the message header contains certain text, to allow the mail through.  We have this because we are on a large campus with numerous list servers that need to bypass this filter.  

    After applying RU9, the block of external messages with our domain name continued to work, but the excpetions stated in the rule did not.  Hope that makes sense..

  40. MauriceW says:

    Any news on the Windows Server 2008 R2 issue? When can we expect an update about this? Thanks!

Comments are closed.

Skip to main content