Microsoft's Support Policy on VMware Virtualization

Ehlo All,

An attendee at our March NY Exchange User Group meeting asked about Microsoft's support policy on the industry leader of virtualization which is running at 100% of all Fortune 100 companies, VMware. There is a lot of fear, uncertainty, and doubt in this realm. So, let me make it crystal clear! Microsoft WILL SUPPORT VMware's SVVP (explained below) solution which is ESX 3.5 update 2. Microsoft virtualized support is for over 30+ server applications & operating systems as per KB ID 957006. Just to clarify, for Exchange 2003 & 2007 SP1 are supported.

Quoted from MS KB # 897615
Additionally, for vendors with whom Microsoft has established a support relationship that covers virtualization solutions, or for vendors who have Server Virtualization Validation Program (SVVP) validated solutions, Microsoft will support server operating systems subject to the Microsoft Support Lifecycle policy for its customers who have support agreements when the operating system runs virtualized on non-Microsoft hardware virtualization software. This support will include coordinating with the vendor to jointly investigate support issues. As part of the investigation, Microsoft may still require the issue to be reproduced independently from the non-Microsoft hardware virtualization software. Where issues are confirmed to be unrelated to the non-Microsoft hardware virtualization software, Microsoft will support its software in a manner that is consistent with support provided when that software is not running together with non-Microsoft hardware virtualization software.

VMware's Exchange support information for ISV support.

VMware Press Release about ESX 3.5 update 2 support Exchange, SQL, SharePpint, and more. They even quote a 50k seat install on ESX with Exchange by the University of Plymouth in England.

Just to be clear, make sure your issue is non-virtualization related. e.g. not performance or other, and more a configuration or those types of problems. If you have an I/O issue, it could easily be a VM issue, so make sure those subsystems working well and you're 100% sure it's not VM related.

Now, you know the real story behind Microsoft support for virtualization and you can now rest easy. Or the other solution is to have a very good back process running on non-virtualized hardware. That's what I do. Sleep is over-rated.

-Ben