This is my fourth posting in a serie of postings in which I will compare features of VMware vSphere 5 with Microsoft Windows Server 2012 Hyper-V.
Goal of the postings is to give a non-biased overview on features of two main players in the server virtualization market: VMware vSphere and Microsoft Windows Server 2012 Hyper-V. I will not use the marketing comparison tables used by both vendors to promote their unique features while ignoring the competitors features (as marketing is all about).
Other posting in this serie are
vSphere 5 versus Windows Server 2012 Hyper-V: storage integration
vSphere 5 versus Windows Server 2012 Hyper-V: live migrations
vSphere 5 versus Windows Server 2012 Hyper-V: high available VMs
For management the compare is pretty simple:
VMware offers vCenter Server to manage ESXi hosts, virtual machines and more components using vendor plugins. At each new release of the ESXi hypervisor vCenter Server will immediately support it.
Windows Server 2012 Hyper-V cannot be managed yet by System Center. System Center Virtual Machine Manager 2008 is unlikely to support Windows Server 2012 Hyper-V at all.
System Center Virtual Machine Manager 2012 will need SP1 to support Windows Server 2012 Hyper-V. Unconfirmed sources say SP1 will come out and the end of the year, or even begin of 2013!
The same applies to DPM2012 for backup and restore.
Read more about it here.