HP Remote Graphics Software 6.0 User Guide

RGS works very closely with the Windows USB driver stack. Any USB device that exclusively uses
the Windows USB driver stack for functionality should work with RGS. The less a USB device's driver
complies with the Windows USB driver stack, the less likely it will work with RGS.
NOTE: Devices that adhere to the USB standard should work. Because RGS is a remote graphics
protocol and is emulating the USB protocol over a network, devices that are sensitive to timing may
not work at all. This includes USB devices with security and encryption mechanisms built into them.
The additional network delay could be looked at as a threat. Other devices that are known to break
the USB standard, such as webcams, may also not function at all. Performance of USB devices over
RGS will not be equal to that of a locally connected device. File copies may take longer due to the
additional overhead of the network protocol sitting on top of the USB protocol.
HP recommends that customers thoroughly test any USB device they are considering to use with
RGS as Hewlett-Packard cannot certify and or guarantee it will work over a Remote USB protocol.
Many USB vendors do not support their devices over any Remote USB protocol and you should
check with the USB vendor for support concerns first.
Unique smart card handling
Smart card readers are handled in a unique manner, as follows:
●
Unique smart card handling requires, on the Sender, that Easy Login be enabled.
Windows XP—The chaining GINA module msgina.dll will be utilized.
Windows 7—The HP ELO Credential Provider will be utilized.
●
Unique smart card handling also requires that the local and remote computers both be running
Windows.
●
For USB configuration settings USB devices are Remote and USB devices are Local/Remote,
smart card readers will always be accessible by the local computer prior to establishing a
connection to a remote computer. This is to allow the smart card reader to be used by the local
computer prior to using the smart card to authenticate access to the remote computer.
●
The USB devices are Remote and USB devices are Local/Remote settings are effectively
ignored for smart card readers. In particular, the USB devices are Remote setting is ignored as
evidenced by the smart card reader being locally accessible prior to establishment of an RGS
connection. Similarly, the USB devices are Local/Remote setting is ignored as evidenced by the
locally-accessible smart card reader automatically becoming remotely accessible once an RGS
connection is established.
●
If a smart card reader is plugged in after an RGS connection is established, it will be available
remotely.
●
If there is a break in the RGS connection, the smart card reader will become locally accessible.
If RDC is used to connect from the local computer to the remote computer, it is possible to get into a
situation where the smart card reader cannot be used to log into the remote computer (for details on
the interoperability of RGS and RDC, see
Interoperability of RGS and Microsoft Remote Desktop
Connection on page 108. This situation can arise as follows:
1. The user uses a smart card reader to log into the remote computer with RDC. Assume that this
login session is established from the user’s home.
2. Assume further that the user inadvertently leaves the RDC login session established, and
departs for work.
3. From work, the user attempts to log into the remote computer with RGS using an at-work smart
card reader in Easy Login mode (which is required for the smart card reader, as noted
Remote USB 75