VMware ESXi and vSphere Cluster Management

Add an ESXi Host to vCenter Server Inventory

Learn how to create a vCenter datacenter, add an ESXi host with the Add Host wizard, validate certificates, assign licensing, configure lockdown mode, and verify connectivity.

Why add an ESXi host to vCenter Server?

An ESXi host is a bare-metal VMware hypervisor that runs virtual machines. vCenter Server is the centralized vSphere management platform used to organize and administer ESXi hosts, virtual machines, clusters, storage, and networking.

A standalone ESXi host can run virtual machines independently, but it is not part of the vCenter Server inventory. Adding the host registers it with vCenter Server and establishes the management relationship needed for centralized operations such as virtual machine provisioning, power management, monitoring, permissions, and resource administration.

Host registration is also a prerequisite for grouping hosts into a cluster. A cluster is a logical group of ESXi hosts that can use services such as vSphere High Availability, which can restart affected virtual machines after a host failure, and Fault Tolerance, which maintains a secondary execution instance for supported virtual machines. Adding a host does not create a cluster or enable HA or Fault Tolerance by itself. Those capabilities require separate configuration, compatible licensing, and suitable infrastructure.

Understand the required inventory structure

The vCenter Server inventory is a hierarchy of objects. The relevant structure is generally:

• vCenter Server: the management system containing the inventory.
• Datacenter object: a logical site or administrative boundary that can contain hosts, clusters, virtual machines, networks, and datastores.
• Cluster: an optional group of hosts used for shared availability and resource-management services.
• ESXi host: the hypervisor server being registered.
• Virtual machines and resource pools: workloads and resource-management objects associated with a host or cluster.

A datacenter object must exist before you can add an ESXi host. The host may initially be placed directly under the datacenter. After onboarding and validation, it can be moved into an appropriate cluster.

Prerequisites and readiness checks

Complete these checks before opening the wizard. They prevent most failed registration attempts.

• Ensure the host is powered on, healthy, and connected to its management network.
• Confirm it is not already managed by another vCenter Server. If it is, follow the supported disconnect, removal, or migration process first.
• Review ESXi and vCenter Server version compatibility.
• Check certificates and resolve DNS inconsistencies before onboarding.
• Confirm that firewalls permit the management communication required by your vSphere version and design.

Open the vSphere management interface

Sign in to the vSphere Client with an account that can modify inventory. Depending on the vCenter Server version, the interface and URL differ. A commonly encountered legacy access pattern is:

https://<vcenter-server>/vsphere-client

Use the current client URL supplied by your vCenter Server deployment when this path is not applicable.

Create a datacenter object

1. Open the Hosts and Clusters inventory view.
2. Select the vCenter Server object or the appropriate inventory root.
3. Use the inventory creation action and choose New Datacenter or the equivalent datacenter creation command.
4. Enter a meaningful name based on your organization, site, environment, or administrative boundary, such as Production-East or Lab.
5. Complete the dialog and verify that the new datacenter appears in the inventory tree.

Select the new datacenter before starting host registration. This ensures that the host is added to the intended container rather than an incorrect site or folder.

Run the Add Host wizard

1. Start the workflow

In Hosts and Clusters, select the target datacenter, open its actions menu, and choose Add Host. The exact labels may vary slightly by vSphere version.

2. Identify the ESXi host

Enter the ESXi management FQDN or a valid management IP address. Prefer the FQDN when your organization has managed DNS and certificate standards.

esxi01.example.com

Do not assume that the vCenter Server login credentials will work here. The address identifies the ESXi host, while the credentials in this step authenticate against that host.

3. Enter ESXi credentials

Supply the local ESXi root account or another account with equivalent permissions. In a common setup, a vCenter administrator signs in to the vSphere Client, and the Add Host wizard separately requests credentials that exist on the ESXi host.

4. Validate the host identity

When vCenter Server contacts an ESXi host for the first time, it may display a certificate, authenticity, or thumbprint warning. This is expected: vCenter Server needs you to establish trust in the host identity.

Compare the presented certificate or thumbprint with information obtained from the ESXi console, a trusted management channel, or approved infrastructure records. Accept the prompt only when the host is confirmed to be the intended system.

Do not blindly accept an unexpected certificate. A mismatch can result from a rebuilt host, a regenerated certificate, incorrect DNS, an incorrect IP address, or a potential network interception issue.

5. Review the discovered host

The wizard may display discovered details such as the ESXi version, hardware information, and virtual machines. Review these details carefully. They should match the host you intended to register. Unexpected virtual machines, hardware, or version information is a reason to stop and investigate.

6. Choose license assignment

Select the appropriate licensing behavior available in your environment:

• Apply an available vSphere license from the vCenter Server license inventory.
• Assign a newly entered license key when the key has not yet been added to the inventory.
• Use evaluation licensing when it is available and appropriate for a lab or temporary evaluation.

Verify that the license edition supports planned features. An unlicensed or expired host may have restricted functionality, and features such as cluster services can require particular entitlements.

7. Decide on lockdown mode

Lockdown mode limits direct administrative access to an ESXi host and favors management through vCenter Server. It can reduce the host's direct attack surface, but it must fit the operational access design.

Enable lockdown mode during onboarding only when emergency access, delegated access, and break-glass procedures are already understood and tested. Otherwise, defer it until access policies are established. Direct ESXi access may be needed for recovery when vCenter Server or the management network is unavailable.

8. Confirm inventory placement

Select or confirm the target datacenter as the host's inventory location. If the workflow offers a cluster destination, use it only when the host is ready to join that cluster and compatibility requirements have been reviewed. Otherwise, place the host directly under the datacenter and move it later.

9. Review and finish

Review the final summary, including the host address, credentials context, certificate decision, license, lockdown setting, and inventory location. Correct any mistake before completing the wizard. Finish the workflow and wait for the host to appear in the inventory.

Wizard decision guide

Post-add validation

After the wizard completes, expand the inventory tree and confirm that the ESXi host appears beneath the intended datacenter. A successful onboarding check should include:

• The host status is Connected, not Disconnected or Not Responding.
• No critical alarms indicate a management, certificate, licensing, hardware, or connectivity problem.
• Host hardware and configuration details are visible.
• Networking objects, VMkernel interfaces, storage adapters, and datastores appear as expected.
• Existing virtual machines are visible and located under the expected host.
• The host has the intended license and no licensing warning remains.
• The host is in the correct datacenter and has not been placed in an unintended folder or cluster.

Adding the host is the beginning of administration, not the end. Typical follow-on tasks include configuring virtual networking and datastores, applying host profiles or configuration standards, moving the host into an appropriate cluster, and configuring vSphere High Availability, Fault Tolerance, vMotion, permissions, and lifecycle management as required.

Common onboarding failures

Example: initial single-host lab

1. Create a datacenter named Lab.
2. Start Add Host from that datacenter.
3. Enter the host management FQDN, such as esxi01.example.com.
4. Provide the local ESXi administrative credentials.
5. Compare the certificate identity with the expected host, then accept it only if it matches.
6. Apply an available evaluation or lab license.
7. Leave lockdown mode deferred if the lab still requires direct administrative access.
8. Finish the wizard and confirm that the host is connected below Lab.

Example: production host onboarding

1. Select or create the approved production datacenter.
2. Use the managed host FQDN rather than an unmanaged IP address when organizational standards require DNS.
3. Validate the certificate thumbprint through an approved out-of-band source.
4. Apply the organization's approved license edition.
5. Enable or defer lockdown mode according to the documented emergency-access procedure.
6. Complete post-add checks, then move the host into the intended cluster.

Exam-relevant notes

• A datacenter is required before an ESXi host can be added to vCenter Server.
• A host can initially be placed directly in a datacenter and later moved into a cluster.
• Adding a host does not automatically create a cluster or enable HA or Fault Tolerance.
• The Add Host wizard uses ESXi host credentials, which are distinct from vCenter Server login credentials.
• Certificate or thumbprint prompts must be validated rather than blindly accepted.
• Lockdown mode restricts direct host management and should be enabled only with a tested emergency-access plan.
• Feature availability depends on licensing, host compatibility, and additional cluster configuration.

For this workflow, see Add ESXi Host to vCenter Server Inventory.