VMware ESXi and vSphere Cluster Management
VMware vSphere Components: ESXi, vCenter Server, Clients, and Management Tools
Learn how VMware vSphere, ESXi, vCenter Server, clients, lifecycle management, orchestration, clusters, and availability features work together.
VMware vSphere is an integrated virtualization platform and product suite. It is not one standalone application installed on a single server. The suite combines a hypervisor, centralized management, administration interfaces, lifecycle tools, and optional automation services.
A useful analogy is an office productivity suite. The suite is the complete platform, while individual applications perform specialized jobs. In vSphere, ESXi runs virtual machines, vCenter Server manages hosts and workloads centrally, and the vSphere Client provides the administrative interface.
vSphere abstracts physical compute, storage, and network resources. This means software-defined virtual machines can use resources supplied by physical servers without each VM needing its own dedicated server. Physical capacity is organized into virtual infrastructure that can be allocated, monitored, and managed according to workload requirements.
Core vSphere architecture
A basic vSphere environment contains physical servers, ESXi hosts, virtual machines, vCenter Server, and management clients. Optional lifecycle-management and orchestration services extend the management plane.
- Physical server: Provides processors, memory, storage interfaces, network adapters, firmware, and other hardware.
- ESXi: Runs directly on the physical server and provides the virtualization runtime.
- ESXi host: A physical server on which ESXi is installed.
- Virtual machine: A software-defined computer with virtual CPUs, memory, disks, network adapters, and a guest operating system.
- vCenter Server: Centrally manages multiple ESXi hosts, VMs, inventory objects, permissions, and clusters.
- vSphere Client: A browser-based interface used by administrators to access vCenter Server and, in some situations, an individual ESXi host.
- Optional services: Lifecycle management and workflow automation integrate with the vCenter management plane.
ESXi runs the virtual machines. vCenter Server manages ESXi hosts and their virtual machines, but it does not replace ESXi as the hypervisor. A virtual machine runs on an ESXi host, not directly on vCenter Server.
VMware ESXi
ESXi is VMware's bare-metal, Type 1 hypervisor. A hypervisor is software that creates and runs virtual machines by abstracting physical hardware. A Type 1 hypervisor runs directly on server hardware rather than on top of a conventional host operating system.
After ESXi is installed on a compatible physical server, it controls and coordinates access to the server's CPU, memory, storage devices, and networking hardware. It presents virtual hardware to each VM and allocates physical resources to VMs according to configuration and demand.
ESXi host, virtual machine, and vCenter Server compared
- An ESXi host is the physical server running the hypervisor.
- A virtual machine is a software-defined computer running on the ESXi host. Its guest operating system is installed inside the VM.
- vCenter Server is the centralized management system that coordinates hosts and workloads. It is not the place where the VMs execute.
ESXi is the foundational runtime component because no VM can run in a vSphere environment unless an ESXi host supplies the virtualization layer.
vCenter Server
vCenter Server is the centralized management plane for ESXi hosts and virtual machines. It provides a unified inventory and allows administrators to manage multiple hosts from one logical location.
Common vCenter Server responsibilities include:
- Maintaining inventory of datacenters, folders, clusters, hosts, datastores, networks, and VMs.
- Creating and configuring virtual machines.
- Managing templates and deployment workflows.
- Monitoring tasks, events, alarms, performance, and host health.
- Applying permissions and role-based access control.
- Organizing hosts into clusters and resource pools.
- Coordinating features such as High Availability, DRS, and live migration when prerequisites are satisfied.
- Integrating lifecycle management and automation tools.
An individual ESXi host can be administered directly, but vCenter Server is generally required for centralized inventory and cluster-level capabilities. vCenter manages hosts; it does not act as a substitute for the ESXi hypervisor.
vSphere management interfaces
The modern primary interface is the browser-based vSphere Client. Administrators use it to connect to vCenter Server and perform tasks such as viewing inventory, creating VMs, configuring hosts, monitoring tasks, reviewing alarms, and managing permissions.
Older training materials may use these names:
- vSphere Web Client: Historical name for an earlier browser-based interface.
- Legacy vSphere Client: A Windows-installed application used with earlier vSphere versions.
Modern administration commonly uses the browser-based vSphere Client. Client names and available screens are version-dependent, so navigation instructions should be checked against the installed vSphere release.
Component overview
| Component | Primary role | Where it runs or is accessed | Typical administrator tasks | Dependency or relationship |
|---|---|---|---|---|
| ESXi | Bare-metal hypervisor and VM runtime | Directly on a physical server | Run VMs, configure host hardware access, networking, and storage | Provides the runtime on which VMs execute |
| vCenter Server | Centralized management plane | As a vCenter Server appliance or supported deployment | Manage inventory, hosts, clusters, permissions, monitoring, templates, and policies | Manages multiple ESXi hosts but does not run their VMs |
| vSphere Client | Administrative interface | In a web browser | Create VMs, configure resources, monitor tasks, and manage permissions | Usually connects to vCenter Server; can also provide limited direct host access |
| vSphere Update Manager / vSphere Lifecycle Manager | Patch, update, compliance, and remediation management | Integrated with the vCenter management environment | Assess compliance, select updates, stage updates, remediate hosts, and verify results | Modern lifecycle management commonly uses vSphere Lifecycle Manager; Update Manager is the historical name |
| vCenter Orchestrator | Workflow automation and orchestration | As a service integrated with vCenter-based operations | Automate provisioning, configuration, approvals, notifications, and repeatable workflows | Historical terminology; newer VMware documentation may associate it with vRealize Orchestrator or VMware Aria Automation Orchestrator, depending on release and branding |
Lifecycle and patch management
Keeping ESXi hosts and related infrastructure up to date helps address security issues, defects, hardware compatibility requirements, and supported feature levels. Virtual machines also require their own guest operating-system and application patch processes; host lifecycle management does not replace guest patching.
vSphere Update Manager was the historical vCenter-integrated tool for host patching and remediation. In modern terminology, this function is commonly provided through vSphere Lifecycle Manager. Product names and capabilities vary by vSphere release and entitlement.
High-level remediation flow
- Assess host or cluster compliance against the selected baseline, image, or update policy.
- Review compatibility, dependencies, capacity, and any blocking conditions.
- Stage or select the approved updates.
- Evacuate, migrate, or shut down workloads as appropriate.
- Place the host into maintenance mode when required. Maintenance mode is a host state used before maintenance, typically after workloads have been moved or stopped.
- Remediate the host and reboot if required.
- Verify compliance, host health, connectivity, and workload availability after remediation.
Automation and orchestration
vCenter Orchestrator is the historical name for a workflow automation and orchestration capability associated with vCenter environments. In newer VMware terminology, readers may encounter vRealize Orchestrator or VMware Aria Automation Orchestrator, depending on the product release and branding. Always confirm the terminology used by the installed release and current product documentation.
Manual administration means an administrator performs each step interactively. Orchestration encodes a repeatable, multi-step process so it can run consistently with fewer manual actions, approvals, and omissions.
Example workflows include:
- Provisioning a VM from a template after an approval request.
- Assigning the correct datastore, network, naming convention, and resource policy.
- Applying post-deployment configuration and notifying the requester.
- Running routine operational tasks such as inventory checks or standardized changes.
Resource pooling and optimization
vSphere can organize compute, storage, and networking resources into a virtual infrastructure. A cluster is a logical group of ESXi hosts managed together. A resource pool is a logical partition used to organize and control allocation of cluster compute resources.
- CPU and memory: Hosts contribute capacity to a cluster from their own physical processors and memory.
- Storage: Datastores and shared storage provide locations for VM files and support access from appropriate hosts.
- Networking: Virtual switches, physical adapters, VLANs, and related constructs connect VMs and hosts to required networks.
Shared storage and consistent networking are important for mobility and availability features. When demand changes, cluster management can place or move eligible workloads toward hosts with suitable capacity, subject to policies and technical prerequisites.
Advanced vSphere capabilities
| Feature | Primary objective | Typical prerequisite category | Example outcome |
|---|---|---|---|
| High Availability (HA) | Restart affected VMs after a qualifying host failure | vCenter-managed cluster, surviving capacity, compatible configuration, and appropriate networking | VMs from a failed host restart on surviving hosts |
| Fault Tolerance (FT) | Provide enhanced availability for selected supported VMs | Supported VM and host configuration, capacity, networking, storage, and licensing | A protected workload can continue with reduced interruption during certain failures |
| Distributed Resource Scheduler (DRS) | Balance workloads according to available resources and policies | vCenter-managed cluster, compatible hosts, capacity, and configured policies | Eligible VMs are placed or moved to improve resource balance |
| Live migration | Move a running VM between hosts with little or no service interruption | Compatible source and destination hosts, suitable networking and storage, and satisfied migration requirements | A VM moves to another host while its service continues |
| Lifecycle remediation | Update hosts or clusters in a controlled, compliant manner | Lifecycle configuration, compatible updates, compliance assessment, and maintenance capacity | Hosts are remediated, rebooted when needed, and returned to service |
Availability is not the same as disaster recovery
HA helps respond to qualifying local host failures by restarting VMs. FT is designed for enhanced continuity for selected supported workloads. Live migration can reduce planned-maintenance interruption. These capabilities improve local availability, but none alone is a complete disaster-recovery plan.
Disaster recovery addresses larger events and recovery objectives, including acceptable data loss, recovery time, independent recovery infrastructure, backups or replication, application dependencies, communications, and regular testing.
Historical and current terminology
| Historical term | Current or common modern term | Teaching note |
|---|---|---|
| vSphere Web Client | vSphere Client | The browser-based vSphere Client is the common modern administration interface; older materials may use the former name. |
| Windows vSphere Client | Browser-based vSphere Client | The Windows-installed client is legacy terminology associated with earlier releases. |
| vSphere Update Manager | vSphere Lifecycle Manager | Lifecycle Manager represents the modern lifecycle-management terminology and capabilities, subject to release and licensing. |
| vCenter Orchestrator | vRealize Orchestrator or VMware Aria Automation Orchestrator | Product lineage and branding changed over time. Verify the name and supported features in the current release documentation. |
How the components work together
- Install ESXi on compatible physical server hardware.
- Configure host management networking, storage connectivity, and required virtual and physical networking constructs.
- Deploy or connect to vCenter Server.
- Add the ESXi hosts to the vCenter inventory.
- Create a datacenter object and, where appropriate, create a cluster.
- Configure datastores, networking, permissions, alarms, and resource policies.
- Create, import, or deploy virtual machines and install their guest operating systems.
- Use the vSphere Client to administer the environment through vCenter Server.
- Use vSphere Lifecycle Manager to assess and remediate infrastructure updates.
- Use orchestration workflows to automate repeatable provisioning and operational tasks.
- Configure monitoring, backup, lifecycle, and availability policies according to organizational requirements.
Direct ESXi management versus vCenter Server management
| Capability | Direct ESXi host management | vCenter Server-managed environment | Why the difference matters |
|---|---|---|---|
| Host and VM administration | Manage one host and its local inventory | Manage multiple hosts and VMs from a central inventory | Central administration is more consistent at scale |
| Centralized inventory | Not available across independent hosts | Available across datacenters, folders, clusters, hosts, and VMs | Administrators can search and organize the whole environment |
| Role-based access control | Configured per host | Managed centrally across vCenter inventory objects | Permissions are easier to standardize and audit |
| Clusters | Unavailable | Available | Clusters provide the foundation for coordinated host features |
| HA | Unavailable as a cluster service | Available when configured and licensed appropriately | VM restart after host failure requires coordinated hosts |
| DRS | Unavailable | Available when configured and licensed appropriately | Workload balancing requires cluster-level coordination |
| Lifecycle management | Limited host-level options | Centralized compliance and remediation capabilities | Updates can be planned and applied consistently |
| Automation | Limited individual-host operations | Workflow automation across vCenter inventory and services | Multi-step processes can be standardized |
vSphere editions and feature licensing
Available capabilities depend on the vSphere version, edition, license, and add-on entitlement. Historically common edition names include Standard, Enterprise, and Enterprise Plus, but historical names and feature matrices should not be assumed to apply to current releases.
Before purchasing or designing an environment, check the current VMware by Broadcom licensing information and product documentation. Confirm the entitlements required for features such as clusters, HA, DRS, FT, lifecycle management, automation, and migration.
Troubleshooting common misconceptions
“vSphere is installed on one server like ESXi.”
This confuses the platform with one component. ESXi is installed directly on physical hardware. vSphere is the broader suite that includes ESXi, vCenter Server, clients, and supporting services.
VMs cannot be centrally managed across several hosts
Check whether the hosts have been added to vCenter Server. Hosts managed independently do not provide one centralized multi-host inventory.
HA or automated balancing is unavailable
Review the dependency chain: compatible hosts, vCenter Server, cluster configuration, network and storage prerequisites, sufficient capacity, licensing, and correct feature settings.
A host cannot be remediated
Review compliance results, running workloads, incompatible updates, capacity, and maintenance-mode requirements. Migrate or shut down workloads as appropriate, place the host into maintenance mode when required, remediate it, and verify the result.
An administrator is searching for the Windows vSphere Client
This usually indicates legacy training material. Current administration commonly uses the browser-based vSphere Client; older client names may still appear in historical documentation.
Exam-relevant summary
- vSphere is an integrated virtualization platform and suite, not a single standalone application.
- ESXi is the bare-metal Type 1 hypervisor and the component that runs VMs.
- An ESXi host is a physical server running ESXi.
- vCenter Server centrally manages hosts, VMs, inventory, permissions, clusters, and policies.
- VMs run on ESXi hosts, not on vCenter Server.
- Clusters logically coordinate host resources, although CPU and memory remain physically located on individual hosts.
- HA restarts VMs after qualifying host failures; FT provides enhanced availability for selected supported workloads.
- DRS balances eligible workloads according to resource availability and policies.
- Live migration moves a running VM between compatible hosts with little or no interruption.
- vSphere Lifecycle Manager is the modern lifecycle-management term commonly associated with the historical Update Manager role.
- Historical vCenter Orchestrator terminology may appear as vRealize Orchestrator or VMware Aria Automation Orchestrator in newer product documentation.
- Feature availability depends on version, edition, licensing, add-ons, and configuration.