locked
Windows 8.1 - Enable remotefx RRS feed

  • Question

  • Hi,

    What I am trying to achieve is to test out the USB redirection capabilities of RemoteFX. My host machine is Windows 8.1 Enterprise, as this has Hyper-V and as I understand it - RemoteFX too. How do I enable RemoteFX or is it automatically enabled as soon as I install Hyper-V role on the machine?

    Once it is enabled I will connect to my Host machine via RDP 8/RemoteFX enabled thin client and test out USB redirection by plugging in various USB devices into the thin client and see whether my host machine detects them.

    Will this test setup work? and give me similar results on what I can expect when I setup RDSH 2012R2

    Thanks


    • Edited by owen1978 Tuesday, September 23, 2014 2:23 PM
    Tuesday, September 23, 2014 2:23 PM

Answers

  • RemoteFX was first used as the marketing name for advanced graphics capabilities for virtual machines with Server 2008 R2 - http://technet.microsoft.com/en-us/library/ff817578(v=WS.10).aspx

    This feature has very picky hardware requirements for GPU; http://technet.microsoft.com/en-us/library/ff817602(WS.10).aspx

    The RemoteFX marketing term was later co-opted to mean anything delivered with more recent versions of the Remote Desktop Protocol - http://blogs.msdn.com/b/rds/archive/2012/11/26/remotefx-features-for-windows-8-and-windows-server-2012.aspx

    The Windows 8 and Server 2012 timeframe also introduced the vGPU in Hyper-V.

    So, you can get the 'RemoteFX' experience simply by having the latest RDP Server and Client installed.

    If you want the GPU virtualization (instead of the now default vGPU) then you need Hyper-V Server.


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.

    • Proposed as answer by Michael_LS Thursday, September 25, 2014 7:02 AM
    • Marked as answer by Michael_LS Friday, October 10, 2014 4:48 AM
    Wednesday, September 24, 2014 7:35 PM
  • Yes.  That is correct.

    The USB redirection has to be enabled on both ends.  It is usually on the 'server' side by default, but when you make the RDP connection from the client side you generally have to enable it.

    If you follow the matrix, you get the highest fidelity when the two sides match - 8.1 to 8.1 for example or 8.1 to 2012 R2.

    And then the fidelity goes down as you create combinations based on the lowest feature version. 

    So, you lose fidelity if one side is 8 or 2012, or win 7 or 2008 R2.  Unless you upgrade the Remote Desktop protocol (RemoteFX) stack to the latest version for both sides.


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.

    Thursday, September 25, 2014 3:35 PM

All replies

  • RemoteFx the VDI feature is only available with Hyper-V Server, not Client Hyper-V.

    Otherwise, enable RDP in your VM and connect to the IP of the VM directly.  And you will be using the native RDP protocol features (confusingly renamed RemoteFx by some marketing person) and the native USB redirection of RDP.


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.

    Tuesday, September 23, 2014 3:36 PM
  • Hi Brian,

    I'm getting confused...

    "Microsoft® RemoteFX™ enables access to the RD Session Host server from a wide range of client devices including rich clients, thin clients, and ultrathin clients."

    This was from a MS guide on how to deploy remotefx with RDSH, so it seems to me that RemoteFX is not just for VDI only for also RDS.

    Or am I missing something?


    Wednesday, September 24, 2014 8:23 AM
  • RemoteFX was first used as the marketing name for advanced graphics capabilities for virtual machines with Server 2008 R2 - http://technet.microsoft.com/en-us/library/ff817578(v=WS.10).aspx

    This feature has very picky hardware requirements for GPU; http://technet.microsoft.com/en-us/library/ff817602(WS.10).aspx

    The RemoteFX marketing term was later co-opted to mean anything delivered with more recent versions of the Remote Desktop Protocol - http://blogs.msdn.com/b/rds/archive/2012/11/26/remotefx-features-for-windows-8-and-windows-server-2012.aspx

    The Windows 8 and Server 2012 timeframe also introduced the vGPU in Hyper-V.

    So, you can get the 'RemoteFX' experience simply by having the latest RDP Server and Client installed.

    If you want the GPU virtualization (instead of the now default vGPU) then you need Hyper-V Server.


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.

    • Proposed as answer by Michael_LS Thursday, September 25, 2014 7:02 AM
    • Marked as answer by Michael_LS Friday, October 10, 2014 4:48 AM
    Wednesday, September 24, 2014 7:35 PM
  • Hi,

    To add, please also take a look at the following article about RemoteFX Explaining:

    Explaining Microsoft RemoteFX

    Quote from the Q&A:

    "

    RemoteFX has been designed as a Windows Server capability to support the growing demand for multi-user, media-rich centralized desktop environments.

    "

    Here are some additional references:

    RemoteFX vGPU Setup and Configuration Guide for Windows Server 2012

    Best regards


    Michael Shao
    TechNet Community Support

    Thursday, September 25, 2014 7:27 AM
  • Thanks again Brian for that link... I have seen that table before, thats what was confusing me...

    On the remote computer section... i.e the computer you rdp onto Windows 8 enterprise has

    "Support for advanced device redirection features, RemoteFX USB Redirection, and PnP device redirection" 

    If I RDP onto my laptop (Win 8 Ent) from a client thats on the supported client list, this will enableme to test out the remote fx

    USB redirection capabilities by plugging in various USB devices on the client and see whether the remote computer

    picks it up? Correct?

     

    Thursday, September 25, 2014 7:46 AM
  • Yes.  That is correct.

    The USB redirection has to be enabled on both ends.  It is usually on the 'server' side by default, but when you make the RDP connection from the client side you generally have to enable it.

    If you follow the matrix, you get the highest fidelity when the two sides match - 8.1 to 8.1 for example or 8.1 to 2012 R2.

    And then the fidelity goes down as you create combinations based on the lowest feature version. 

    So, you lose fidelity if one side is 8 or 2012, or win 7 or 2008 R2.  Unless you upgrade the Remote Desktop protocol (RemoteFX) stack to the latest version for both sides.


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.

    Thursday, September 25, 2014 3:35 PM