System Center Virtual Machine Manager is now starting to get more traction than ever, especially so given some of its management capabilities around Storage and Networking, Moreover when the Windows Azure Pack is used in production, Virtual Machine Manager must be installed in high availability in order to your tenants have almost always access to their VM management. To do this VMM uses the Failover Cluster feature integrated in Windows Server.
Before you begin there are some important things to note:
- Not only should the VMM Management Server should be highly available, but also the SQL Server where the VMM database will be installed and the file share for the Library Share too.
- Whilst it is possible to have two or more VMM Management servers in a cluster, only one node will ever be active.
- You will need to configure Distributed Key Management. The distributed key management is used to store encryption keys in AD instead of storing the encryption keys on the machine/VM where the Management Server is installed.
The high level steps we will be carrying out in this post are:
- Install all the SCVMM prerequisites (ADK)
- Create a VMM Service Account which has local admin rights on the SCVMM nodes.
- Create a container in Active Directory Domain Services for the Distributed Key Management.
- Set all IP addresses, you may also configure an independent Heartbeat network
- Install & configure the Failover Cluster feature on both servers.
- Install SCVMM 2016
First Install ADK and MSODBCSQL & MSSQLCMD on both VMM Server’s.
You can also download the ADK to an alertnate path and install on your VMM Server’sif your machine is not connected with internet.
Install Failover Clustering feature on Both VMM Server’s.
Start Installing VMM on VMM Node 1
Right Click on the Setup and Run As Administrator
Click on Install
After you click Next from the Above Picture, it will check for the Prerequisite for the VMM like Minimum Memory,ADK and Etc.
It the Prerequisite Passed then it will give you option to configre Database for VMM Server’s.
Enter the database information for the MSSQL database you want VMM to use. As stated earlier, this should be a highly available SQL installation installed on a separate failover cluster from the cluster we are installing VMM on.
Use Domain Admin Credentials it should automatically Detect MSSQLSERVER in Instance Name and Click on Next.
Enter the service name for the VMM installation. Click Next
Click Select and search for your Service Account and enter the Password. In the Distributed Key Management section enter the location of the DKM container in AD created earlier.
Add the Service Account to the Local Administrator Group.
Done with the Installation on VMM Node 1 Click Close to Finish.
Start VMM Installation on Node 2.
Finally you need to install VMM on the second node in the cluster. To do this, log on to the second node and run the VMM installer.
You’ll be prompted to add this server as a node to the highly available VMM installation (you’ll obviously say you do).
You won’t have to enter the DKM information again (you’ll still have to enter the VMM service account password but not the username.
You won’t have to enter database information.
Below Snapshot is from the Database Configuration fron Node 2.
Below Snapshot Either you can Create a Library or you can use the Existing one.
To Connect to VMM Server you can either enter the Clsuter Role name for VMM server or the Active Node Name and Click Connect.
Below snapshot you can confirm both the VMM server’s.
That’s it! You now have a highly available VMM environment to manage your Server 2012 R2 /Server 2016 Hyper-V Hosts.