Feature Overview
The goal of RemoteFX USB redirection is simple: the user should be able to use any device they want, and have it just work. RDP has numerous high-level redirections that allow specific types of devices to be used effectively in a remote session, such as:
Easy Print, which allows users to print to local printers in remote sessions
Drive Redirection, which allows users to access the file system on any local drive in a remote session, including USB drives
Smart Card Redirection, which allows users to authenticate to and in a remote session by using smart cards/e-tokens
Plug-and-Play Device Redirection, which allows users to access PTP digital cameras, MTP music players, and POS for .NET devices in a remote session, among others
Input Redirection, which allows the use of keyboards/mice in remote sessions
Audio Redirection, which allows recording and playback of audio in remote sessions
Port Redirection, which allows the use of serial and parallel ports in remote sessions
However, there are many devices which are not covered by these redirections, such as scanners, multifunction printers, webcams, and more. RemoteFX USB redirection acts as a catch-all mechanism that redirects these USB devices! Unlike high-level redirections such as drive redirection, RemoteFX USB redirection happens at the port protocol (USB request block or URB) level, and is similar to how one can redirect serial or parallel ports via RDP. This provides some unique advantages, as you’ll see below. However, RemoteFX USB redirection is meant to supplement high-level redirections, not to supplant them. By combining RemoteFX USB redirection with RDP high-level device redirections, you can have the best of both worlds. Here is a table that compares and contrasts the two forms of redirection.
Read more: Remote Desktop Services (Terminal Services) Team Part 1, Part 2