VMware ESXi and vSphere Cluster Management

Install and Connect the VMware vSphere Client on Windows

Learn how to install the legacy Windows VMware vSphere Client from vCenter media or a welcome page, connect to ESXi or vCenter Server, validate certificates, and troubleshoot login issues.

The vSphere Client is a graphical Windows application for administering VMware infrastructure. In supported legacy vSphere environments, it can connect directly to an ESXi host or to vCenter Server.

An ESXi host is VMware's bare-metal hypervisor that runs virtual machines. vCenter Server is the centralized management platform used to manage multiple ESXi hosts and shared virtual infrastructure. The Windows-based vSphere Client is a legacy interface; newer VMware environments commonly use browser-based management interfaces instead. Always use a client version compatible with the ESXi or vCenter Server version you administer.

What You Can Manage

Connection Target	Management Scope	Typical Credentials	Inventory Visibility	Considerations
Single ESXi host	One host and the virtual machines, networks, and datastores directly managed by that host	An authorized local ESXi account, often the root account for initial administration	The connected host and its managed objects	There is no centralized multi-host inventory or vCenter coordination
vCenter Server	Centrally managed hosts, clusters, virtual machines, datastores, networks, and resources	An account recognized by vCenter Server with suitable privileges	The inventory assigned to that vCenter Server and permitted to the account	Available features depend on the vSphere edition, licenses, permissions, and connected inventory

Installation Requirements

A supported Windows workstation with permission to install software. Local administrative privileges may be required.
Network reachability from the workstation to the target ESXi host or vCenter Server.
A valid administrative account. For a direct ESXi login, this may be the authorized local root account. Use a named account where possible and protect all administrative credentials.
Internet access if the installer must obtain prerequisites or components online. A package that contains all required components may avoid this dependency.
A vSphere Client release compatible with the deployed ESXi or vCenter Server version.

Before installing, identify the management address you intend to use. You can enter an IP address or a resolvable host name, such as a fully qualified DNS name. When using a host name, confirm that Windows resolves it to the expected management address.

Ways to Obtain the Installer

Method	Starting Point	Key Steps	Requirements	When to Use
vCenter Server installation media	Mounted or opened vCenter Server installation source	Run `autorun.exe`, select the VMware vSphere Client component, and follow the setup wizard	Access to trusted installation media and Windows installation permissions	When the matching client is included with the vCenter distribution
ESXi or vCenter Server welcome-page download	The target server address opened in a web browser	Open the welcome page, choose the vSphere Client download, save the package, and run it	Network access, browser download permission, and a compatible offered client	When the server provides the legacy client download

Download availability and the offered version depend on the deployed VMware product version. A newer ESXi or vCenter Server may not provide the legacy Windows client, or may require a different management interface.

Install from vCenter Server Installation Media

Mount the vCenter Server installation media or open the trusted installer source on the Windows workstation.
Run the main installer launcher, commonly named autorun.exe. Approve a Windows security prompt if appropriate.
From the component-selection menu, choose VMware vSphere Client.
Start the installation wizard.
Choose the installation language.
Read and accept the license agreement.
Confirm or change the destination folder. Use a location permitted by your organization's software policy.
Begin the installation and wait for the wizard to report completion.
Confirm that a vSphere Client shortcut appears on the desktop or in the Windows Start menu.

Practical example: Mount the vCenter installer source, run autorun.exe, select the vSphere Client option, accept the license, retain or select the destination folder, and finish the wizard. Launch the client from its new shortcut.

Install from an ESXi or vCenter Welcome Page

Open a web browser on the Windows workstation.
Browse to the IP address or host name of the ESXi host or vCenter Server. Use the management address, not an unrelated guest or storage address.
On the welcome page, locate the download option for the VMware vSphere Client.
Save the installer package to a trusted local folder.
Run the downloaded installer with appropriate Windows permissions. Verify the source and package before execution.
Follow the wizard: select a language, accept the license, confirm the destination folder, and complete installation.
Open the client from the desktop or Start menu shortcut.

If the download does not begin, check browser download restrictions, proxy settings, firewall rules, and connectivity to the server. The package may also be unavailable because the deployed VMware version does not offer the legacy client. In that case, use the compatible installer source for that product version.

Connect Directly to an ESXi Host

Launch the installed vSphere Client.
Enter the ESXi host's IP address or fully qualified host name in the server field.
Enter the authorized credentials configured on that ESXi host.
Use the root account only when appropriate. Handle its password securely and avoid sharing it.
Submit the login details.
Review any certificate or evaluation notices as described below.
Verify that the intended host appears in the Inventory pane, the navigation area that displays connected VMware objects.

DNS example: If the host name is esxi01.example.local, enter that complete name rather than an approximate short name. Confirm from Windows that the name resolves to the expected ESXi management address. Also confirm that the certificate identity corresponds to the name used for the connection.

Connect to vCenter Server

Launch the vSphere Client.
Enter the vCenter Server IP address or resolvable fully qualified host name.
Provide an account recognized by vCenter Server and assigned the privileges needed for the intended tasks.
Complete the login process and review any certificate or licensing notices.
Confirm that the expected vCenter inventory, including permitted hosts, clusters, and virtual machines, appears in the Inventory pane.

The displayed hierarchy and available actions depend on whether the connection is direct to ESXi or goes through vCenter Server. Permissions can also hide objects or prevent operations even when the server connection succeeds.

Certificate and Security-Warning Handling

During the first connection, an ESXi host may present a TLS certificate. TLS certificates encrypt the management connection and help verify the identity of the endpoint. A default self-signed certificate is signed by the system itself rather than by a public or enterprise certificate authority, so the client may report that it is not trusted.

Do not accept the warning automatically.
Verify the server identity, certificate details, and fingerprint through a trusted channel, such as an approved management record or a separate administrative console.
Check that the certificate name matches the IP address or host name you selected, where applicable.
Accept or install the certificate only after the endpoint and fingerprint have been validated.
Trusting the certificate can prevent repeated warnings, but it does not make an unverified endpoint safe.

Post-Login Validation

Confirm that the server name or address is the intended ESXi host or vCenter Server.
Check the host status and inspect basic managed objects such as virtual machines, networks, and datastores.
Compare the visible inventory with the expected direct-host or vCenter hierarchy.
Confirm that ordinary navigation and permitted management views load successfully.
Acknowledge an evaluation or licensing notice if one appears at login, then verify the license state before performing production administration.

A successful login proves authentication, but it does not prove that every management function is available. Licensing, permissions, product version, and connection target determine the features shown.

Common Login and Installation Issues

Symptom	Likely Cause	Validation Step	Resolution
Cannot download installer	Incorrect or unreachable address; firewall, proxy, or browser policy; the VMware version does not provide the legacy client	Confirm network access and inspect browser or proxy behavior	Use the correct management address, adjust approved access controls, or obtain the compatible installer from trusted media
Installer does not launch	Insufficient Windows rights, incomplete package, or blocked prerequisite download	Check Windows permissions, package integrity, and Internet or prerequisite access	Run with appropriate local administrative privileges, obtain a valid package, or use media containing required components
Cannot connect to host	Wrong address, DNS failure, routing or firewall restriction, or unavailable management service	Resolve the name, verify management-network reachability, and check the target service	Correct the address or DNS, permit approved management traffic, and restore service availability
Certificate warning	Default self-signed certificate, name mismatch, replaced certificate, or unexpected endpoint	Compare certificate details and fingerprint with a trusted source	Use the intended name and trust the certificate only after verification
Authentication failure	Wrong credentials, locked or disabled account, insufficient privileges, or credentials for another target type	Verify account status, target address, and authorization	Use an authorized local ESXi account for direct host access or a permitted vCenter account for vCenter access
Host absent from expected inventory	Direct connection instead of vCenter, missing permissions, or wrong vCenter instance	Confirm the login address and review inventory permissions	Reconnect to the correct vCenter Server and correct role or inventory permissions

Recommended Next Steps

After establishing access, review communication between vCenter Server and ESXi to understand management connectivity. If a host must be centrally managed, see how to add an ESXi host to vCenter Server inventory. For controlled administration, continue with assigning permissions and review ESXi lockdown mode.

Exam-Relevant Notes

The vSphere Client is a Windows graphical management application in legacy vSphere environments.
A direct ESXi connection manages one host; a vCenter Server connection exposes centrally managed inventory subject to permissions and licensing.
A welcome page may be provided by an ESXi host or vCenter Server and may offer a compatible client download.
Self-signed certificates commonly cause first-login warnings. Verify the fingerprint before trusting the certificate.
The root account is a high-privilege local ESXi account and must be protected.
Seeing fewer objects after login may be expected when connected directly to ESXi rather than to vCenter Server.