5.2

Table Of Contents
n
A
redirected USB device stops working if you reconnect a desktop session even if the desktop shows that
the device is available.
n
USB redirection is disabled in View Administrator.
n
Missing or disabled USB redirection drivers on the guest.
n
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."
Solution
n
If available, use PCoIP instead of RDP as the desktop protocol.
n
If a redirected device remains unavailable or stops working after a temporary disconnection, remove the
device, plug it in again, and retry the redirection.
n
In View Administrator, go to Policies > Global Policies, and verify that USB access is set to Allow under
View Policies.
n
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.
n
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.
Troubleshooting Desktops That Are Repeatedly Deleted and Recreated
View Manager can repeatedly delete and recreate linked-clone and full-clone desktops that are in an Error
state.
Problem
A linked-clone or full-clone desktop is created in an Error state, deleted, and recreated in an Error state. This
cycle keeps repeating.
Cause
When a large desktop pool is provisioned, one or more virtual machines might end up in an Error state. The
View Manager automatic recovery mechanism attempts to power on the failed virtual machine. If the virtual
machine does not power on after a certain number of attempts, View Manager deletes the virtual machine.
Following the pool size requirements, View Manager creates a new virtual machine, often with the same
desktop name as the original desktop. If the new virtual machine is provisioned with the same error, that
virtual machine is deleted, and the cycle repeats.
Automatic recovery is performed on linked-clone and full-clone desktops.
If automatic recovery attempts fail for a virtual machine, View Manager deletes the virtual machine only if it
is a floating desktop or a dedicated desktop that is not assigned to a user. Also, View Manager does not delete
virtual machines when pool provisioning is disabled.
Solution
Examine the parent virtual machine or template that was used to create the desktop pool. Check for errors in
the virtual machine or guest operating system that might cause the error in the virtual machine.
VMware Horizon View Administration
398 VMware, Inc.