I have hundreds of on premise VDI's built around Hyper-V servers with thin clients running RDP utilizing RemoteFX. I was a complete devastated to learn that Microsoft was suddenly forcing all users to abandon RemoteFX in one of the recent Windows updates. And even more so to read that it cannot be used past Feb 2021, see Microsoft's link below. Information,12/1/2017 1:00:51 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,141,RemoteFX module,PerfCounter session started with instance ID 3 Information,12/1/2017 1:00:51 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,72,RemoteFX module,Interface method called: SendPolicyData Information,12/1/2017 1:00:51 PM,Microsoft-Windows. Microsoft RemoteFX is a Microsoft brand name that covers a set of technologies that enhance visual experience of the Microsoft-developed remote display protocol Remote Desktop Protocol (RDP). RemoteFX was first introduced in Windows Server 2008 R2 SP1 and is based on intellectual property that Microsoft acquired and continued to develop since.

Microsoft RemoteFX is a Microsoft brand name that covers a set of technologies that enhance visual experience of the Microsoft-developed remote display protocol Remote Desktop Protocol (RDP).^[1] RemoteFX was first introduced in Windows Server 2008 R2 SP1 and is based on intellectual property that Microsoft acquired and continued to develop since acquiring Calista Technologies.^[2] It is a part of the overall Remote Desktop Services workload.

History[edit]

Windows Server 2008 R2 SP1[edit]

RemoteFX components introduced in Windows Server 2008 R2 SP1 include:

RemoteFX vGPU: the ability to present a virtualized instance of a physical GPU into multiple Windows 7 virtual machines. This provides VMs with access to the physical GPU, enabling hardware-acceleration for rich graphics scenarios such as 3D rendering and game play.
RemoteFX USB Redirection: generalized support for redirecting USB devices into Windows 7 VMs. This allows peripheral devices connected to thin client terminals to be used within virtual machines.^[3]^[4]
RemoteFX Codec (also referred to as RemoteFX Calista Codec): a lossy codec that is capable of preserving a high-fidelity experience for both video and text. The RemoteFX Codec does not require any special hardware, and uses the CPU for encoding.^[5]

Windows Server 2012[edit]

In Windows Server 2012, the following components were added to RemoteFX.^[6]

RemoteFX Adaptive Graphics: The RemoteFX graphics pipeline dynamically adapts to various runtime conditions, such as graphic content types, CPU and network bandwidth availability, and client rendering speed.^[7]
RemoteFX for WAN: a series of changes to the network transport pipeline to support UDP and ensure a fluid experience in both WAN and wireless network configurations.^[8]
RemoteFX Multi-Touch: supports remoting of gestures (e.g. pinch and zoom) between the client and host with up to 256 touch points^[9]
RemoteFX Media Redirection API: allows Voice over IP (VoIP) applications to natively integrate with RemoteFX, and enables transmission and rendering of audio and video content directly on the client side.^[10]
Choice of GPU: All RemoteFX features can be used with either a software-emulated GPU, which is available by default in all virtual machines and session hosts, or they can benefit from hardware acceleration when a physical video card is placed in the server and the RemoteFX vGPU is enabled.^[11]

In addition, the following components were updated:

RemoteFX vGPU: updated to support DirectX 11^[9]
RemoteFX USB Redirection: updated to support all desktop remoting scenarios vGPU-enabled virtual machines, traditional VMs, desktop sessions and physical desktop hosts^[9]
RemoteFX Codec (also referred to as RemoteFX Progressive Calista Codec): updated to include progressive rendering, which is more effective for rendering content over the WAN by sending images at full resolution only if bandwidth permits.^[12]

Windows Server 2016, Windows 10 Enterprise[edit]

In Windows Server 2016 (RDP 10), the following components were added to RemoteFX.^[13]

OpenGL 4.4 and OpenCL 1.1 API support in a virtual machine with the RemoteFX adapter
More dedicated VRAM for the RemoteFX adapter
Various performance improvements in transport and API implementations

RemoteFX Media Streaming (H.264) replaced Multi Media Redirection (MMR). Note: MMR is now completely removed from RDP 10 given that RemoteFX Media Streaming works for all types of video content whereas MMR which just worked for some.^[14]

RemoteFX vGPU Deprecation[edit]

Beginning in July 2020 RemoteFX vGPU was deprecated in all versions of Windows because of security vulnerabilities. It was scheduled to be completely removed in February 2021.^[15]

Requirements[edit]

In Windows Server 2008 R2, the RemoteFX Codec could be leveraged for both session hosting (Remote Desktop Session Hosts) and VDI scenarios (and Remote Desktop Virtualization Hosts). The RemoteFX vGPU and RemoteFX USB Redirection features could only be used in VDI scenarios (Remote Desktop Virtualization Hosts).^[16]

Windows 10 version 1511 brings RemoteFX to client Hyper-V, removing dependency on Remote Desktop Services role.^[17]

Generation 2 VMs on Windows Server 2012 R2 do not support RemoteFX.^[18] Windows Server 2016 added such support.^[19]

In Windows Server 2012, all features of RemoteFX (with the exception of the vGPU) can be used with or without a physical GPU present in the server.^[20] When no GPU is present in the server, a synthetic software-emulated GPU is used to render content. When a GPU is present in the server, it can be used to hardware accelerate the graphics via the RemoteFX vGPU feature.

RemoteFX vGPU Requirements[edit]

The RemoteFX vGPU has the following requirements:^[21]

Hyper-V must be installed on the server. The VMs must be created and run using Hyper-V.
The server's CPU must support Second Level Address Translation (SLAT), and have it enabled.
For Windows Server 2008 R2 SP1, at least one DirectX 9.0c and 10.0 capable graphics card must be installed on the server.
For Windows Server 2012, at least one DirectX 11.0 capable graphics card with a WDDM 1.2 driver must be installed on the server.^[22]
The host machine must not be a Domain Controller. For single server configuration, Microsoft supports running Domain Controller as a Hyper-V virtual machine.^[23]

Windows Server 2008 R2 with SP1 has been tested for up to twelve virtual machines per GPU, for a total of twenty-four virtual machines on two physical GPUs.^[21]

Although any GPU meeting the above requirements will be capable of using RemoteFX, the Windows Server Catalog carries an additional qualification to further define the requirements for server-qualified GPUs. These specifications define GPUs configuration requirements and provide VM performance targets.^[24]Graphics cards that meet these are typically professional workstation products such as ATI/AMD's FirePro, v5800, v5900, v7800, v7900, v8800, v9800, and Nvidia's Quadro 2000, 3800, 4000, 4800, 5000, 5800, 6000, Quadro FX 2800M and 880M, QuadroPlex 7000 and Tesla M2070Q.^[25]

Servers running the RemoteFX vGPU need to accommodate such graphics cards with either larger power supplies and more PCIe slots^[26] or alternatively connect existing servers to an external PCIe expansion chassis.

Guest OS requirements[edit]

The RemoteFX virtual graphics adapter is only supported by Enterprise editions of Windows,^[27] starting from Windows 7 SP1. Other editions are missing the required drivers to use the RemoteFX g

Microsoft Remotefx