Vmware Esxi

vSphere Graphical Management Interfaces: vSphere Client and vSphere Web Client

Learn how the historical Windows vSphere Client and browser-based vSphere Web Client managed ESXi hosts, vCenter Server, and virtual infrastructure.

VMware vSphere provides graphical tools for administering hosts, virtual machines, and inventory. In the historical vSphere product generation covered here, the two important graphical interfaces were the Windows-based vSphere Client and the browser-based vSphere Web Client.

These tools were alternatives to the Direct Console User Interface (DCUI), which is the local, text-based console available at an ESXi host. The correct graphical interface depends mainly on whether you are managing one standalone ESXi host or managing hosts through vCenter Server.

Core terms

• ESXi host: The VMware hypervisor system that runs virtual machines. It can be managed directly or through vCenter Server.
• vCenter Server: The centralized vSphere management platform used to organize inventory and manage one or more ESXi hosts.
• DCUI: The local Direct Console User Interface at an ESXi host. It is text-based and is commonly used for basic host configuration and recovery tasks.
• Direct host connection: A client connects straight to one ESXi host rather than connecting to vCenter Server.
• Centralized management: Administration is performed through vCenter Server, which presents the inventory and coordinates management of its ESXi hosts.

Why use a graphical interface?

A graphical interface makes it easier to inspect inventory, configure hosts, manage virtual machines, and perform advanced administration tasks than working only from the local DCUI. The GUI also gives an administrator a broader view of virtual infrastructure, especially when several hosts are managed by vCenter Server.

The management model matters:

• With a standalone ESXi host, the administrator works with that individual host and the virtual machines running on it.
• With vCenter Server, the administrator works from a centralized inventory containing managed hosts, virtual machines, datastores, and other resources.

Centralized management does not mean that vCenter replaces the ESXi host. ESXi still runs the virtual machines, while vCenter provides the central management layer for the hosts it controls. For background, see adding an ESXi host to vCenter Server inventory and communication between vCenter Server and ESXi.

Legacy Windows vSphere Client

The historical vSphere Client was an installed desktop application that ran on Windows. It was historically the principal rich graphical administration tool for vSphere.

The client could connect to either of two endpoint types:

• An individual ESXi host through a direct host connection.
• A vCenter Server instance for centralized management.

When connected to a host, the client could be used for host administration and for managing virtual machines on that host. When connected to vCenter Server, it could work with the vCenter inventory and manage resources across multiple hosts, subject to the permissions and features available in that environment.

Typical capabilities

• Reviewing and configuring ESXi host settings.
• Creating, powering on, powering off, and configuring virtual machines.
• Viewing and organizing inventory.
• Managing host and virtual machine resources.
• Performing advanced configuration tasks exposed by the particular vSphere release.

The available features were not necessarily identical for every connection. A direct connection to an ESXi host exposed host-level administration for that host. A connection to vCenter Server exposed centralized inventory and management features. The vSphere version, user permissions, licensing, and connection target could all affect what the administrator could see and do.

Legacy vSphere Web Client

The historical vSphere Web Client was a browser-delivered, platform-independent management interface. Unlike the installed Windows client, it did not require the administrator to install the desktop application on the workstation.

In the historical product context, the Web Client used an Adobe Flex-based architecture. Adobe Flex was the technology foundation for the browser interface in that generation.

The Web Client connected to vCenter Server, not directly to an ESXi host. After signing in to vCenter Server, an administrator could use the vCenter inventory to manage the ESXi hosts controlled by that server. This made the Web Client the intended successor to the older Windows vSphere Client in the referenced vSphere generation.

Indirect management path

When an administrator manages an ESXi host through the historical Web Client, the path is indirect:

1. The administrator opens a supported browser.
2. The browser connects to the vSphere Web Client service associated with vCenter Server.
3. The administrator signs in and selects objects in the vCenter inventory.
4. vCenter Server coordinates management operations with the selected ESXi host.

A browser running the historical Web Client could not connect straight to an ESXi host by entering that host's address. Direct ESXi-to-Web-Client access was not supported in this interface model.

Connection paths and management scope

Management Connection Paths

Choosing the appropriate interface

Choose the Windows vSphere Client when

• You need direct access to an individual ESXi host.
• No vCenter Server is available, such as in a standalone-host environment.
• The administrative workstation runs Windows and can install the client.
• You need host-level or virtual machine administration through a direct connection.

Choose the vSphere Web Client when

• The environment is managed by vCenter Server.
• You want centralized administration of multiple hosts and inventory objects.
• The administrator is using a non-Windows workstation or wants to avoid installing the Windows desktop client.
• The client and vSphere release support the historical Web Client architecture.

If direct access to an isolated ESXi host is necessary, use the historical Windows vSphere Client. Do not attempt to use the historical Web Client as a direct-to-ESXi tool.

Practical examples

Configure a standalone ESXi host

An administrator has no vCenter Server and needs to review host settings and manage virtual machines. The administrator installs the Windows vSphere Client and connects it directly to the ESXi host. This is a direct host connection.

Manage hosts in a centralized environment

An administrator opens a supported browser, signs in to vCenter Server through the vSphere Web Client, selects an ESXi host from the vCenter inventory, and performs management tasks. The browser is connected to vCenter Server; it is not connected directly to the host.

Use a non-Windows workstation

An administrator is working from a non-Windows workstation in an environment with vCenter Server. The Windows-only desktop client cannot be installed there, so the administrator uses the browser-based Web Client through vCenter Server, assuming that the environment supports that historical client.

Avoid an unsupported connection

An administrator needs direct access to an isolated ESXi host and tries to enter the host address in the historical Web Client. That connection fails because the Web Client requires vCenter Server. The administrator should instead use the Windows vSphere Client for direct host access, or connect to the vCenter Server that manages the host.

Troubleshooting interface selection

The Web Client cannot connect to an ESXi host address

Likely cause: The historical Web Client is designed to connect to vCenter Server, not directly to ESXi.

Resolution: Connect the Web Client to the vCenter Server managing the host. If direct host access is required, use the historical Windows vSphere Client.

The Windows vSphere Client cannot be used from a non-Windows workstation

Likely cause: The desktop vSphere Client is Windows-only.

Resolution: Use the browser-based Web Client through vCenter Server when the environment and client generation support it. Otherwise, use a supported Windows administration workstation.

A host is visible in vCenter but unavailable through a direct-client workflow

Likely cause: Centralized vCenter access is being confused with direct ESXi connectivity.

Resolution: Decide whether the task requires a direct host connection or centralized management. For centralized access, work from the vCenter inventory. For direct access, verify the ESXi endpoint and use the Windows vSphere Client.

Exam-relevant notes

• The historical vSphere Client was a Windows-installed desktop GUI.
• The historical vSphere Client could connect directly to ESXi or to vCenter Server.
• The historical vSphere Web Client was browser-based and platform-independent from the administrator's workstation perspective.
• The historical Web Client used Adobe Flex and connected to vCenter Server.
• The historical Web Client could manage ESXi hosts only indirectly through vCenter Server.
• A direct ESXi connection from the historical Web Client was not supported.
• Direct host administration and centralized vCenter administration are different management paths.

For related administration topics, review basic ESXi configuration, assigning permissions, and ESXi DCUI administration.