New and existing RemoteFX-enabled VMs do not start on a DC that is running the Remote Desktop Virtualization Host service on Windows Server

Applies to: Windows Server version 1803Windows Server Datacenter CoreWindows Server Standard Core More

Symptoms


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.

Resolution


To resolve the issue, use one of the following methods.

Method 1

Remove the RemoteFX 3D video adapter from the VM. To do this, follow these steps:

  1. Open Hyper-V Manager. To do this, click Start, point to Administrative Tools, and then click Hyper-V Manager.
  2. 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.
  3. In the Action pane, click Settings under the virtual machine name.
  4. In the navigation pane, click RemoteFX 3D Video Adapter.
  5. Click Remove, and then click OK.

Method 2

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.

Status


This behavior is by design. Running AD DS on a server that is also running a RemoteFX-enabled VM is not a supported configuration.