7.0

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. For the location of these log files, see “Using
Log Files for Troubleshooting and to Determine USB Device IDs,” on page 219.
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.
Manage Machines and Policies for Unentitled Users
You can display the machines that are allocated to users whose entitlement has been removed, and you can
also display the policies that have been applied to unentitled users.
A user who is unentitled might have left the organization permanently, or you might have suspended their
account for an extended period of time. These users are assigned a machine but they are no longer entitled
to use the machine pool.
You can also use the vdmadmin command with the -O or -P option to display unentitled machines and
policies. For more information, see the View Administration document.
Procedure
1 In View Administrator, select Resources > Machines.
2 Select More Commands > View Unentitled Machines.
3 Remove the machine assignments for unentitled users.
4 Select More Commands > View Unentitled Machines or More Commands > View Unentitled Policies
as appropriate.
5 Change or remove the policies that are applied to unentitled users.
Resolving Database Inconsistencies with the ViewDbChk Command
With the ViewDbChk command, you can resolve inconsistencies in the databases that store information about
desktop virtual machines in an automated desktop pool and RDS hosts in an automated farm.
In a View environment, information about desktop virtual machines and RDS hosts in an automated farm is
stored in the following places:
n
The LDAP database
n
The vCenter Server database
n
For View Composer linked-clone machines only: the View Composer database
Normally, you can recover from an error that occurs during provisioning or other operations by removing
or resetting a desktop virtual machine or an RDS host using View Administrator. On rare occasions, the
information in the different databases about a machine that is in an error state might become inconsistent
and it is not possible to recover from the error using View Administrator. You might see one of the
following symptoms:
n
Provisioning fails with the error message Virtual machine with Input Specification already exists.
n
Recomposing a desktop pool fails with the error message Desktop Composer Fault: Virtual Machine
with Input Specification already exists.
Setting Up Desktop and Application Pools in View
344 VMware, Inc.