VMM 2012 promise a much deeper cluster integration than VMM 2008 R2 provided, and I wanted to test the entire process, from creating Hyper-V hosts, to create a Failover Cluster – everything from my VMM 2012 server.
This post will cover the process of how you enable your physical servers for virtualization.
(Info: In VMM 2012, you are also able to do a bare metal deployment of your Hyper-V servers, but I won’t cover it here in this post).
(Bonus info: support for managing trusted and untrusted Hyper-V host clusters from the same VMM management server is new in VMM 2012. In VMM 2008 R2, two VMM management servers were required; one for trusted domain hosts; and one for untrusted domain hosts.)
Before we get started:
Both of my physical servers was installed with Windows Server 2008 R2 Enterprise SP1
There are 4 NICs pre-configured on the servers, and both servers are joined to my domain.
Both servers are connected to the iSCSI-target (used for CSV in my lab).
I`ve created a RunAs account in the ‘Host computer’ category for managing my physical servers.
If you`re most likely to have many Hyper-V servers, you should try to segment them into logical groups in VMM 2012. I`ve created a host group called Hyper-V hosts in my VMM server; this is where I want to place my two physical Hyper-V host in this process.
Ok, we start by heading into the fabric, and select our host group. Right click, and select 'Add Hyper-V Hosts and Clusters'
The job starts, and do the following tasks:
· Add the Virtual Machine host
· Install Virtual Machine Agent
· Refresh hosts
· Enable Hyper-V
After the job has finished, you will be presented with a lot of detailed information about the deployment. (NIC configuration, storage, CPU, RAM ++)
The new Hyper-V hosts are located in the hosts group in the Fabric. We are now ready to create a Failover Cluster.