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...
Updated Jul 01, 2019
Version 2.0
Blog Post
I am glad I came across this article before we went further with our server/network refresh.
I have to agree with a lot of people here when they say "they were not made aware of this incompatibility", not even from the installation of the software. Since the Exchange 2007 runs a prerequisite check before it tries installing and shoots out a report, why was this not mentioned in that report? Seems to me to be something of a large prerequisite.
From the eight vendors we received quotes from for our new hardware and software, none mentioned that our Exchange 2007 SP2 servers would not run on Windows Server 2008 R2. Even after pointing them to this article they did not believe it (and I must say I was skeptical as well) when they first read it.
We were about to commit over 12 million in new hardware and software. Over one million in Microsoft OS's and other software such as Exchange 2007. Since this has come to our attention, a lot of our upper management, who are mostly technically inclined, are quite upset about this. Upset to the point that they are now rethinking their decision on using Exchange 2007 and staying with the current solution.
Essentially, this means a lot of money will NOT reach our vendors and thus become part of the economy. This decision by Microsoft has left a "sour taste" in our collective mouths. We have not been tasked to look for alternatives or ways of making it work. If we cannot meet our mandate of using the same OS for all servers and a standard collaborative mail server architecture from Microsoft, then we will have to look at other offerings.
We had started out as a Novell and Domino dominated company many years ago and had painfully made the switch to Windows and Exchange. Now when we are poised to invest a lot of capital into the economy, we have to scrap that for now while we figure out our next steps.
This not only means a lot of work and overtime for me to make up for lost time, it means mounting frustrations for those who believed Microsoft could do no wrong in the OS and mail server fields.
Remember... people can change their minds, and do often enough.
I'm wondering if Apple will make a commercial about this now?
Mac: Hi, I'm a Mac.
PC: Hi, I'm a PC.
Mac: So, what are you up to today PC?
PC: I'm waiting to hear when my good buddy Exchange 2007 will show up.
Mac: That's nice, are you two going to do something fun together?
PC: Well, not really fun. I'm playing hide 'n' seek. Oops, time to go, I hear him trying to install.
Over and out.
I have to agree with a lot of people here when they say "they were not made aware of this incompatibility", not even from the installation of the software. Since the Exchange 2007 runs a prerequisite check before it tries installing and shoots out a report, why was this not mentioned in that report? Seems to me to be something of a large prerequisite.
From the eight vendors we received quotes from for our new hardware and software, none mentioned that our Exchange 2007 SP2 servers would not run on Windows Server 2008 R2. Even after pointing them to this article they did not believe it (and I must say I was skeptical as well) when they first read it.
We were about to commit over 12 million in new hardware and software. Over one million in Microsoft OS's and other software such as Exchange 2007. Since this has come to our attention, a lot of our upper management, who are mostly technically inclined, are quite upset about this. Upset to the point that they are now rethinking their decision on using Exchange 2007 and staying with the current solution.
Essentially, this means a lot of money will NOT reach our vendors and thus become part of the economy. This decision by Microsoft has left a "sour taste" in our collective mouths. We have not been tasked to look for alternatives or ways of making it work. If we cannot meet our mandate of using the same OS for all servers and a standard collaborative mail server architecture from Microsoft, then we will have to look at other offerings.
We had started out as a Novell and Domino dominated company many years ago and had painfully made the switch to Windows and Exchange. Now when we are poised to invest a lot of capital into the economy, we have to scrap that for now while we figure out our next steps.
This not only means a lot of work and overtime for me to make up for lost time, it means mounting frustrations for those who believed Microsoft could do no wrong in the OS and mail server fields.
Remember... people can change their minds, and do often enough.
I'm wondering if Apple will make a commercial about this now?
Mac: Hi, I'm a Mac.
PC: Hi, I'm a PC.
Mac: So, what are you up to today PC?
PC: I'm waiting to hear when my good buddy Exchange 2007 will show up.
Mac: That's nice, are you two going to do something fun together?
PC: Well, not really fun. I'm playing hide 'n' seek. Oops, time to go, I hear him trying to install.
Over and out.