Various problems can arise with USB redirection in View Client.

USB redirection in View Client fails to make local devices available on the remote desktop, or some devices do not appear to be available for redirection in View Client.

The following are possible causes for USB redirection failing to function correctly or as expected.

USB redirection is not supported for Windows 2003 or Windows 2008 systems or for View desktops that are managed by Microsoft Terminal Services.

Webcams are not supported for redirection.

The redirection of USB audio devices depends on the state of the network and is not reliable. Some devices require a high data throughput even when they are idle.

USB redirection is not supported for boot devices. If you run View Client on a Windows system that boots from a USB device, and you redirect this device to the remote desktop, the local operating system might become unresponsive or unusable. See http://kb.vmware.com/kb/1021409.

By default, View Client for Windows does not allow you to select keyboard, mouse, smart card and audio-out devices for redirection. See http://kb.vmware.com/kb/1011600.

RDP does not support the redirection of USB HIDs for the console session, or of smart card readers. See http://kb.vmware.com/kb/1011600.

Windows Mobile Device Center can prevent the redirection of USB devices for RDP sessions. See http://kb.vmware.com/kb/1019205.

For some USB HIDs, you must configure the virtual machine to update the position of the mouse pointer. See http://kb.vmware.com/kb/1022076.

Some audio devices might require changes to policy settings or to registry settings. See http://kb.vmware.com/kb/1023868.

Network latency can cause slow device interaction or cause applications to appear frozen because they are designed to interact with local devices. Very large USB disk drives might take several minutes to appear in Windows Explorer.

USB flash cards formatted with the FAT32 file system are slow to load. See http://kb.vmware.com/kb/1022836.

A process or service on the local system opened the device before you connected to the remote desktop.

A redirected USB device stops working if you reconnect a desktop session even if the desktop shows that the device is available.

USB redirection is disabled in View Administrator.

Missing or disabled USB redirection drivers on the guest.

For View Client from View 5.0.x or earlier, missing or disabled drivers for the device that is being redirected on the client. View Client from View 5.0.x or earlier requires that you install the USB driver for a redirected device on the client. View Client from View 5.1 and later does not have this requirement."

If available, use PCoIP instead of RDP as the desktop protocol.

If a redirected device remains unavailable or stops working after a temporary disconnection, remove the device, plug it in again, and retry the redirection.

In View Administrator, go to Policies > Global Policies, and verify that USB access is set to Allow under View Policies.

Examine the log on the guest for entries of class ws_vhub, and the log on the client for entries of class vmware-view-usbd.

Entries with these classes are written to the logs if a user is not an administrator, or if the USB redirection drivers are not installed or are not working.

Open the Device Manager on the guest, expand Universal Serial Bus controllers, and reinstall the VMware View Virtual USB Host Controller and VMware View Virtual USB Hub drivers if these drivers are missing or re-enable them if they are disabled.