Virtual machines that are managed by vCenter Server can be in various states of operation and availability. In Horizon Administrator, you can track the status of machines in the right-hand column of the Machines page.
Status of Virtual Machines That Are Managed by vCenter Server shows the operational state of virtual-machine desktops that are displayed in Horizon Administrator. A desktop can be in only one state at a time.
|Provisioning||The virtual machine is being provisioned.|
|Customizing||The virtual machine in an automated pool is being customized.|
|Deleting||The virtual machine is marked for deletion. Horizon 7 will delete the virtual machine soon.|
|Waiting for Agent||Horizon Connection Server is waiting to establish communication with View Agent or Horizon Agent on a virtual machine in a manual pool.|
|Maintenance mode||The virtual machine is in maintenance mode. Users cannot log in or use the virtual machine.|
|Startup||View Agent or Horizon Agent has started on the virtual machine, but other required services such as the display protocol are still starting. For example, View Agent cannot establish an RDP connection with client computers until RDP has finished starting. The agent startup period allows other processes such as protocol services to start up as well.|
|Agent disabled||This state can occur in two cases. First, in a desktop pool with the Delete or refresh machine on logoff or Delete machine after logoff setting enabled, a desktop session is logged out, but the virtual machine is not yet refreshed or deleted. Second, View Connection Server disables View Agent or Horizon Agent just before sending a request to power off the virtual machine.
This state ensures that a new desktop session cannot be started on the virtual machine.
|Agent unreachable||Horizon Connection Server cannot establish communication with View Agent or Horizon Agent on a virtual machine.|
|Invalid IP||The subnet mask registry setting is configured on the virtual machine, and no active network adapters have an IP address within the configured range.|
|Agent needs reboot||An Horizon 7 component was upgraded, and the virtual machine must be restarted to allow View Agent or Horizon Agent to operate with the upgraded component.|
|Protocol failure||A display protocol did not start before the View Agent or Horizon Agent startup period expired.
Note: View Administrator can display machines in a Protocol failure state when one protocol failed but other protocols started successfully. For example, the Protocol failure state might be displayed when HTML Access failed but PCoIP and RDP are working. In this case, the machines are available and Horizon Client devices can access them through PCoIP or RDP.
|Domain failure||The virtual machine encountered a problem reaching the domain. The domain server was not accessible, or the domain authentication failed.|
|Already used||In a desktop pool with the Delete or refresh machine on logoff or Delete machine after logoff setting enabled, there is no session on the virtual machine, but the session was not logged off.
This condition might occur if a virtual machine shuts down unexpectedly or the user resets the machine during a session. By default, when a virtual machine is in this state, Horizon 7 prevents any other Horizon Client devices from accessing the desktop.
|Configuration error||The display protocol such as RDP or PCoIP is not enabled.|
|Provisioning error||An error occurred during provisioning.|
|Error||An unknown error occurred in the virtual machine.|
|Unassigned user connected||A user other than the assigned user is logged in to a virtual machine in a dedicated pool.
For example, this state can occur if an administrator starts vSphere Client, opens a console on the virtual machine, and logs in.
|Unassigned user disconnected||A user other than the assigned user is logged in and disconnected from a virtual machine in a dedicated-assignment pool.|
|Unknown||The virtual machine is in an unknown state.|
|Provisioned||The virtual machine is powered off or suspended.|
|Available||The virtual machine is powered on and ready for a connection. In a dedicated pool, the virtual machine is assigned to a user and will start when the user logs in.|
|Connected||The virtual machine is in a session and has a remote connection to the Horizon Client device.|
|Disconnected||The virtual machine is in a session, but it is disconnected from the Horizon Client device.|
|In progress||The virtual machine is in a transitional state during a maintenance operation.|
While a machine is in a particular state, it can be subject to further conditions. Horizon Administrator displays these conditions as suffixes to the machine state. For example, Horizon Administrator might display the Customizing (missing) state.
Machine Status Conditions shows these additional conditions.
|Missing||The virtual machine is missing in vCenter Server.
Typically, the virtual machine was deleted in vCenter Server, but the Horizon LDAP configuration still has a record of the machine.
|Task halted||An instant clone task such as push image or a View Composer operation such as refresh, recompose, or rebalance was stopped.
For details about troubleshooting a recompose operation, see Correcting an Unsuccessful Recomposition.
For details about View Composer error states, see View Composer Provisioning Errors.
The Task halted condition applies to all virtual machines that were selected for the operation, but on which the operation has not yet started. Virtual machines in the pool that are not selected for the operation are not placed in the Task halted condition.
A machine state can be subject to both conditions, (missing, task halted), if a View Composer task was stopped and the virtual machine is missing in vCenter Server.