VMware ESXi and vSphere Cluster Management
vSphere Management GUIs: vSphere Client and vSphere Web Client
Learn how the historical Windows vSphere Client and Adobe Flex vSphere Web Client connect to ESXi and vCenter Server, and when to use each interface.
VMware vSphere environments can be administered through graphical tools as well as through an ESXi host's local console. Graphical user interfaces (GUIs) help administrators configure, monitor, and manage virtual infrastructure such as hosts, virtual machines, networks, storage, and inventory objects.
This lesson focuses on the historical Windows-installed vSphere Client and the historical Adobe Flex-based vSphere Web Client. These names are important because newer vSphere releases use an HTML5-based vSphere Client with different implementation details and supported access methods.
Prerequisites and key terms
- ESXi host: The VMware hypervisor server that runs virtual machines. It can be managed directly or through vCenter Server.
- vCenter Server: The centralized management platform for multiple ESXi hosts and their virtual infrastructure resources.
- Direct host connection: Logging in to an ESXi host itself rather than logging in to vCenter Server.
- Centralized management: Managing hosts, virtual machines, and related resources through vCenter Server.
- Direct Console User Interface (DCUI): The local console interface on an ESXi host. It is commonly used for basic host setup, network configuration, and recovery tasks, rather than for complete virtual infrastructure administration.
Why use a vSphere GUI?
An ESXi host can be configured locally through the DCUI, but the DCUI is intentionally limited. It is useful when setting up or recovering a host, especially when remote network access is unavailable. It is not the main interface for organizing a virtual datacenter or performing broad inventory administration.
A vSphere GUI provides a visual way to perform tasks such as:
- Creating, powering on, configuring, and monitoring virtual machines.
- Viewing hosts, clusters, datastores, networks, and other inventory objects.
- Configuring virtual hardware, storage, networking, and host settings.
- Monitoring resource use, alarms, tasks, and events.
- Managing several ESXi hosts through a central inventory when vCenter Server is used.
The connection endpoint matters. A client may connect directly to one ESXi host, or it may connect to vCenter Server and work with the hosts that vCenter Server manages.
Historical vSphere Client overview
The traditional vSphere Client was an installed desktop application for Windows. In earlier vSphere releases, it was the primary graphical administration tool. An administrator installed the application on a Windows workstation and then entered the management address of either an ESXi host or a vCenter Server instance.
When connected to an ESXi host, the client provided direct administration of that standalone host and its virtual machines. When connected to vCenter Server, it provided access to the centralized inventory and the hosts registered with that vCenter Server.
Its broad historical capabilities included:
- Host configuration and monitoring.
- Virtual machine creation, configuration, power operations, and console access.
- Inventory navigation for datacenters, clusters, hosts, and virtual machines.
- Virtual networking, including virtual switches, port groups, and network adapters.
- Storage configuration, datastores, and storage adapters.
- Advanced host and virtual machine configuration tasks.
- Viewing alarms, events, recent tasks, performance information, and permissions.
The important connection rule is that the historical installed vSphere Client could connect to either endpoint:
- Directly to an ESXi host: useful for a standalone host that is not registered with vCenter Server.
- To vCenter Server: useful for centralized administration of multiple hosts and their inventory.
Historical vSphere Web Client overview
The historical vSphere Web Client was a browser-based, platform-independent interface. Instead of installing the desktop client on each administrator workstation, an administrator opened a supported browser and connected to vCenter Server.
This generation of the Web Client was built on Adobe Flex, a browser application technology used by that historical interface. Adobe Flex describes the technology foundation of the legacy Web Client; it should not be used as a description of every modern browser-based vSphere interface.
Browser-based management was useful because:
- No Windows desktop client installation was required on each administrator workstation.
- Administrators could work from supported operating systems and browsers.
- A centrally accessed interface could expose the inventory managed by vCenter Server.
- Administrators could select hosts, virtual machines, networks, and storage objects from one centralized view.
The historical Web Client connected to vCenter Server only. It did not provide a direct login path to an individual ESXi host. An ESXi host had to be added to the vCenter Server inventory before the Web Client could be used to manage that host.
Connection architecture and access paths
There are two distinct management paths. The first is direct host administration. The second is centralized administration through vCenter Server.
- The administrator uses the installed Windows vSphere Client to connect directly to an ESXi host. The host is managed as an individual system.
- The administrator uses the installed vSphere Client to connect to vCenter Server. vCenter Server presents the inventory of registered hosts and resources.
- The administrator opens the historical vSphere Web Client in a supported browser and connects to vCenter Server. Hosts are managed through the vCenter Server inventory.
In the third path, the Web Client does not create a separate direct connection to the ESXi host. The host is accessed as an object managed by the connected vCenter Server.
| Administrator Tool | Connects To | Can Manage an ESXi Host Directly? | Prerequisite |
|---|---|---|---|
| vSphere Client | An ESXi host or vCenter Server | Yes | Install the historical Windows client and have network access and valid credentials for the selected endpoint. |
| vSphere Web Client | vCenter Server | No | Use a supported browser, connect to vCenter Server, and ensure the ESXi host has been added to its inventory. |
Historical vSphere GUI client comparison
| Characteristic | vSphere Client | vSphere Web Client |
|---|---|---|
| Delivery method | Installed desktop application | Browser-based application |
| Supported administrator platform | Windows workstation | Supported operating system and browser combination |
| Connection endpoint | ESXi host or vCenter Server | vCenter Server only |
| Direct ESXi host connection | Supported | Not supported |
| vCenter Server connection | Supported | Supported and required |
| Typical historical use case | Standalone host administration or administration through vCenter Server | Centralized inventory administration through vCenter Server |
| Technology and version context | Traditional Windows client used in earlier vSphere releases | Legacy Adobe Flex-based Web Client generation |
Choosing the appropriate interface
Choose the installed vSphere Client for direct host administration
Use the historical installed client when an ESXi host is standalone and is not registered with vCenter Server. The administrator connects to the host's management address from the Windows workstation. This is the valid historical GUI path for managing that host directly.
Choose the Web Client for vCenter-managed environments
Use the historical Web Client when the environment is administered through vCenter Server and browser access is preferred. After hosts are added to vCenter Server, the administrator can select an ESXi host or virtual machine from the centralized inventory.
Consider the task and the version
Feature availability can vary according to the vSphere release, the client generation, and whether the connection is direct to ESXi or through vCenter Server. A feature available through vCenter Server may not be available during a direct host connection, and a feature in one client generation may be arranged differently or absent in another.
| Situation | Valid historical choice | Reason |
|---|---|---|
| One ESXi host is not registered with vCenter Server | Installed Windows vSphere Client connected to the host | Direct host access is required. |
| Several hosts are managed centrally | vSphere Web Client connected to vCenter Server | The hosts must be selected from the centralized inventory. |
| Windows administrator needs direct host access | Installed vSphere Client | The historical client supports a direct ESXi connection. |
| Cross-platform administrator needs browser access to a vCenter-managed environment | vSphere Web Client | The browser client avoids installing the Windows desktop application, subject to browser support. |
Practical examples
Example: managing a standalone ESXi host
An administrator has one ESXi host that is not registered with vCenter Server. The administrator identifies the host's management address, opens the historical Windows vSphere Client, and connects directly to that address.
The legacy Web Client is not an alternative for this direct connection. It expects a vCenter Server endpoint, so the administrator must either use the installed client or first add the host to vCenter Server.
Example: managing hosts through vCenter Server
An organization has several ESXi hosts registered in a vCenter Server inventory. The administrator opens the historical Web Client in a supported browser and authenticates to vCenter Server. The administrator then selects a host or virtual machine from the centralized inventory.
The Web Client is connecting to vCenter Server. The selected ESXi host is being managed through that vCenter Server relationship, not through a direct Web Client-to-host connection.
Example: selecting a client based on access requirements
A Windows administrator needs to troubleshoot a standalone host. The installed vSphere Client is appropriate because it supports direct ESXi access. A different administrator needs browser-based access to a vCenter-managed environment from a supported non-Windows workstation. The historical Web Client is appropriate because it connects to vCenter Server through a browser.
Troubleshooting connection and access problems
The Web Client is opened directly against an ESXi host
Likely cause: The legacy Web Client uses vCenter Server as its connection point and does not provide direct ESXi host access.
Resolution: Connect with the historical installed vSphere Client for direct host management, or add the host to vCenter Server and then access it through the Web Client.
A host does not appear in the Web Client inventory
Possible causes: The host has not been added to the connected vCenter Server, the administrator connected to the wrong vCenter Server, or the account lacks the required inventory permissions.
Checks: Verify the vCenter Server address, confirm that the host is registered in the expected datacenter or cluster, and review the user's roles and permissions.
The old Windows client or Flex Web Client behaves differently than expected
Likely cause: Client features, supported access methods, and interface behavior differ between vSphere releases.
Resolution: Confirm the installed vSphere release and the exact client generation. Use documentation and compatibility information that match that release.
The legacy browser client cannot be launched
Possible cause: The browser or required legacy browser components are not supported or available in the environment.
Resolution: Check the supported browser matrix for the relevant vSphere release. Also distinguish the historical Adobe Flex Web Client from newer HTML5-based interfaces.
Version and terminology context
This lesson uses vSphere Client to mean the historical Windows-installed client and vSphere Web Client to mean the historical Adobe Flex-based browser interface. Those terms describe a particular generation of vSphere administration tools.
Newer vSphere releases use an HTML5-based vSphere Client. It is not automatically equivalent to the legacy Flex Web Client, even though both provide browser-based administration. Before following a procedure, verify the vSphere release, the installed interface, the supported browser or operating system, and whether the connection is to ESXi or vCenter Server.
Exam-relevant summary
- The historical installed vSphere Client was a Windows desktop application.
- The historical installed vSphere Client could connect directly to an ESXi host or to vCenter Server.
- The historical vSphere Web Client was browser-based and built on Adobe Flex.
- The legacy Web Client connected to vCenter Server only.
- An ESXi host had to be added to vCenter Server before it could be managed in the legacy Web Client.
- Direct host management and centralized vCenter Server management are different access paths.
- Always match procedures and feature expectations to the vSphere version and client generation.
For the terminology and access-path distinction, see vSphere management GUIs.