Administration

Prerequisites
Verify that the registered machines that you want to remove are not being used in any desktop pool.
Procedure
1 In View Administrator, select View Configuration > Registered Machines.
2 Click the Others tab.
3 Select one or more machines and click Remove.
You can select only machines that are not being used by a desktop pool.
4 Click OK to confirm.
Status of Unmanaged Machines
Unmanaged machines, which are physical computers or virtual machines that are not managed by vCenter
Server, can be in various states of operation and availability. In View Administrator, you can track the status
of unmanaged machines in the right-hand column of the Machines page under the Others tab.
Table 8-7 shows the operational state of unmanaged machines that are displayed in View Administrator. A
machine can be in only one state at a time.
Table 8‑7. Status of Unmanaged Machines
Status Description
Startup View Agent has started on the machine, but other required services such as the display
protocol are still starting. The View Agent startup period allows other processes such
as protocol services to start up as well.
Validating This state occurs after View Connection Server first becomes aware of the machine,
typically after View Connection Server is started or restarted, and before the first
successful communication with View Agent on the machine. Typically, this state is
transient. It is not the same as the Agent unreachable state, which indicates a
communication problem.
Agent disabled This state can occur if View Connection Server disables View Agent. This state ensures
that a new desktop session cannot be started on the machine.
Agent unreachable View Connection Server cannot establish communication with View Agent on the
machine. The machine might be powered off.
Invalid IP The subnet mask registry setting is configured on the machine, and no active network
adapters have an IP address within the configured range.
Agent needs reboot A View component was upgraded, and the machine must be restarted to allow View
Agent to operate with the upgraded component.
Protocol failure A display protocol did not start before the View 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 machine encountered a problem reaching the domain. The domain server was not
accessible, or the domain authentication failed.
Configuration error The display protocol such as RDP or another protocol is not enabled.
Unassigned user connected A user other than the assigned user is logged in to a machine in a dedicated-
assignment pool.
For example, this state can occur if an administrator logs in to the unmanaged machine
without using Horizon Client.
Unassigned user disconnected A user other than the assigned user is logged in and disconnected from a machine in a
dedicated-assignment pool.
Chapter 8 Managing Desktop Pools, Machines, and Sessions
VMware, Inc. 153