New and existing RemoteFX-enabled VMs do not start on a DC that is running the Remote Desktop Virtualization Host service on Windows Server
This article provides a solution to an issue where which new and existing RemoteFX-enabled virtual machines cannot run on a domain server.
Original product version: Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2008 R2 Service Pack 1
Original KB number: 2506417
You have a server that is running the Remote Desktop Virtualization Host service on Windows Server. When you configure Active Directory Domain Services (AD DS) on the server to add the server as a domain controller, you experience the following symptoms:
- All existing RemoteFX-enabled virtual machines (VMs) do not start.
- An administrator cannot create a RemoteFX-enabled VM.
To resolve the issue, use one of the following methods.
Remove the RemoteFX 3D video adapter from the VM. To do this, follow these steps:
- Open Hyper-V Manager. To do this, click Start, point to Administrative Tools, and then click Hyper-V Manager.
- In the details pane, under Virtual Machines, select the VM that you want to configure. The VM must be off for you to be able to change its settings.
- In the Action pane, click Settings under the virtual machine name.
- In the navigation pane, click RemoteFX 3D Video Adapter.
- Click Remove, and then click OK.
Reconfigure AD DS so that the server that is running the Remote Desktop Virtualization Host service is not a domain controller. Instead, make the server a member server or a member of a workgroup.
This behavior is by design. Running AD DS on a server that is also running a RemoteFX-enabled VM is not a supported configuration.