I was thrown into a Hyper-V 2012 R2 deployment on Nutanix recently and I found that it would have been impossible to manage without Powershell. It is the only way to really manage Hyper-V in my mind. Or at least the hosts.
Some things that I learned from the deployment:
1> Nutanix Foundation 3.01 is needed to properly deploy Hyper-V 2012R2.
2> IPMI is no longer being used as a means to install the OS. Also you may run into IPMI config problems unless you statically assign the IPMI IP addresses of the nodes.
3> SCVMM is assumed as the management standard, but not everybody want to pay for it. So learn to use powershell
4> You MUST connect the hosts to a domain but using the python script “setup_hyperv.py” on a CVM after provisioning the host OS.
(reference: https://portal.nutanix.com/#/page/docs/details?targetId=HyperV_Administration-NOS_v4_0:hyperv_scvmm_host_storage_add_t.html )
5> Some switches will not like it if you use LBFO switch independent teaming (the default). Switch the teaming to LACP and switch dependent. Below is an extremely useful guide for NIC teaming on Windows Server 2012 / Hyper-V server 2012.
6> You can access a CVM on a host with broken networking by accessing the host on the console and then in powershell ssh to the CVM as follows
This will always connect to the CVM if it’s running.
7> Lastly, when you add the hosts to the domain with the script, it will also create an SMB3 share with the UNC path \\clustername\containername
So if your cluster name is MyFancyCluster and your container is VOL01, then the UNC is \\myfancycluster\vol01
This is what you configure on the Hyper-V nodes for the default VM location.
If you try to use the FQDN like \\myfancycluster.contoso.com\vol01 it will look like it works. But it will fail on VM creation.
8> Whitelist the container if you want other non-Nutanix hosts to access it via SMB3.