A RemoteFX-enabled server must meet the following hardware requirements:

• The server runs Windows Server 2008 R2 Service Pack 1 (SP1) with Hyper-V.
• The server also meets the hardware requirements that are listed in the Windows Server 2008 R2 Technical Library.

The following configuration is recommended for thin-client hardware so that your devices can take advantage of RemoteFX functionality when they connect to virtual desktops through an RD Virtualization Host or use the Remote Desktop Session Host (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 (also called a network interface card). 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 client 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 Remote Desktop Protocol (RDP) connection to the Windows server, if the local time of the operating system does not match the time stamp of the certificate being issued by the server, the Windows server rejects the RDP session request.

• Latency of LAN network: RemoteFX is optimized for a local area network (LAN). A LAN 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 a Streaming SIMD Extensions 2 (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 Advanced RISC Machine (ARM) or x86 CPU and a RemoteFX decoder, such as an application-specific integrated circuit (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.

You must meet the following software requirements to take advantage of RemoteFX functionality when your device connects to virtual desktops or the RD Session Host server.

• Windows server software requirements: For a list of specific editions of Windows Server 2008 R2 SP1 that support RemoteFX, see Microsoft RemoteFX.
• Windows Embedded Compact 7 thin-client software requirements: RemoteFX software requirements are Windows Embedded Compact 7 with support for Remote Desktop Connection 7.1.

System Integrators who want to develop RemoteFX hardware or implement the RemoteFX algorithm in a coprocessor need to obtain a RemoteFX Partner license. Partners who want to obtain this information are encouraged to contact their Technical Account Manager to learn more about becoming a RemoteFX Partner. If you are not a partner, see Microsoft RemoteFX for information about joining the partner program. RemoteFX software-only decoding does not require a RemoteFX Partner license.

• Windows Embedded Compact 7: RemoteFX Overview
• Getting Started with RemoteFX in Windows Embedded Compact 7 whitepaper: http://www.microsoft.com/windowsembedded/en-us/develop/windows-embedded-compact-7-white-papers.aspx
• Windows Embedded Compact 7: Remote Desktop Protocol