DC on Hyper-V Cluster
Posted on 2014-03-27
I have two physical servers that are running 2012r2 and I want to create a hyperv cluster using these two physical servers and one physical NAS. I have done this previously without issue but I had an external domain controller in those situations.
In this situation I want the DC to reside on the hyperv cluster, for example on vmhost1 and an exchange server to run on vmhost2. I want them in a virtual environment so that they can fail over if one of the physical hosts fail.
I have read many docs for and against this scenario and can't find a conclusive answer. I am sometimes told that I need to make the nodes of the cluster DC's themselves so that a domain structure exists when they start. Others say that you can create the one and only DC on the vmhost and that if everything needs to reboot the vmhosts will startup up and start the DC vm even though the DC needs to be on first.
I was also told that exchange will not function on a vm is the host is a DC and that if I do virtualize my DC that it cannot be part of the failover cluster and must be manually failed over.
I am looking for general guidence on this type of setup and tips on how to implement it if you have done so already. How do I build the hyperv cluster without a DC to start with?
Thanks in advance.