Browse other questions tagged windows-10 remote-desktop nvidia-graphics-card h.264 remotefx or ask your own question. The Overflow Blog Level Up: Creative Coding with p5.js – part 6. RemoteFX is new age Remote Desktop Protocol and enables the GPU (GPU card) virtualization which means sharing a physical graphics adaptor among the multiple virtual machines The virtual machines can offload rendering of graphics information from the processor to the dedicated graphics processing unit (GPU card) attached to the host. Windows Server 2016 update KB4103723 is known to break RDPWrapper with RemoteFX (you will get remote desktop licensing error when you try to 'RDP' into a RemoteFX-enabled guest). Try to stick with Windows 10 1703 (15063.0) for guest operating system. Windows 10 1709 has some graphics driver issue when used as a RemoteFX-enabled guest.
Symptoms
RDP Connection attempts to a RemoteFX enabled Terminal Server fail, resulting in the following error on the client:
'The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your server administrator.'
The Terminal Server logs the following event:
Event ID: 1152
Source: TerminalServices-RemoteConnectionManager
Message: The Remote Desktop Virtualization Host server cannot issue a client license. It was unable to issue the license due to a changed (mismatched) client license, insufficient memory, or an internal error.
Cause
This problem occurs when standard RDP security is used by the client to connect to the RemoteFX server.
This can occur under the following conditions:
The client is a custom application using the Remote Desktop active control. This control uses standard RDP security by default.
The client is 3rd party or Windows Remote Desktop client that is configured to use standard RDP security. Windows XP SP3 and newer Remote Desktop clients use Enhanced RDP security by default and will not exhibit this problem. Older client operating systems use standard RDP security by default, and will exhibit the symptoms listed in this article.
Resolution
The client must be configured to use Enhanced RDP security.
If the client is a custom application using the Remote Desktop ActiveX control, the client must use minimum control version IMsRdpClientAdvancedSettings4 interface and set the AuthenticationLevel property to either 1 or 2 (default level is 0).
Windows XP SP2 clients running MSTSC.exe can work around this licensing problem by using RDP enhanced security (by selecting the 'Attempt authentication' Drop down in the security tab properties of the Remote Desktop Connection client.
This policy setting allows you to permit RDP redirection of other supported RemoteFX USB devices from this computer. Redirected RemoteFX USB devices will not be available for local usage on this computer.If you enable this policy setting you can choose to give the ability to redirect other supported RemoteFX USB devices over RDP to all users or only to users who are in the Administrators group on the computer.If you disable or do not configure this policy setting other supported RemoteFX USB devices are not available for RDP redirection by using any user account.For this change to take effect you must restart Windows.
Policy path:
Scope:
Windows 10 Rdp Enable Remotefx
Supported on:
Registry settings:
Windows 10 Rdp Disable Remotefx
Windows 10 Rdp Server
Filename: