VMware ESXi and vSphere Cluster Management

Install and Connect to the VMware vSphere Client for ESXi and vCenter Server

Learn how to install the legacy Windows VMware vSphere Client, connect to ESXi or vCenter Server, validate certificates, and troubleshoot common connection problems.

The legacy VMware vSphere Client is a Windows desktop application for administering compatible VMware environments. It can connect directly to one ESXi host or connect to vCenter Server, which provides centralized management for multiple hosts and virtual machines.

This lesson covers obtaining the client, installing it from a browser download or vCenter Server media, logging in, handling the first certificate prompt, and confirming the initial inventory.

Understand the vSphere Client and Its Scope

An ESXi host is a bare-metal hypervisor that runs virtual machines. A direct host connection means that the client communicates with one ESXi host without using vCenter Server.

vCenter Server is the centralized management platform for ESXi hosts, inventories, permissions, and features that operate across hosts. When you connect to vCenter Server, the client displays the objects managed by that vCenter instance according to your permissions.

Connection target: Standalone ESXi host

Inventory scope: One host and the virtual machines, storage, and networking objects available on it.

Typical credentials: The local ESXi root account for initial access, or an authorized local account.

Use case: Initial setup, recovery, or administration of a host that is not managed by vCenter Server.

Administrative consideration: Direct access does not provide centralized inventory or multi-host management.

Connection target: vCenter Server

Inventory scope: The centrally managed datacenters, clusters, hosts, virtual machines, storage, and networks visible to the account.

Typical credentials: An account authorized in vCenter Server.

Use case: Centralized administration of multiple ESXi hosts and vSphere objects.

Administrative consideration: Permissions are controlled through vCenter roles and inventory assignments.

The legacy desktop client is different from newer browser-based VMware management interfaces. Some newer vSphere versions are managed primarily through a web browser and do not provide a compatible legacy desktop client. Check the target product version and its supported management tools before installing software.

Prerequisites Before Installation

A supported Windows workstation.
Local permission to install applications and, when required, permission to run installers with administrative rights.
Network connectivity from the workstation to the ESXi management interface or vCenter Server.
The IP address, DNS host name, or fully qualified domain name of the intended connection target.
Valid credentials. A newly installed standalone ESXi host commonly uses its root account for initial administration. A vCenter connection requires an authorized vCenter account.
Access to vCenter Server installation media or to the target system's welcome and download page.
Internet access if the installer must download prerequisites or other components.

Record the following values before starting:

ESXi host address:       <esxi-host-name-or-ip>
vCenter Server address:  <vcenter-host-name-or-ip>
Username:                <authorized-account>
Password:                <password>

Use only the address that matches your intended management target. Connecting to an ESXi host and connecting to vCenter Server are separate workflows with different inventory scopes.

Choose an Installation Method

Browser-based download from an ESXi host or vCenter Server welcome page

Source location: The management address of the target VMware system.

High-level workflow: Open the address in a browser, locate the vSphere Client download option, download the installer, and run it on Windows.

When to use it: When the target version exposes a compatible client download on its welcome page.

Considerations: The option may not exist on newer systems. Browser prompts, Windows security controls, network access, and downloaded prerequisites can affect setup.

Installation from vCenter Server installation media

Source location: Mounted or extracted vCenter Server installation media.

High-level workflow: Start the media menu, select the VMware vSphere Client component, and complete the installation wizard.

When to use it: When the matching client is supplied with the vCenter Server media or when the target welcome page does not provide a download.

Considerations: The media and client must match the supported product versions. Do not use an obsolete client merely because it is available on old media.

Method 1: Download the Client Through a Web Browser

Open a browser on the Windows workstation.
Navigate to the management address of the ESXi host or vCenter Server. Use the system's IP address or DNS name as appropriate.
On the welcome page, locate the option for downloading the compatible vSphere Client.
Start the download and save the installer to a known local folder.
Run the downloaded installer.
Respond to the browser download prompt and any Windows security prompt only after confirming that the installer came from your trusted VMware system or approved installation source.
Complete the installation wizard and wait for setup to report success.

Available download options depend on the VMware version and configuration. If the page offers only a browser-based management interface, do not assume that the legacy desktop client is supported for that system.

Some installers retrieve prerequisites from the internet. If setup pauses while obtaining a component, verify internet access and the workstation's proxy or endpoint-security policy.

Method 2: Install from vCenter Server Media

Locate the vCenter Server installation media, or mount the approved installation image on the Windows workstation.
Open the media folder.
Launch the installer entry point, typically autorun.exe.
In the vCenter installation interface, choose the VMware vSphere Client component.
Start the vSphere Client installation wizard.
Select the installation language.
Continue past the welcome screen.
Read and accept the license agreement.
Select or confirm the destination folder.
Start the installation and wait for the completion message.
Close the wizard after setup finishes successfully.

The precise wording and layout can vary between releases, but the core choices are language, license acceptance, destination folder, and installation confirmation.

Post-Installation Checks

Open the Windows Start menu or desktop and confirm that a vSphere Client shortcut or program entry is available.
Launch the application.
Confirm that the login window opens without an installation error.
Prepare the address and credentials for the intended ESXi host or vCenter Server.
After connecting, verify that the expected target appears in the Inventory view.

If the application launches but refuses the connection, client and server incompatibility is one possible cause. Check the supported version combination before repeatedly reinstalling the same client.

Log In Directly to an ESXi Host

Open the installed vSphere Client.
In the server field, enter the ESXi host's IP address or fully qualified host name.
Enter the appropriate username and password.
For a newly installed standalone host, use the local root account when initial administration requires it.
Complete the connection.
Open the Inventory view and verify that the ESXi host appears at the top of the inventory tree.

The root account has the highest local privilege on an ESXi host. Use it only when appropriate for initial setup or approved recovery work. Create and use less-privileged accounts for routine administration whenever the environment's access-control design permits it.

Connect Through vCenter Server

Open the vSphere Client.
Enter the vCenter Server DNS name or fully qualified host name rather than an individual ESXi host address.
Authenticate with an account authorized in vCenter Server.
Complete the connection.
Browse the centrally managed inventory. The objects shown depend on the account's assigned permissions.

A successful vCenter connection can expose multiple hosts and other managed objects. A user may be able to connect successfully but still be unable to see or administer particular objects because of vCenter permissions.

Handle the First Certificate Warning Safely

A certificate warning commonly appears when an ESXi host presents a self-signed certificate. A self-signed certificate is issued by the host itself rather than by a certificate authority already trusted by the workstation. A warning can also occur when the certificate name does not match the address used, or when a host certificate changed after a rebuild.

Review the host identity, certificate subject, validity information, and certificate fingerprint.
Verify those details through a trusted channel, such as approved host documentation or information displayed through a trusted administrative console.
Compare the fingerprint and expected host name with the system you intended to contact.
Only after validation, choose the option to trust or install the certificate.
Reconnect and confirm that future warnings are suppressed as expected.

When reliable DNS resolution and certificate naming are configured, prefer the DNS name that matches the certificate. Using an IP address when the certificate was issued to a host name can create an avoidable name-mismatch warning.

Review the Evaluation Notice and Inventory

An evaluation notice is a dialog indicating trial or evaluation licensing status. It may appear in an unlicensed or evaluation environment during or after login.

Read the evaluation or licensing notice.
Acknowledge it using the available confirmation option.
Open the Inventory view.
Verify that the connected ESXi host is visible at the top of the inventory tree.

Inventory is the hierarchical view of managed VMware objects. Seeing the expected host confirms that the connection succeeded and provides the starting point for host, virtual machine, storage, and networking administration.

Common Prompts and Safe Responses

Untrusted certificate warning

Likely meaning: The host uses a self-signed certificate, the name does not match, or the certificate changed.

Safe response: Validate the host identity and fingerprint before trusting or installing the certificate.

Verification step: Compare the certificate details with trusted host records or console information.

Evaluation notice

Likely meaning: The environment is using trial or evaluation licensing.

Safe response: Review and acknowledge the notice.

Verification step: Open Inventory and confirm that the expected host is present.

Authentication failure

Likely meaning: Credentials, authentication target, permissions, or account status are incorrect.

Safe response: Confirm whether you are logging in to ESXi or vCenter Server and use the correct account.

Verification step: Check the account's permissions and status through approved administrative procedures.

Unable to connect because of version mismatch

Likely meaning: The installed legacy client is not supported by the target server.

Safe response: Check the product compatibility requirements and install the supported client or use the browser-based interface.

Verification step: Record the client version and target ESXi or vCenter Server version and compare them with supported combinations.

Troubleshoot Installation and Connection Problems

The installer will not start

Confirm that the download or media source is trusted and complete.
Run the installer with appropriate local administrative rights.
Review Windows security and endpoint-protection alerts for a blocked executable.
Check whether required prerequisites are missing.
Use compatible installation media or download the supported client release.

The download link is unavailable

Confirm the VMware product version and whether it supports the legacy desktop client.
Check whether the target is configured for a browser-based management interface.
Test network, DNS, TLS, and browser access to the management address.
Use matching installation media where applicable.
Avoid using an unsupported legacy client against a newer platform.

The client cannot connect

Validate the host name or IP address.
Confirm network connectivity from the Windows workstation to the management interface.
Check firewall and port restrictions according to the environment's approved network design.
Confirm that the target management service is available.
Check client and server compatibility before reinstalling the client.

The certificate warning keeps appearing

Compare the certificate identity or fingerprint with trusted host documentation.
Use the host name that matches the certificate when possible.
Determine whether the certificate changed after a host rebuild or replacement.
Do not permanently trust a certificate that cannot be verified.

Login is rejected

Confirm whether the connection target is an ESXi host or vCenter Server.
Use the correct account format and password for that target.
Verify that the account has the required permissions.
Check whether the account is locked, disabled, or otherwise unavailable.

The host is missing from Inventory

Confirm the server address used at login.
Open the Inventory view rather than another application view.
Verify the user's assigned permissions and vCenter inventory scope.
If connected to vCenter Server, confirm that the host is actually managed by that vCenter instance.

Security and Operational Guidance

Use DNS names when name resolution is reliable and certificate naming is configured correctly.
Operate from a secured administrator workstation.
Do not expose ESXi management interfaces to untrusted networks.
Restrict direct root usage after initial setup and use least-privilege accounts for routine work.
Document the installed client version, target system version, and trusted certificate identity.
Remove or update obsolete client software when the VMware environment is upgraded or migrated to a browser-based management workflow.

Practical Installation Examples

Example: Install from an ESXi host download page

Open a browser to the ESXi management address.
Locate the vSphere Client download link on the welcome page.
Run the downloaded installer on Windows.
Launch the client and enter the host IP address.
Authenticate and open Inventory.

Expected result: The standalone ESXi host is visible in Inventory.

Example: Install from vCenter Server media

Open the mounted installation media.
Run autorun.exe.
Select the VMware vSphere Client option.
Choose the language.
Accept the license agreement.
Choose or confirm the installation path.
Complete the installation.

Expected result: The client is installed locally and available from the desktop or Start menu.

Example: First connection with a certificate prompt

Connect to an ESXi host by DNS name or IP address.
Review the certificate warning.
Validate the host identity and fingerprint using a trusted source.
Trust the certificate only after verification.

Expected result: The connection proceeds without repeatedly showing an unverified certificate warning.

Example: Connect through vCenter Server

Enter the vCenter Server name instead of an individual ESXi host address.
Authenticate with an account authorized in vCenter.
Browse the centrally managed inventory.

Expected result: Multiple managed objects are available according to the user's assigned permissions.

Key Exam and Operations Notes

The legacy vSphere Client is a Windows desktop application.
A direct ESXi connection manages one host; a vCenter Server connection provides centralized inventory and permissions.
Client and server version compatibility is required.
The root account is the highest-privilege local ESXi account and should not be the routine account when least-privilege alternatives are available.
A self-signed certificate can cause a first-connection warning.
Validate a certificate fingerprint before trusting the certificate.
Seeing the expected host in Inventory is a basic confirmation of successful login and target selection.
Newer VMware environments may require a browser-based management interface instead of the legacy desktop client.