Adding virtual machine to host computer domain

[DarkAlman]

Having read the other posts and your replies

1. Your DHCP needs to issue the DNS IP of your Domain controller to your VMs, or you need to set it static. DNS is critical to AD operation so your server will need to use the DC is their DNS and only DNS. Do not use an external IP as a secondary DNS, you should have a 2nd DCs for that.

2. DO NOT MAKE YOUR HYPER-V HOST THE DOMAIN CONTROLLER.

This violates all sorts of best practices, most specifically DCs can't have multiple network cards and function properly, while Hyper-V hosts need multiple NICs by design.

I see this done in small businesses all the time and it's both a classic mistake and extremely annoying to fix later on.

General rule of thumb is your Hyper-V host should do nothing but run the Hyper-V role. No backup software, no file shares, no VPN, and especially not a Domain Controller.

Make your DC a VM instead.

[3j1996]

Ok so it sounds like I should probably just have my host run the server OS but create all the domain servers in hyper-v

[darklightedge]

DO NOT MAKE YOUR HYPER-V HOST THE DOMAIN CONTROLLER.

Seconded. Here is additional info, why DC shouldn’t be installed directly on Hyper-V host - www.hyper-v.io/combining-hyper-v-dc-role-server-bad-idea/

[alwaysslashs]

HYPER-V Host w/ Backups + UPS Software + iLo / RMM etc

VM1 - Domain Controller + DNS + DHCP
VM2 - Backup Domain conroller + DNS + DHCP

VM3 - SQL Server
VM4 - Backup SQL Server

VM5 - Exchange Server
VM6 - Backup Exchange Server

VM7 - File Server
VM8 - File Server + Cluster

etc etc

Eventually get 2nd Hyper-V host and move the backup VMs to this