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 CowperthwaiteSmall Business OwnerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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.
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.
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

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
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.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.