In Part 1 of our series on RemoteFX USB redirection, we looked at an overview of the feature and what it can do, and how to set up a basic deployment of the feature. In Part 2, we discussed publishing, deploying for rich and thin clients, RD Web Access, and server device security. Now, let’s take a look at your most frequently asked questions about RemoteFX USB redirection.
RemoteFX USB redirection
Supported while in a session
Not supported during logon
Plug and Play device redirection
MTP Media Player
Supported (LAN only)
Audio (not a USB composite device)
CD or DVD drive
Supported for read operations
Hard Drive or USB Flash Drive
Smart Card Reader
Smart card redirection
USB Network adapter (also includes some personal digital assistants)
USB Keyboard or Mouse
The highlighted devices are supported by RemoteFX USB redirection. Other devices in this table are supported by high-level device redirection mechanisms. Devices not listed in the table will be processed by using RemoteFX USB redirection; they may work, but are not considered officially supported.
When redirecting a USB VoIP phone or other USB audio device to the remote session, you have a choice between high-level audio redirection and USB audio redirection:
While high-level audio redirection is in use, USB audio redirection cannot be used, and vice-versa.
To adjust the audio settings for a remote session, in Remote Desktop Connection, go to the Local Resources tab, and in the Remote audio section, click Settings.
To use USB audio redirection: Set audio playback to Play on remote computer. On the Local Resources tab, in the Local devices and resources section, select the box to redirect the audio device over USB.
To use high-level audio redirection: Set audio playback to Play on this computer and audio recording to Record from this computer. On the Local Resources tab, in the Local devices and resources section, do not select the box to redirect the audio device over USB.
In Device Manager, expand Universal Serial Bus controllers, and find any of the USB root hub, USB hub, or USB controller devices. Right-click the device, then click Properties. On the Driver tab, click Driver Details. If RemoteFX USB redirection is properly installed and enabled, tsusbflt.sys will appear in the list of driver files provided.
* The usage of Office Communicator in a remote session is not officially supported at this time.
To learn more about RemoteFX USB redirection, see the “Configuring USB Device Redirection with Microsoft RemoteFX Step-by-Step Guide” on the Microsoft Technical Library: http://technet.microsoft.com/en-us/library/ff817581(WS.10).aspx .
I hope you’ve enjoyed our series of blogs on RemoteFX USB redirection. If you have any questions or comments, please post them to the blog. We look forward to hearing from you!
Do you have any information regarding support for hardware dongle license such as Hasp HL? www.safenet-inc.com/sentinelhasp. Many CAD style applications use this sort of licensing. As an ISV, our customers are looking to move the 3D CAD applications to VMs and which to use their dongle licensing on the VM.
So far we have been able to have the remote desktop client defect the HASP HL, but have yet to see it work on the VM.
Quote: "RemoteFX USB redirection is available for connections to VMs through RD Web Access and for RemoteApp programs running on RemoteFX-enabled Windows 7 SP1 VMs."
According to this, If I have a Windows 7 SP1 client and then make a (not RDWEB) RDP 7.1 connection to a Windows 7 SP1 VM on my Hyper-V box, it is not supported? I seems so, because I can't get it to work.
Why would I make a connection to a VM then try to run a remote APP from that VM and only then hope that I could use the scanner that is connected to my physical client? I haven't tested this because I don't see this as a real world scenario.
This USB RemoteFX redirection seems like it would be a highly desired feature yet it has the MOST baffling of all of the things that I've tried to get working in Microsoft's VDI offering.
Maybe I'm just too far out on the edge.
The article states:
In the situation I described, I am assuming the 'remote computer' is 20012TS1 - the Terminal Server hosting the session/desktop the user is working with not the physical Windows 7 computer the person used to run RDP to the Terminal Server i.e. Win7physical.
" On the Local Resources tab, in the Local devices and resources section, select the box to redirect the audio device over USB."
What devices are referred to here by "Local Resources and Local Devices" - devices on 2012TS1? Or devices on Win7physical?
"High-level audio redirection allows you to use your default Windows audio playback and recording devices in the remote session. The devices can be used in both the local and remote session at the same time. This mode works on both LAN and WAN. However, extended VoIP phone functionality/call controls will not work in this mode.
USB audio redirection is the preferred mode for those who want to use USB phones in their remote session. USB audio redirection allows the use of all features of your USB VoIP devices in the remote session, including call controls. However the USB audio device can only be used by the remote session while it is redirected. This mode is LAN-only."
By WAN do they mean logging in via RDP from a computer across the Internet ?
As far as WAN usage goes, do I not get any audio redirection at all via the USB Redirection or just not able to do VOIP type stuff over WAN? For instance with the USB redirection I was able to hear stuff on my headphones over the WAN.
"The devices can be used in both the local and remote session at the same time."
Does this mean if I had a USB phone directly attached to 2012TS1 as well as to Win7physical I could hear the audio on both - simultaneously? And if I was logged in via the Internet I could hear audio on both simultaneously? In other words if someone was seated at the server with a USB phone while I was logged in either via RDP across the LAN or RDP across the Internet with my USB phone they could hear everything I could hear and vice versa? If that's the case what would happen if we both spoke at the same time?
Your response to the above points is appreciated in advance.
I did all the steps, though I can see my biometric scanner I can't use it. It keeps saying that the device is disconnected. What can I do?
Thanks for the article. I know it's an old post, but we still use RemoteFX for Windows Server 2012 (R2) today.
RemoteFX is a amust for a VDI platform. The most we use is RemoteFX USB Redirection.
The problem i found is Redirecting voice over RemoteFX (using USB headsets). We are encountering voice latency (delays when speaking). I wish someone can told us the best practices when implementing VDI/Voice (CPU, RAM, NICs, buffers, switches).
(We encounter delays when using Cisco Communicator application)
I follow the instruction and I can see the drivers on both local ( WIN7 ) and remote ( Public Cloud ) but I can't let remote VM connect to my local headset still, I'm not sure where was wrong.
Thanks for the article. I wanted to know if RemoteFX is not installed, can we redirect device to specific session for RDSH base OS.
If yes how is that achieved. Is there a new driver that help to maintain session context and allow to redirect a device to specific session.
Nice read, well done! Just one thing is buggin' me.
'RemoteFX USB redirection, like the rest of RemoteFX, has been designed for LAN connections...'
Using RemoteFX across a VPN. Every once in a while, may be increasing to once a week now, the USB to Serial device will drop off. The users then have to reconnect/recheck the device from the RemoteFX button on the top blue connection bar.
Do we know how to make it more stable across a WAN connection? MTU settings may help (not so far from my experiences)?