An Up-Close Review of Microsoft RemoteFX in Windows Server 2008 R2 SP1 and Windows 7 SP1

In the upcoming Windows Server 2008 R2 Service Pack 1 and Windows 7 Service Pack 1 Microsoft is introducing a technology called RemoteFX which will prove to be groundbreaking for anyone that knows RDP (which is probably everyone that reads this). In this article we will have a look at what RemoteFX exactly is, what it can do and what it cannot do and how it works under the covers.


About 2.5 years ago Microsoft announced that they had acquired a company called Calista Technologies. This company was pioneering the science of virtualizing the GPU. It was very early days, so early even that Calista did not have a shipping product yet. Regardless, Microsoft decided to pick them up to, as it shows today, take RDP to a whole new level.

In March 2010 Microsoft announced a bunch of stuff around desktop virtualization. One of these announcements was the fact that Microsoft will introduce a technology called RemoteFX in Windows Server 2008 R2 Service Pack 1 and Windows 7 SP1. At the core of this RemoteFX is the technology from the Calista acquisition.

What exactly is RemoteFX?

The most common misconception that exists today is that RemoteFX is a new display protocol that will replace RDP. This is not true. RemoteFX is an umbrella term for a set of technologies that will enhance RDP. RemoteFX for example also includes USB redirection technology but that is out of scope in this article. In this article we will focus on the graphical user experience enhancements that RemoteFX brings to RDP 7.1 (the RDP version in Windows Server 2008 R2 Service Pack 1 and Windows 7 SP1).

When we’re talking about the user experience enhancements of RemoteFX, it’s important to distinguish between two distinct scenarios. That’s because there will be an implementation of the user experience enhancements of RemoteFX for VDI and one for Remote Desktop Session Hosts (RDSH). As we discuss these scenarios you will find out why they need to be treated separately somewhat.

RemoteFX for VDI (RD Virtualization Host)

This typically is what people are referring to when they talk about “RemoteFX”. At the core of RemoteFX for VDI is the ability to virtualize the GPU and share it among many users (or more accurately, virtual desktops). This ability to virtualize and share the GPU allows RemoteFX to deliver an unprecedented user experience with RDP unlike anything you have ever seen before with RDP. With RemoteFX the entire “content” of the desktop is rendered on the host utilizing that virtualized and shared GPU (and CPU/ ASIC as I will explain later). This “content” I am referring to is everything that is displayed during your Windows session, the desktop, web pages, HD movies, CAD, Silverlight, Flash and basically anything else you can think of.

There are three key aspects to RemoteFX for VDI that you need to keep in mind.

  • The virtualization and sharing of the GPU is a feature that is only available on Windows Server 2008 R2 Service Pack 1 with Hyper-V Role enabled. Actually, it is a new part of the RD Virtualization Host role.  So given the current incarnation of RemoteFX, RemoteFX will not work on other hypervisors – that means no VMware ESX and no XenServer.
  • RemoteFX for VDI does require a physical GPU in the physical Hyper-V R2 SP1 host.
  • Windows 7 SP1 is the only supported Guest OS (the virtual desktop) if you want to use the user experience enhancements of RemoteFX.

RemoteFX for Remote Desktop Session Hosts

What is very special about the graphical user experience enhancements of RemoteFX is that they also will be available for Remote Desktop Session Hosts (RDSH). The big difference is that this will not require a GPU. In fact, the whole GPU virtualization and sharing technology is absent in this implementation. The way content will be rendered and encoded is by means of the CPU (or an ASIC).

How does it work?

Now that we know that RemoteFX is able to deliver an extremely rich user experience with RDP by rendering all content on the host, let’s take a look at how this works under the hood.

RemoteFX for VDI

First, let’s take a look at RemoteFX for VDI since this is the implementation with the most “moving parts”. This is the architectural diagram of RemoteFX for VDI:

In this architectural diagram there are the following components:

  • (1) A VGPU driver. This driver presents the GPU to the virtual desktop. The virtual desktop (or more accurately the application in the desktop) does not know any better than that it has a dedicated GPU. The applications just send display commands to the GPU like they would on a regular physical desktop that is equipped with a GPU. The vGPU driver then takes these commands and sends them to the RCC via the VMBUS and Shared Memory. This is the GPU that you will see inside the virtual desktop:
  • (2) The RCC component is a process that runs in the parent partition per RemoteFX enabled virtual desktop that is responsible to actually process the content request from the applications. RCC stands for Render, Capture and Compress and this is exactly what it does:
    • First the “raw display instructions” are received from the vGPU driver and the content is rendered on the GPU (3)
    • Second the rendered content is captured. This means that RemoteFX will actually look at the frames that are being generated. It does so by dividing the screen into rectangles and watching which rectangles have changed and only selects those for transport. What is also very interesting is that the capture process also communicates with RDP to see if the client is able to process all of the display information. It might not be able to “take in” all of this display information because of limitations such as the network, client buffers, etc. If this is determined, the capture process will adjust accordingly and will actually send fewer frames. This happens all the time so you could call RemoteFX auto-optimizing in that sense.
    • Finally, after it has been decided which frames to send, the content is compressed and encoded. There are two ways to this. One is what Microsoft refers to as the software solution and this is using a combination of the GPU (3) and the CPU. The second way is to offload this to something called an ASIC (4). This is a special chip  specifically built to encode the display data coming from the RCC. The ASIC can provide offload capabilities for the encoding, but it is not mandatory; in contrast, since the GPU is used for rendering, it is mandatory. The big advantage of having an ASIC is that it relieves the GPU and CPU from encoding tasks, thus improving the scalability of the Hyper-V VDI host.

RemoteFX for Remote Desktop Session Hosts (RDSH)

When we look at RemoteFX for Remote Desktop Session Hosts (RDSH) it is a little different. As I mentioned earlier, this incarnation of RemoteFX does not support using a GPU in the Remote Desktop Session Host. Instead, this work is done by the CPU. Here’s how things work from an architectural perspective on a Remote Desktop Session Host:

Also the in the RDSH RemoteFX scenario, an ASIC can be used. In fact, it makes a lot more sense to consider investing in the ASIC in the RDSH scenario to offload the encoding because the CPU is generally much more heavily loaded than for VDI because of the higher number of sessions per host and lack of GPU which is used to offload the CPU for encoding in the case of VDI.

Client Devices

As I stated earlier, RemoteFX is not a replacement for RDP but rather different content in the RDP display channel. This is clearly shown in this overview of the RemoteFX architecture from a client perspective:

So, if you want to enjoy the richness of a RemoteFX experience you will need a RDP Client that is capable of decoding the RemoteFX payload. As the architecture shows, there’s two ways to go about this.

  • The “traditional way” using the latest versions of the RDP Client, 7.1 in this case. It has not yet been officially determined which Windows versions this will support – only Windows 7 are definite, but we expect Microsoft to reveal any plans for downlevel OS support in the future . Using the 7.1 RDP Client on, for example, your Windows 7 laptop will the use GPU and CPU with RemoteFX codec included in the 7.1 RDP Client on your laptop to decode the RemoteFX payload.
  • Another way to benefit from  RemoteFX is to use a client device that has a hardware decoder (ASIC). This is conceptually the same as the ASIC on a Hyper-V host we talked about earlier. While the ASIC on the Hyper-V host encodes the RemoteFX payload, the ASIC on the client device decodes the RemoteFX payload. Note that I am using the term “client device” and not just the term “Thin Client”. We’ll discuss why in the next paragraph about the Ecosystem.

The Ecosystem

Don’t worry; I am not trying to make a case about our changing climate. I am referring to the ecosystem around RemoteFX. Let me explain. Previous iterations of Remote Desktop Services, or RDP more specifically, traditionally have had a relatively low impact on the RDP ecosystem of partners. With RemoteFX this is significantly different and Microsoft is very aware of this. There are a couple of reasons why it is different when it comes to RemoteFX:

  • The need for a GPU or GPUs in your Hyper-V hosts to be able to leverage RemoteFX for VDI
  • The introduction of (optional) ASICs to the encode RemoteFX payload on the Hyper-V Virtualization Host or RD Session Host
  • (Optional) ASICs to decode the RemoteFX payload on the client device

Microsoft wants to make sure that it is easy as possible to get a RemoteFX-capable piece of hardware. Whether that is a server with a proper GPU and potentially an ASIC or whether it is a client device with a RemoteFX ASIC, it needs to be perfectly normal.

In theory this means that in the RemoteFX timeframe (when SP1 is released) when you order a new server you will just be able to check a box that will add a RemoteFX capable GPU and potentially an ASIC.

It is even cooler for client devices – all you really need is a RemoteFX decoder. These hardware decoders (ASIC) are relatively cheap to produce and have a very low system footprint. They enable a whole new line of client devices. One new type of client device is called an “Ultra Lightweight Thin Clients” (no I did not make that up but it made me think, what’s next, Sub-Zero Clients?). These are very interesting devices that can use as little as 3 Watts of power and are rumored to be available at as low as $100 when launched! Imagine that – a full fidelity user experience on a $100 device! It does not stop at Thin Clients. The ASIC could easily be embedded in other devices as well. Think about monitors, TVs, tablets, phones… heck, even an XBOX could have such an encoder.

Of course a lot of the success of RemoteFX enabled client devices depends on acceptance by hardware manufacturers. Microsoft knows this and has made a very clever move in my mind: anyone can make an ASIC. Let me explain that: if you sign up as a RemoteFX partner you can get the specifications of the RemoteFX decoder and create your own ASIC. The key thing is that this is royalty free. Where other comparable solutions ask for a fee for every ASIC sold this is not the case with RemoteFX.

What can it do?

Anything! Well, from a display perspective at least. This is the really cool part. Since to the virtual desktop and its applications it appears that a “normal” GPU is available, almost all content can be rendered. RemoteFX is like a catch-all. Basically all kinds of “desktop content” can be viewed in near full fidelity in your virtual desktop.

For reference, these are examples of content that currently aren’t able to be delivered in full fidelity in today’s RDP version (7.0):

  • Flash
  • Silverlight
  • HTML5
  • Non-Windows Media format movies (many QuickTime movies still won’t play, for example)
  • 3D applications

RemoteFX solves all that … if you have the bandwidth. Again, because it is catch-all you can deliver almost any content type using RemoteFX. Think of content like this:

  • Office 2010
  • Full Aero desktop experience
  • Flash
  • Silverlight
  • HTML5
  • Any media format you can think of
  • 3D applications

What’s less cool?

Of course RemoteFX isn’t the most brilliant thing since the seedless watermelon but it is pretty darn close! There are a couple of characteristics – I would not call them drawbacks – which you have to be aware of though:

  • LAN only. Out of the box RemoteFX is a LAN technology only. Period. Microsoft is not being vague or secretive about this. Without a 10 Mbps of network bandwidth and latencies above 20ms it is not recommended to use RemoteFX. As is common, Microsoft points to the (software) RemoteFX partners for more than this out of the box functionality. Quest has announced that vWorkspace is slated to extend the reach of RemoteFX beyond the LAN within 30 days of the shipping date of Service Pack 1 (Brian Madden has published a preview of this). Similarly, Citrix (Harry Labana) has announced that they will be supporting RemoteFX approximately 6 months after Service Pack 1 ships.
  • Need for a GPU. You need a GPU in the Hyper-V host. Remember this is not just any GPU you get at your local geekshop – you need a server-class GPU with at least 1 GB of (V)RAM. Depending on your use case, you might even need more VRAM and/or more GPUs. The actual VRAM could be as low as 75 MB or greater than 200, depending on the resolutions in your VM. These guys don’t come cheap either but are expected to drop in price over time. The good news is that RemoteFX supports multiple GPUs in one server (provided they are the same). RemoteFX also supports so-called external “GPU Appliances”.
  • (Possibly) no 7.1 RDP Client for Windows XP. This article was written based on the beta of RemoteFX which includes RDC 7.1 for Vista and Windows 7 but not retail XP. At TechEd Microsoft could not say whether there would be a 7.1 RDP Client for Windows XP.
  • No OpenGL. Well, I said that RemoteFX could deliver almost any content type. Not all. OpenGL is an example of this. Because the RemoteFX 3D display adapter driver in the virtual desktop is based on DirectX, it will not support OpenGL apps beyond what Windows natively supports.
  • Hyper-V R2 SP1 only. You cannot use any other hypervisor than Hyper-V R2 SP1. Although it is pretty clear why Microsoft is doing this some people might perceive this to be a disadvantage of RemoteFX.
  • Windows 7 SP1 only. Windows 7 SP1 is the only supported Guest OS (the virtual desktop) if you want to use the user experience enhancements of RemoteFX.


Many people complained that Microsoft took too long to implement the Calista technologies into what was clear from the first minute- RDP. I personally think that Microsoft wanted to wait until all the pieces were in place to start yet another game of chess (or a more violent sport) with their good friends VMware. These pieces are not only assimilating the Calista technologies into Windows but also building the RemoteFX Ecosystem. They even decided to include a major feature as big as RemoteFX into a service pack which is pretty uncommon for Microsoft.

If it wasn’t clear, RemoteFX is (in many ways) Microsoft’s answer to PCoIP. In fact, in the same announcement that talked about RemoteFX, Microsoft also announced another feature of Service Pack 1 called “Dynamic Memory”. Dynamic Memory could be perceived to be as a countermove against VMware’s “memory overcommit”, which many people agree is one of the big things lacking in Hyper-V today. The comparison is very interesting, but beyond the scope of this piece.

Regardless of what Microsoft wants to achieve with RemoteFX (or Service Pack 1 as a whole) RemoteFX will have a great impact on desktop virtualization. It will change the way we buy servers, it will change the client devices we buy (and why we buy them) and it will change the “RDP user experience”. I am not saying it will happen overnight but in time it will happen.

A question that I get a lot as well is if I think if RemoteFX will replace all other remote display protocols such as Quest EOP or Citrix HDX. I think RemoteFX will not replace these protocols. Even though there is some overlap – in particular, RemoteFX is similar to Citrix HDX 3D Pro – Microsoft has created an ecosystem around RemoteFX that allows for partners to embrace and extend RemoteFX. It is much more likely that RemoteFX will be supported by protocols from these, and other, vendors, who will continue to extend and enhance Microsoft’s Remote Desktop platforms.

Filed under: Articles Leave a comment
Comments (1) Trackbacks (2)
  1. RemoteFX will certainly deliver improved performance of graphics content for LAN users. However, it may have some issues in a high latency/low bandwidth WAN environment. For slow WANs, organizations that want to enable access for remote users should seriously consider complementing it with Ericom Blaze, a software-based RDP acceleration and compression product. It accelerates RDP by up to 25x and is ideal for remote users connecting over slow WANs who need to access graphics-rich content and applications.

    Blaze works with any standard RDP host, including VDI, Terminal Servers and remote physical machines.

    Read more about Blaze and download a free evaluation at:

    To read more about WebConnect and RemoteFX visit:


Leave a comment