After I installed SCVMM I wanted to get up and running quickly. At that time I wrote this document. However after using VMM for a few months I fouund what I did wrong. I re-installed VMM and now I have updated this document to reflect the changed.
Here are the updated steps:
- Start SC VMM manager on the VMM server (At least once start the VMM manager on the VMM server, later on you can install and use it from your own Workstation.)
- Authenticate to the localhost using the admin account (I was already logged on using an admin account so I chose the option – “Use current…)
- On the lower left corner, click on “Settings”.
- On the left side, expand “security” and click on the “Run As Accounts”.
- On the ribbon at the top, click on “Create Run As Account” button.
- Create a new account called “Host Admin” and give it the credentials of the AD account we created earlier – “SCVMM Admin”. More info about why this account is needed is here.
- Now that you have a run as account in VMM, you will use it to add Hyper-V hosts to VMM.
- Click on “Fabric” on the lower left side.
- Click on the big green plus sign called “Add Resources” on the top left corner and choose “Hyper-V hosts and Clusters”.
Note: The next screen has some very interesting options. The last one is very, very interesting:
- At this point, I will just choose the first option and go with it.
- On the next page, choose “Use and existing Run As Account” and click “Browse”.
- Choose the “Host admin” account and click OK
- On the next page I specified an AD query to search for all my hyper-v hosts. I just used a wildcard because all my hyper-v hosts are named similarly.
- It found all my 4 Hyper-V hosts including the Hyper-V cluster I had setup separately.
- I selected all hosts and the cluster and clicked “next”.
- On the next screen I checked the checkbox “Reassociate this host…” because I had been using these hosts with another VMM server earlier.
- I added two VM placement paths
- C:\ClusterStorage\Volume2 (for a CSV on SAN)
- D:\Hyper-V (for local disk array on the HV nodes)
- On the next screen I turned on the incoming/outgoing live migrations.
- Since my servers are already configured to use Kerberos, I checked that radio button.
- I set the Cluster heartbeat network to be used for live migrations – 10.10.10.0/24
- Click next and it shows a confirmation page of what it is going to do next.
- Click finish and it shows the jobs page.
- I got a few failures…all of them were saying that the hosts have an unsupported version of VMM agent. I uninstalled the old VMM agent software on the host servers and tried the operation again.
- I went to “VMs and Services” on the left side and noticed that my cluster was there but the nodes under were in a pending state. I removed the cluster from VMM and tried re-adding the hosts and clusters and described above.
- At this point the add succeeded.
Notes from the install I did earlier:
- It takes a minute or two for the jobs to finish. I think it installs an agent on each hyper-v host.
- I got a warning for each machine, telling me that a restart is required because “the server needs to complete claiming of multi-path I/O devices”. I did that later.
- I closed the jobs window and now I see all three hyper-v hosts and my VMM server in the managed computers list.
- Click on “VMs and Services” and I see all my Hosts and the VMs running on those hosts.
- The console provides a lot of options for managing these VMs and hosts from within one application. Sweet!
More, detailed information on Administering SCVMM 2012 is here.