Hope you like it..

Virtualized Domain Controller Nightmare on Nutanix Hyper-V Cluster

December 27, 2016 at 9:00 am 2 comments

Hi Guys

We recently deployed a Hyper-V  Nutanix Cluster , and everything looked fine until we hit the wall. For some reasons if the VM(Domain Controllers)  go down you will not be able to power it on . The reason behind this that the Hyper-V Cluster on Nutanix uses SMB3 based share as the shared storage . Unless  the Hypervisor is able to authenticate the access to the SMB3 share is blocked. In our case it was not possible because the 2 DC VM’s were powered off and unable to power it on.(Chicken and Egg situation)

Error Message I received:

The below Nutanix article explains the below:

Source:https://portal.nutanix.com/#/page/kbs/details?targetId=kA032000000TTGWCA4

So the conclusion is that you must need either a physical domain controller or a DC VM that does not sit on the SMB3 share. Hopefully the Windows 2016  may come up with a solution for this scenario.

Update1: As a last resort , I changed the Virtual disk path from on the DC VM from the FQDN  of the cluster name to the IP address of the cluster , voila I was able power it on the 2 VM’s(but I do not have any clue how this has worked)

Entry filed under: Nutanix. Tags: hyper-v cluster 2016, Nutanix, smb3 shared based hyper-v cluster, Windows 2012 r2.