EDIT 9/16/2009: We have now published fixes for this problem and have an updated blog post about it. Please go here to read the updated information.
We have learned of and analyzed the problem wh...
Updated Jul 01, 2019
Version 2.0
Blog Post
2 MIN READ
Exchange 2007 SP2 Setup fails if all domain controllers are running Windows Server 2008 R2
Exchange team -
I am a CIO of an organization that was (until reading this blog) expecting to acquire a significant amount of microsoft product to upgrade our server o/s environment, exchange environment, and SQL environment. After learning of the incompatabilities stated in this blog with regard to the mentioned product groups, I have decided to stop my organization's purchasing of microsoft product. I will certainly explore this issue further with my Microsoft sales team, but I must tell you that your managing director should take a moment to hear what is behind the words of the people commenting in this blog. What is behind these comments is a growing industry frusteration with Microsoft's ability to deliver. In a free market, frustration with a product manufacturer inevitably creates a new market for other manufacturers and their products. The hard working engineers speaking to you through this blog medium are trying to tell you that they are willing to wait for a season, but that the season is drawing short. Once a manufacturer loses it's good-will standing with a market, that good-will can not be bought back easilly. The allegiance these people are showing towards you is remarkable. Do not disregard their allegiance to your products. These engineers, once they feel they have exhausted all their options, they will move on realizing that it is better to have products that interoperate and cost more, than to try and work with products that continually frusterate their efforts. The same allegiance they are showing towards you, will shift away and become the resiliance apposed to you.
I certainly hope that Microsoft can,in some fashion, regain their once quality standing with regard to product interoperability and reliability.
I am a CIO of an organization that was (until reading this blog) expecting to acquire a significant amount of microsoft product to upgrade our server o/s environment, exchange environment, and SQL environment. After learning of the incompatabilities stated in this blog with regard to the mentioned product groups, I have decided to stop my organization's purchasing of microsoft product. I will certainly explore this issue further with my Microsoft sales team, but I must tell you that your managing director should take a moment to hear what is behind the words of the people commenting in this blog. What is behind these comments is a growing industry frusteration with Microsoft's ability to deliver. In a free market, frustration with a product manufacturer inevitably creates a new market for other manufacturers and their products. The hard working engineers speaking to you through this blog medium are trying to tell you that they are willing to wait for a season, but that the season is drawing short. Once a manufacturer loses it's good-will standing with a market, that good-will can not be bought back easilly. The allegiance these people are showing towards you is remarkable. Do not disregard their allegiance to your products. These engineers, once they feel they have exhausted all their options, they will move on realizing that it is better to have products that interoperate and cost more, than to try and work with products that continually frusterate their efforts. The same allegiance they are showing towards you, will shift away and become the resiliance apposed to you.
I certainly hope that Microsoft can,in some fashion, regain their once quality standing with regard to product interoperability and reliability.