5.2

What to do next
The action that you should take depends on the problem that View Administrator reports for a desktop.
n
If
the View Desktops plug-in was added to the vSphere Web Client, you can use the vSphere Web Client
to search for a View user, display the desktops that are associated with that user, and troubleshoot the
underlying virtual machines in vCenter Server. See “Troubleshoot a Problem Desktop Virtual Machine
Using the vSphere Web Client,” on page 382.
n
If a linked-clone desktop is in an error state, the View Manager automatic recovery mechanism attempts
to power on, or shut down and restart, the linked clone. If repeated recovery attempts fail, the linked clone
is deleted. In certain situations, a linked clone might be repeatedly deleted and recreated. See
“Troubleshooting Desktops That Are Repeatedly Deleted and Recreated,” on page 398.
n
If a desktop is powered on, but does not respond, restart its virtual machine. If the desktop still does not
respond, verify that the version of the View Agent is supported for the desktop operating system. See
“Configuring Logging in View Agent Using the -A Option,” on page 411.
n
If a desktop remains in the provisioning state for a long time, delete its virtual machine, and clone it again.
Verify that there is sufficient disk space to provision the desktop. See “Virtual Machines Are Stuck in the
Provisioning State,” on page 394.
n
If a desktop reports that it is ready, but does not accept connections, check the firewall configuration to
make sure that the display protocol (RDP or PCoIP) is not blocked. See “Connection Problems Between
Desktops and View Connection Server Instances,” on page 390.
n
If a desktop appears to be missing from a vCenter Server, verify whether its virtual machine is configured
on the expected vCenter Server, or if it has been moved to another vCenter Server.
n
If a desktop has an active login, but this is not on the console, the session must be remote. If you cannot
contact the logged-in users, you might need to restart the virtual machine to forcibly log out the users.
Troubleshoot a Problem Desktop Virtual Machine Using the vSphere
Web Client
If a View desktop has a problem, you can use the View Desktops feature in the vSphere Web Client to search
for a View user, display the user's desktop, and troubleshoot problems with the underlying virtual machine
in vCenter Server.
For example, if a user calls in with a problem such as a desktop that is performing slowly, you can immediately
jump to the user's virtual machine on the Virtual Machines page in the vSphere Web Client and troubleshoot
the issue.
Prerequisites
n
Verify that the View Desktops plug-in was added to the vSphere Web Client. See "Adding the View
Desktops Plug-in to the vSphere Web Client" in the VMware Horizon View Installation document.
n
Verify that you can log in to the vSphere Web Client as a user with the View Administrators role or View
Administrators (Read only) role and with the vSphere Administrator privilege for the View desktop
virtual machines and vCenter Server folders that store the virtual machines.
If you search for desktops without having the vSphere Administrator privilege, the virtual machine names
are displayed as disabled links and you cannot access the virtual machine information.
Procedure
1 Log in to the vSphere Web Client as a user with the View Administrators role or View Administrators
(Read only) role and the appropriate vSphere Administrator privileges.
For example: https://
vSphere_Web_Client_IP_address_or_FQDN :9443/vsphere-client/
2 In the Search box, type the username of a View user.
VMware Horizon View Administration
382 VMware, Inc.