RemoteFX Prerequisites (Compact 7)

3/12/2014

To enable RemoteFX on your device, your server and your thin client device must meet certain hardware, software, and licensing requirements.

RemoteFX Requirements and Recommendations

A RemoteFX-enabled server running Windows Server 2008 R2 and a RemoteFX-enabled thin client device must meet the following requirements and recommendations. For more information about the hardware requirements for deploying RemoteFX, see Hardware Considerations for RemoteFX.

Server Requirements

A RemoteFX-enabled server must meet the following requirements:

Thin Client Device Hardware Requirements and Recommendations

The following configuration is recommended for thin client device hardware so that your devices can take advantage of RemoteFX functionality when they connect to virtual desktops through an RD Virtualization Host or RD Session Host server:

  • Display chipset that supports 32 bits per pixel (BPP) color depth.
  • 100 megabits per second (Mbps) or greater, wired network adapter. For better performance, use a 1 gigabit per second (Gbps) network adapter.
  • Human interface device (HID) mouse and keyboard.
  • 128 MB or larger primary storage volume.
  • 512 MB RAM or greater.
  • 32 BPP hardware cursor support.

The following configurations are also recommended:

  • Local time of both the server and device should match. The method for setting the accurate time in the operating system at run-time. The operating system time can be set by a real-time clock (RTC), a network time service, or another method.

    Important

    When you establish a secure RDP connection to the server, if the local time of the device does not match the time stamp of the certificate being issued by the server, the server rejects the RDP session request.

  • LAN network should have a latency of 20 milliseconds or less. RemoteFX is optimized for a LAN network. A LAN network that has a latency of 20 milliseconds or less is recommended.
    In addition, the following decoding requirements and recommendations apply:

    • RemoteFX software decoding. Requires a CPU processor that is enabled with an SSE2 instruction set. For best results, use a 2 gigahertz (GHz) CPU. If the CPU speed is lower than 400 megahertz (MHz), a RemoteFX session is not established. Hardware-accelerated BitBlt in the device driver is recommended, which helps reduce workload on the CPU.
    • RemoteFX hardware-assisted decoding. Requires a 1 GHz ARM or x86 CPU and a RemoteFX decoder, such as an ASIC or a digital signal processor (DSP) that has a corresponding RemoteFX display driver. For better performance, it is recommended that the display driver also support hardware-accelerated BitBlt.

See Also

Concepts

Design and Implement RemoteFX Display Drivers