- Hyper-V Host (Windows 2012 R2) to be configured for virtual machine-based VDI
- One network for VMs and host (not external) with static IP and DNS
- One network for external with dynamic IP and DNS
- Domain controller is a VM on the Hyper-V host
- On the internal network not the external network with static IP
- Is the DNS server for the domain
RD Virtualization Host Configuration Failed on machineName.domain.com With Error: Could not create the Windows Management Instrumentation Windows Firewall exception on machineName.domain.com.
In my case this was because the Hyper-V host started using the DNS from the dynamic interface instead of the internal network and lost track of the domain. The network that had the domain controller was being detected as a public network instead of a domain network. My fix was to change the IPv4 configuration on the external network to use static DNS servers and not enter any DNS servers. The Hyper-V Host then used DNS on the DC and detected everything properly.