You can display a list of the desktops whose operation View Manager has detected as being suspect.

View Administrator displays desktops that exhibit the following problems:

Are powered on, but which are not responding.

Remain in the provisioning state for a long time.

Are ready, but which report that they are not accepting connections.

Appear to be missing from a vCenter Server.

Have active logins on the console, logins by users who are not entitled, or logins not made via a View Connection Server instance.

1

In View Administrator, select Desktops.

2

Under the VirtualCenter VMs tab, click Problem Desktops.

The action that you should take depends on the problem that View Administrator reports for a desktop.

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.

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.

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.

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.

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.

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.

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.