Hi, I’m Shanmugam Kulandaivel, a senior program manager on the Remote Desktop Virtualization team. As most of you know, both the Windows 8 and Windows Server 2012 operating systems are available in multiple editions. I’d like to use this blog post to provide details on the features of Microsoft RemoteFX® that are supported in each edition of Windows 8 and Windows Server 2012.
Before I provide the details, I’d like to start with a summary:
With that summary in mind, let’s first look at the features that Windows 8 and Windows Server 2012 editions support when running on client computers, and then we’ll look at the features that Windows 8 and Windows Server 2012 support when running on remote computers.
Client computer refers to the computer that the user is physically logged on to. Users use Remote Desktop Connection (RDC) on the client computer to connect to remote computers. The following table lists the features that are supported on client computers running any one of the different editions of Windows 8 and Windows Server 2012.
Operating systems for client computers
Windows 8 Pro
Windows 8 Enterprise
Windows Server 2012
Windows 7 Enterprise with RDP 8.0 Update
Ability to connect to remote computers
Ability to use RemoteApp
Support for redirection features, such as RemoteFX USB Redirection, drive redirection, and smart card redirection
RemoteFX for WAN with RemoteFX Network Auto-Detect
RemoteFX virtual graphics processing unit (vGPU)*
RemoteFX Adaptive Graphics and RemoteFX Media Streaming
RemoteApp and Desktop Connections
Email discovery of remote applications and remote computers
Remote Desktop Windows Store app
Support for all other RemoteFX features
* Requires that the remote computer be configured with RemoteFX vGPU.
The key takeaway is that users can use any edition of Windows 8 or Windows Server 2012 on their client computers and experience all the new features of RemoteFX.
Remote computers are the computers that users connect to. Remote computers can be a physical computer, a Remote Desktop Session Host server, or a virtual machine. The following table lists the features that are supported on remote computers running any one of the different editions of Windows 8 and Windows Server 2012.
Operating systems for remote computers
Windows 8 and
Windows Server 2012 Remote Administration Mode
Windows Server 2012 RD Session Host
Ability to connect to remote computers
Support for basic redirection features, such as
Clipboard redirection, drive redirection, and smart card redirection
Support for advanced device redirection features,
RemoteFX USB Redirection, and PnP device redirection
Remote Desktop Easy Print
Audio playback redirection
Multimedia redirection (WMV redirection)
User profile disk
RemoteFX virtual graphics processing unit (vGPU)
While this might seem like lot of specifics to remember, in reality, the feature differentiation is very simple. You just need to remember the following summary when deciding which edition to use for your virtual machine-based desktop deployment:
I hope this information is useful and answers the questions that you have on this topic. If you have more questions, please feel free to post a new thread in the RDS & TS forum.
RemoteFX supports OpenGL 1.1 with CPU acceleration.
Looks like I am having the same problem as many, I have a new Dell with an AMD S9000 and unable to have a VM of W2K12 running RDSH where clients can use the graphics on this VM or clients connect to the host to use the graphics. If this is by design, it should not be...when will this be resolved?
I would like to use vGPU with RDSH in a Hyper-V VM (Windows Server 2012 R2) as well. I do not understand why this is not supported...
I am a customer who has just splashed out on Windows 8.1 Pro.
NB: There is no client-server relationship here, just one PC.
However, I have important 32-bit only applications that won't even install on this 64-bit OS, and they need a GPU to run them.
PS: Please don't tell me not to use the 32-applications as that would be very arrogant, and they were very expensive. Thank you.
Ok, so to solve this I have installed a 32-bit Windows version in a VM using Hyper V, and my applications will install ok within that VM.
However, they still won't run because they can't detect the GPU.
How do I get this "RemoteFX vGPU" thing working so they can see the GPU in my machine?
This must be a very, very common scenario for everyone thinking of upgrading to Windows 8.1.
Will Microsoft help out, or do I need to maintain a second PC just for my 32-bit applications?
How can i connect a diskless client to remotefx server that is Hyper-V VIRTUAL desktop. Is there any guide or procedure ? Pls. share with me
Shanmugam, as I understand, with Remote FX, you can use a scanner, connected via USB on a remote computer to scan documents directly to a server via remote desktop....is that true? If so, what are the requirements of the scanner? and particular brand or model?
Is a Windows 8(or 8.1) Enterprise physical machine capable of providing a 'RemoteFX encoding for RemoteFX clients designed for Server 2008 R2 SP1'?
@Ethos Unum, yes RemoteFX encoding is also available for physical machines. the key feature that is not available for physical machines is RemoteFX vGPU ie the capability to use a Virtualized GPU.
Are there any plans to support sensor redirection (e.g. accelerometer, gyroscope, and camera)?
According to this grid, I should be able to have the host computer be Windows 8(.1?) and have a Windows 8 OS in the VM and be able to enable USB pass-through. I am not finding how to enable this like I can on my Windows Server 2012 R2. I am trying to pass-through a USB dongle to the VM. On the R2 server, it added a RemoteFX option and let me select the dongle. This is not working on the Win 8 host.
The grid says yes but I am unable to get it working...Ideas?