Blog Post

Exchange Team Blog
2 MIN READ

Exchange Server 2007 SP2 and Windows Server 2008 R2

The_Exchange_Team's avatar
The_Exchange_Team
Platinum Contributor
Sep 21, 2009

EDIT 11/4/2009: The information in this article is obsolete. Please read this post for new information on the subject.

Since we announced the release of Exchange Server 2007 SP2, we've received a few questions about running Exchange 2007 on Windows Server 2008 R2.  We wanted to provide some additional information on how we made the decision to support Exchange Server 2007 SP2 on Windows Server 2003 SP2, Windows Server 2003 R2 SP2 and Windows Server 2008 SP2 but not Windows Server 2008 R2.   This decision is not one we took lightly and was informed by customer feedback.

Two primary technical points drove our decision to not support Windows Server 2008 R2.  First, Windows Server 2008 R2, while an incremental OS upgrade, creates significant testing requirements for Exchange 2007. Because the Exchange 2007 SP2 engineering preceded the Windows Server 2008 R2 RTM, Exchange 2007 SP2 would have had to be delayed significantly to align testing schedules.  Second, because upgrading the server OS underneath an existing Exchange server is not supported, the feedback we have received is that the primary need is to support Windows Server 2008 R2 domain controllers in an existing Exchange 2007 deployment, which we have done. 

In reviewing the specific work items to support Windows Server 2008 R2, we determined that while significant testing time would be required this work would only ensure the minimum level of compatibility, and it still might not allow Exchange to take advantage of new Windows 2008 R2 features.  Additionally, this work would be at the expense of delivering the capabilities customers have told us they want in Exchange 2010.  So, based on this reality we decided to focus on the compatibility between Exchange 2007 SP2 and Windows Server 2008 R2 domain controllers and the releasing of Exchange 2010 as close to Windows 2008 R2's release as possible.  We felt that thoroughly validating the combination of Exchange 2010 on Windows Server 2008 R2 allowed us to focus on delivering great solutions which would be fully tested and would support the features of Windows Server 2008 R2.

We recognize that there are some downstream impacts to this decision related to administration only installs.  The technical problem for us is that an administration install of Exchange is almost identical to a full Exchange server installation. 

This is a hard trade-off to make, but we believe it is the right one and a good balance between serving existing customers and driving innovation.

Hope that this sheds some light on the subject!

- Nino Bilic

Updated Jul 01, 2019
Version 2.0

60 Comments

  • I don't see the big problem in not supporting Exchange 2007 on Server 2008 R2. Why do you want to spendt time reinstalling or adding Exchange 2007 cluster servers and so on to the environment on Server 2008 R2 instead of just using Server 2008 SP2? If you are ready for the new server OS shouldn't you be ready for the new Exchange version as well?
    I am looking forward to the release of Exchange 2010 so that we can take benifit of the new DAG features.
  • Yeah, I wonder too - Why someone may don't want to install a new SP2 to a product? Fears? Diffidence?
    I always do, after some thorough testing in the lab of course.



    Русский перевод статьи здесь (Russian version of this post is here): http://www.maximumexchange.ru/2009/09/22/exchange-2007-sp2-and-windows-server-2008-r2/
  • Hi Exchange Team !

    I really hope you will at least come back to that problem after Exchange 2010 has been released and issue a hotfix that makes Exchange 2007 compatible with Windows Server 2008 R2. There will be quite a few reasons why this should be done, one of them is to allow people who purchased Exchange 2007 and do not want to upgrade to Exchange 2010 (or whose company policy wont allow it) to use the latest Server OS once a reinstall is necessary. You don´t need to support all the features of R2 with Exchange 2007, just make it work similar to R1 once Exchange 2010 is out. Having said that, I am looking forward to Exchange 2010 :-)
  • Will a future update allow Exchange 2007 SP2 (even at least admin tools!) to be installed on Server 2008 R2?  Or will that never happen?
  • You made the right decision. Supporting the 2008 R2 DC's is what's important.
  • Good thing we canceled SA and decided to settle on 2008 (no R2) for a few years including for our upcoming Exchange 2007 deployment.
  • @ samara lynn - Exchange 2007 SP2 is required for coexistence of Exchange 2007 with Exchange 2010. So while you do not have to install Exchange 2007 SP2 now, you will need to do so when you will want to coexist with Exchange 2010.

    Curious - is there a specific thing blocking you from installing Exchange 2007 SP2 on your existing Exchange 2007 servers when the time comes?
  • Justin, not sure what you mean by barely a year old...  it's 20 months between win2008 rtm and win2008r2 rtm by my count (feb 08 to oct 09).  Shorter than usual, sure, but can't blame MS for wanting to get away from the Vista/2008 codebase as quickly as possible.

    I see no reason for the team to have spent resources getting ex2007 working on 2008r2 when ex2010's release is imminent, and may happen before R2 is officially release on oct 22 (cmon guys!) :-)
  • Hello,

    One question: Since you need to deploy Exchange 2007 SP2 to upgrade to Exchange 2010, how does this effect admins wishing to upgrade to 2010 eventually, but not able to install SP2?

    Thanks,

    Samara Lynn
  • I understand the decision ... but the "impression" being left about is starting to get negative.

    2008 is barley a year old yet the changes to R2 create waves of implications.   Other MS prodcuts arn't certified on it.  Applications _introduced_ in 2008 have alreayd been removed (servermanagercmd.exe in core for example).  New Forest exclusive modes to leverage potentially great features that in practice are clunky to the average admin (no GUI at all for the ad-recycle bin?  I dont know a single tech who likes the idea of doing powershell queries instead of the drag and drop they are used to).

    2008 and R2 are huge leaps forward in secuirty and configurability but these areas of polish that have been neglected are sadly the first thing most daily admins will see ... and thats just going to leave a poor impression and alot of techs to simply sit on 2003 a little longer until all this is sorted out.