Hyper-V Domain Setup

I am using two host computers running Server 16 to setup 4 VM servers for a new domain. Host1 will have VM1 as the domain controller and VM2 as the Exchange Server. Host 2 will have VM3 as the secondary domain controller and VM4 as the file and application server.
Do the host machines need to join the network after the domain controller is up and running? what is the best practice?
Rick Cowperthwaite
Rick's Energy Solutions
Rick CowperthwaiteAsked:
Who is Participating?
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
In a client setting where we have two hosts with one DC per host we join the hosts to the domain.

Microsoft dealt with the Chicken and the Egg dilemma a long time ago as far as booting standalone domain joined or clustered hosts with no DCs online. There is no worries there plus one could always log on with the local admin account if things were hung up which can happen.

Having the hosts on the domain makes management simpler, but keep in mind that users should _not_ have write access to any shared resources on the host so as to protect them from an encryption or other compromise event.
David AtkinTechnical DirectorCommented:

This is a good read for you :)


But basically, the answer is yes you should probably add the host onto the domain.
Lee W, MVPTechnology and Business Process AdvisorCommented:
I agree - I usually add the systems to the domain and put them in a separate OU for Hyper-V servers.
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

No need to add hosts to domain unless you are configuring hyper-v failover cluster, it is not requirement

If you have any legal / compliance requirement, then you need to.
if you add host to domain, you need to change startup option of VMs hosting active directory to "start with host operating system" to avoid login issues on hyper-v host in case you reboot it.
Lee W, MVPTechnology and Business Process AdvisorCommented:
I almost always join to the domain, never had any login issues.
when DCs are hosted as virtual machines on hyper-v host and those are only DCs available in network, post rebooting hyper-v host, DC VMs remain offline and hence hyper-v host cannot find Dc to logon with, it will logon but with cached credentials, hence need to change the DC VM startup option as commented earlier
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.