Over the last week tweeted ten times with tips on RemoteFX. In this article we will summarize them.
RemoteFX tip #1: Do not try RemoteFX on anything else than a decent LAN. More than 15-20 ms latency? Use a 3rd party (Quest, Riverbed etc.)
RemoteFX tip #2: Don't try RemoteFX without at least 10Mbps. Personal experience? At least 25 Mbps for best quality. Watch out for wifi.
RemoteFX tip #3: Do you know you can tune RemoteFX from a FPS and display quality perspective? Check the GPOs in here:http://bit.ly/eklBm5
RemoteFX tip #4: RemoteFX has a maximum resolution of 1920x1200 @ 1 or 2 monitors. More monitors = lower resolution.
RemoteFX tip #5: Your VM needs to have a RemoteFX virtual display adapter in the VM before you can use RemoteFX USB redirection.
RemoteFX tip #6: RemoteFX also offers USB device redirection, allowing you to use almost any USB device in VDI session. No RDSH support.
RemoteFX tip #7: Using RemoteFX requires the RDVH role on your Hyper-V box. This in turn means you need a RDCAL, just like RDSH.
RemoteFX tip #8: Did you know what RemoteFX is also available for RDSH (TS)? The great thing about this is that this does not require a GPU.
RemoteFX tip #9: RemoteFX requires the RDP 7.1 client. If there is not 7.1 client for your OS,then no RemoteFX. So no RemoteFX from WinXP...
RemoteFX tip #10: If you don't plan on using RemoteFX in your VM, don't add the RemoteFX display adapter.It uses a couple of 100 MBs of RAM.
This concludes my RemoteFX tip series. Did you find it useful? If you did, let me know and I will (try to) continue. Let me know in the comments.