A study that VMware paid for claims that managing their virtualisation is cheaper than managing Hyper-V. OK class, calm down. You at the back … stop laughing before your head falls off! Yes, and a study I paid for says that VMware are getting desperate … as in Novell in the year 2000 desperate.
Last year I wrote a post that compared the cost of Windows Server VMs on a 2U host, with 2 CPUs and 92 GB RAM., and 50 VMs Hyper-V and all of System Center on one hand, and vSphere Standard (not Enterprise plus with all the features and all the additional cost) with just vCenter Operations. Even with the most basic VMware solution (against the full MSFT pack), MSFT came in at 57% of the cost of VMware.
OK, since then, System Center 2012 SMLs are maybe a little more expensive than the old SMSD … but I can counter that now by switching to an ECI license (big discount for big orders) or CIS (small discount for small orders) where Windows Server and System Center 2012 are bundled.
Maybe the VMware commissioned study is saying that the actual cost of operations are higher in the MSFT space? How does one service pack or patch vSphere? They do get released from time to time, you know. Oh yeah … you don’t install them because they usually break the host. But when you do, isn’t it time consuming? Over on the MSFT space, I have Windows Update, WSUS or ConfigMgr to control the distribution of updates. I can orchestrate the installation using VMM 2012, or I can use Cluster Aware Updating in Windows Server 2012. Test, setup, fire and forget (well … run a report every now and then to check compliance). Complete automation, baby!
What about the cloud? How does that work in vSphere? Spend lots and lots of money and hack the ell out of their rebadged point solutions. In MSFT world, you have System Center 2012, download and add the Cloud Services Process Pack and there you have a private cloud, with self-service. Now the “users” can deploy VMs for themselves with audit trails, governance, and all that jazz. No need to involve IT in service deployment.
This could go on and on and on and on and on and ….
Hmm, VMware, you really are sounding like you’re grasping for straws right now.

