Welcome to Exchange Team Blog Sign in | Join | Help

Syndication

This Blog

Microsoft Virtualization: Best Choice for Exchange Server

Virtualization continues to be a hot topic for many of you with questions raised around whether Exchange should be virtualized.  We started talking about this back in January (http://msexchangeteam.com/archive/2009/01/22/450463.aspx) and continue to recommend Microsoft virtualization technologies for these deployment scenarios.   For example, the Exchange team recommends Microsoft virtualization (Hyper-V + System Center) for customers who want to virtualize their underutilized CAS, Hub and mailbox roles.  Additionally, the Edge Transport role along with other security gateways on the edge server can be considered for virtualization to maximize hardware utilization.  

Studies have shown that in mixed physical/virtual Exchange environments, virtualization can deliver significant benefits including reduced server hardware costs, power and space savings, improved server utilization and rapid server provisioning.  Additionally, by choosing MS virtualization (Hyper-V + System Center) customers  benefit from a lower cost solution (both up front and ongoing) that is already part of Windows Server and an integrated end to end management solution for both physical and virtual environments. 

Whether you install on physical hardware or virtual machines, Exchange Server and Windows Server + System Center provide the best solution for you.

For more information on virtualizing Exchange and other Microsoft server applications please visit http://www.microsoft.com/virtualization/solutions/business-critical-applications.  Also check out the latest MS virtualization blog here.

- The Exchange Team

Published Thursday, September 03, 2009 2:34 PM by Exchange
Filed Under: ,

Comments

 

Fred GUILY said:

Hi

A objective comparison between VMWare virtualisation and Hyper-V would be more interresting, don't you think ?

Fred
September 4, 2009 3:53 AM
 

Mattias said:

Have to agree with Fred here...
September 4, 2009 4:13 AM
 

Pete said:

I agree with Fred as well, is there a link that could be posted comparing and contrasting Hyper-V to VMware and possibly Xen and Linux KVM as well?
September 4, 2009 9:33 AM
 

Pierre said:

This is biased...
September 4, 2009 9:59 AM
 

Chris said:

It would be nice to see the recommended configurations for both vmware and Hyper-V
September 4, 2009 10:13 AM
 

Sean said:

Of course it is biased, this is the Exchange Team who are employees of Microsoft.  Why wouldn't they promote Microsoft technologies?
September 4, 2009 10:25 AM
 

Rob said:

Of course they are going to recommend their own product.  

They are also going to definetly recommend the product that they test with and can actually support over a third party solution.
September 4, 2009 12:13 PM
 

pesos said:

Guys, don't be silly - this is a Microsoft blog lol.  VMWare continues to be the best solution for large installations.

That being said, I am using Hyper-V to virtualize all of my DCs, a SQL server, a couple lightweight citrix servers, and my web server.  Now that R2 is out I plan to move everything to a beefy 2 node cluster and virtualize my file server and upcoming Exchange 2010 servers as well.  Hyper-V is a young but solid option, especially for those already invested in 2008r2 Enterprise/Datacenter...
September 4, 2009 12:52 PM
 

mdgrkb said:

I believe it would have been better to at least publish a link to some third party benchmark comparing Exchange running on different virtualization platforms.

Regards
September 7, 2009 7:59 AM
 

Wayne Hoggett said:

If you haven't tried Hyper-V, maybe it's time you did. I've been a VMWare supporter for some time, but Hyper-V deserves a look.
September 8, 2009 8:16 PM
 

Sean said:

I tried Hyper-V after using VMware for about a year and it was not a pleasant experience.  We decided to use Hyper-V with a client because it was during the period when MS refused to support their product running on VMware so we didn’t want to take a chance. Hyper-V took longer to setup, we had issues with DHCP and NICs not being able to bind, spent hours on the phone with MS techs who didn't know what to do because it was so new.  I think this is when I realized that MS puts out a "finished product" but it’s really a massive beta test.  After a few months we started having performance issues.  Instead of wasting more time with MS, we converted the images and installed ESX.  All of our problems disappeared.  That’s when I decided I was tired of being the MS ginnie pig.  VMware has always been a solid product with very few issues.  We don't use anything else for our virtualization solutions, especially now that MS cam to their senses about support.
September 24, 2009 12:54 PM
New Comments to this post are disabled

News


This blog and its contents are provided "AS IS" with no warranties, and they confer no rights. Use of any included script samples are subject to the terms specified in the Terms of Use.
New! Would you like to suggest a topic for the Exchange team to blog about? Send suggestions to us.

Exchange Server 2010 - Get the Release Candidate



Poll:

Other Exchange Blogs from MSFT