Since the emergence of vSphere 6.0, I would like to write an article on vSphere 6.0 vs Windows Server 2012 R2. I collected vSphere 6.0 features from few blogs and VMware community forum. Note that vSphere 6.0 is in beta program which means VMware can amend anything before final release. New functionalities of vSphere 6.0 beta are already available in Windows Server 2012 R2. So let’s have a quick look on both virtualization products.
||Hyper-v Server 2012 R2
||Active Directory Certificate Services
||Certificate Store in Windows OS
|Single Sign on
||VMware retained SSO 2.0 for vSphere 5.5
||Active Directory Domain Services
||vPostgres database for VC Appliance up to 8 vCenter
||Microsoft SQL Server
||Web Client & VI
VMware retained VI
|SCVMM Console & Hyper-v Manager
||Combined single installer with all input upfront
||Combined single installer with all input upfront
||Long distance Migration up to 100+ms RTTs
||Multisite Hyper-v Cluster and Live Migration
||Storage vMotion with shared and unshared storage
||Hyper-v Live Storage Migration between local and shared storage
|Combined Cloud Products
||Platform Services Controller (PSC) includes vCenter, vCOPs, vCloud Director, vCoud Automation
||Microsoft System Center combined App Controller, Configuration Manager, Data Protection Manager, Operations Manager, Orchestrator, Service Manager, Virtual Machine Manager
||View the services that are running in the system.
||Platform Services Controller (PSC) includes Licensing
||Volume Activation Role in Windows Server 2012 R2
||A Virtual Datacenter aggregates CPU, Memory, Storage and Network resources.
||Provision CPU, Memory, Storage and network using create Cloud wizard
Another key feature to be compared here that those who are planning to procure FC Tape library and maintain a virtual backup server note that vSphere doesn’t support FC Tape even with NPIV and Hyper-v support FC Tape using NPIV.
Previously I wrote a blog on comparing price and features of Hyper-v and VMware. I got lot of feedback and questions why I believe Microsoft will win the battle. Here is a short answer for this question.
Living in mining city of Australia, its truth that most mining, oil and gas company isn’t adopting Microsoft Hyper-v yet excluding Fortescue Metals (FMG). FMG took a smart decision to go for Microsoft cloud than any other cloud technology. But wind is shifting quickly. Not just mining, oil and gas companies. Here are other examples: ING Direct case study and Suncorp Bank case study. There is nothing to hide that Microsoft came late to Hypervisor game. Slowly but surely Microsoft is gaining momentum.
I worked in almost 15 years now. I have seen in many occasions that Microsoft crashes its opponent and gain market in their own business. This is what happening in Hypervisor battle. Let’s be honest VMware is THE leader in virtualization. I am sure there are skeptics who believe, beating VMware isn’t possible. Those skeptics betted their money on Novell Netware, IBM Lotus Notes and Corel Word Perfect in those days. If I had told you in year 2000 that Active Directory would beat Novell e-directory, you would have burst out of laugh. But now there’s nothing to comment on this. By now you rarely see and work e-directory, word perfect or lotus notes. These examples says it all. VMware’s fate is written when Microsoft released Windows Server 2012, Hyper-v Server 2012 and System Center 2012. By the next Windows, Hyper-v and System Center release VMware may extinct.
If you need more evidence then you can find Microsoft’s Oil and Gas customer’s success stories on Microsoft View Point.
Client Hyper-V on Windows 8 provides a rich virtual platform for developers and IT professionals. You can create and manage virtual machines using client Hyper-V leveraging the security, scale, and manageability of Windows 8 and Server Hyper-V platforms. This is a convenient lab and test environment for Wintel Engineers, developers and cloud engineer. Client Hyper-V uses the same VHD format as Hyper-V on the server. However not all the features available in bare-metal Hyper-V are available in Client Hyper-V.
- Windows 8 32-bit and 64-bit operating systems
- Support up to 32 virtual processors and 512GB of memory
- Support IDE, iSCSI, SMB, and USB flash drives.
- BitLocker Drive Encryption and Secure Boot
- Support Second Level Address Translation (SLAT) on x64 PC
- Multiple wired and Wireless network support
- 3D, audio, multi-touch,sleep and hibernate states
- Support same VHD virtual disk as bare-metal Hyper-V
You can build, host, and test an entire infrastructure on your Admin PC and then export the virtual machines directly into production environment in Windows Server 2012. To turn on the Windows 8 Hyper-V feature also installs a VM management tool called Hyper-V Manager.
- Hover mouse on right hand side top corner, Click Search, Type Control Panel then click control panel click Programs, then select Programs and Features.
- Select Turn Windows Features on or off.
- Click Hyper-V, then OK, and then Close.
To enable Client Hyper-V using Windows PowerShell, Open elevated PowerShell command , type the following:
Once Hyper-V is enabled, you must shut down PC and start your PC to complete installation. You will be able to create and manage VMs through Hyper-V Manager or the Hyper-V Module for Windows PowerShell. You can also use Virtual Machine Connection to remotely connect to VMs. You can utilize sysinternals Disk2vhd VHD converter to create and import large virtual machines into Client Hyper-V to test and experiment your infrastructure.