The redirection of peripheral device can be configured in
the "Peripherals" section of Setup UI for both RX300 and RX-RDP thin
clients. To simplify the setup there are three general redirection policies,
which can be selected: Corresponding description below
· Default – this is the right choice for
typical users. Best possible redirection types are pre-selected. On RX300
devices the default selections are optimized for UXP connections. On RX-RDP
devices the selections are optimized for RDP connections.
· Custom – this is the most flexible
selection, which allows the administrator to decide what devices will be
redirected and which not, and what redirection method will be used for each
device class. Additionally, devices not reporting any supported device class
(e.g. reporting the USB class 255, which is the vendor-specific class) can be
added for the Generic USB redirection as custom devices (identified by the
Vendor ID and Product ID).
The possible peripheral devices redirection types
(methods) are:
· No redirection – the device will not be
redirected to remote server.
· Native – protocol-specific, native
(functional) redirection will be used for the device. Such redirection
leverages functionality-specific virtual channel of remoting protocol and
usually provides optimized support for the peripheral device. When the Native
redirection is available for the peripheral device/protocol combination then
it’s advisable to use it, as for peripheral devices redirected with the Native
method the remote server ensures that only the session owner will have access
to the device.
· Generic USB – low level USB-based
redirection will be used for the peripheral device. A virtual USB host
controller on the server will detect the device and load a server-side device
driver for it. This redirection method usually generates more network traffic
compared with the Native method, as for Generic USB redirection the low-level,
raw USB communication will be redirected. Additional mechanisms must exist in
the server for filtering the devices and making sure that only the session’s
owner will have access to the device. If such mechanisms do not exit, it can
happen that only the console user or users of all terminal sessions will have
access to the redirected device.
Following redirection types are available for different
peripheral device classes and remoting protocols:
Peripheral device class | UXP protocol | RDP protocol |
Mass storage | No redirection, Generic USB | No redirection, Native |
Audio | No redirection, Generic USB, Native | No redirection, Generic USB, Native |
Printers | No redirection, Generic USB | No redirection, Generic USB |
Imaging devices (webcams) | No redirection, Generic USB | No redirection, Generic USB |
Smart card readers | No redirection, Generic USB, Native | No redirection, Native |
Serial ports | No redirection, Generic USB | No redirection, Generic USB, Native |
Human Interface Devices | No redirection, Generic USB | No redirection, Generic USB |
Custom devices | No redirection, Generic USB | No redirection, Generic USB |