How do you turn a blank, expensive server into a machine that can run dozens of virtual computers at once? ESXi installation and configuration is the critical first step that transforms physical hardware into a virtualisation host. For VCP-DCV candidates, mastering this process is non-negotiable — it’s the foundation upon which every other VMware skill is built.
Jump to a section
A simple way to picture ESXi Installation and Configuration
Have you ever tried to build a custom shelf but realised you can’t just start hammering nails into bare studs without a solid base? Installing ESXi on a physical server is exactly like preparing a house for a major renovation.
Before you can hang cabinets or run new wiring, you need a clean, level, and well-supported foundation. Similarly, a brand-new server arrives as a blank canvas — no operating system, no applications, just raw hardware. ESXi is the specialised foundation that turns that raw metal into a usable home for virtual machines (your future furniture and appliances). You get to choose whether you install this foundation using a bootable USB (like a portable toolbox), a CD/DVD (an old-fashioned blueprint roll), or over the network via PXE boot (a builder arriving with a digital plan from the cloud).
Once the foundation is poured, you must properly configure the server’s internal setup — its IP address (the house number), hostname (the family name), DNS servers (the phone book to find other buildings), and storage connections (water and electricity lines). If you get these basics wrong, the whole renovation is doomed: virtual machines can’t find their data, neighbours (other servers) can’t communicate, and the house becomes isolated and useless. The process of installing and configuring ESXi is that critical, unskippable step of pouring a perfect concrete slab and hooking up utilities before anyone moves in.
Let’s start with the absolute basics. ESXi (Elastic Sky X Integrated) is a type-1 hypervisor. A hypervisor is a thin layer of software that sits directly on your server’s hardware and allows you to run multiple virtual machines (VMs) — each acting like its own independent computer — on that single physical machine. “Type-1” means it runs directly on the hardware, not on top of another operating system like Windows. This makes it extremely efficient and secure.
Before you can use ESXi, you must obtain it. VMware provides the ESXi installer as an ISO file (a digital image of a CD/DVD). You can download this from the VMware website with a valid account. The installer comes in different versions that match your server’s processor architecture — almost always 64-bit x86 for modern servers.
The installation process itself is surprisingly simple. You boot the server from the installation media (USB drive, CD/DVD, or over the network using PXE). The server then loads a minimal environment that walks you through a few steps:
- Selecting a disk or partition to install ESXi onto. The installer will warn you if the disk has existing data. - Choosing a keyboard layout. - Setting a root password. The root account is the all-powerful administrator account for the ESXi host. After a few minutes, the installer finishes and prompts you to remove the installation media and reboot. When the server comes back up, you see a Direct Console User Interface (DCUI) — a text-based screen with a yellow-and-grey menu. This is your primary way to configure network settings if you don’t have remote access. Now comes the critical configuration part. To manage your ESXi host remotely (which is how 99% of IT professionals do it), you need to assign it an IP address. You can do this through the DCUI by pressing F2, logging in as root, and navigating to the “Configure Management Network” section. Here you set:
- The IP address (the unique network identifier for your server, like 192.168.1.10) - The subnet mask (defines which part of the IP identifies the network vs. the specific device) - The default gateway (the router that connects your network to other networks) - DNS server addresses (servers that translate human-readable names like “vcenter.local” into IP addresses) You can alternatively assign these automatically via DHCP (Dynamic Host Configuration Protocol), where a network device hands out IP addresses. For production environments, static IPs are almost always used to ensure the server’s address never changes. Once networking is configured, you can connect to the ESXi host using the VMware Host Client — a web interface you reach by typing the host’s IP address into any browser on the same network. From this web interface, you can create datastores (storage containers for VM files), create virtual switches (software-based network switches for VMs), and eventually deploy VMs. Another key configuration is enabling or disabling services. For example, SSH (Secure Shell) allows command-line remote access, but VMware recommends keeping it disabled except during troubleshooting to reduce security risk. You also configure NTP (Network Time Protocol) so the host’s clock stays synchronised — important for logs and authentication. The installation also writes a bootloader to the disk that loads ESXi on startup. ESXi itself is installed on a boot device (often an SD card or USB drive for datacenter servers, freeing up disk bays for VM storage). The configuration files, including settings you make in the DCUI, are stored in a partition called /bootbank and /altbootbank, allowing for easy recovery if something corrupts. Why does all this matter? Without proper installation and configuration, your ESXi host might be unreachable on the network, unable to authenticate users, or vulnerable to attacks. For the VCP-DCV exam, you need to know not just the steps, but the reasoning behind each choice: why use static IPs? Why lock down SSH? Why install on separate boot media? These decisions define a well-architected datacenter versus a messy, insecure one.
Download the ESXi Installer ISO
Obtain the correct ESXi version from VMware’s website using a valid customer or evaluation account. The ISO is a single file containing the entire installer. Verify the downloaded file’s checksum to ensure it has not been corrupted.
Create Bootable Installation Media
Use a tool like Rufus or balenaEtcher to write the ISO to a USB flash drive (at least 4GB) or burn it to a CD/DVD. This media is used to boot the physical server and launch the installer. For PXE installations, you set up a network boot server instead.
Boot the Server from the Installation Media
Insert the media into the server, restart, and press the appropriate key (often F11, F12, or Del) to enter the boot menu. Select the USB or optical drive as the boot device. The server will load the ESXi installer from the media.
Run the ESXi Installer and Select Target Disk
The installer presents a welcome screen. Accept the EULA (F11), then choose the disk or partition where ESXi will be installed. Typically, you select a small, dedicated drive (e.g., an SD card or a low-capacity SSD) rather than large VM storage drives.
Set the Root Password and Complete Installation
The installer prompts you to set a strong root password (minimum 7 characters, including at least one uppercase, lowercase, digit, and special character). After confirmation, the installer copies files and writes the bootloader. Remove the media when prompted and reboot.
Configure the Management Network via DCUI
After reboot, the DCUI appears. Press F2 and log in as root. Navigate to ‘Configure Management Network’ and set a static IP address, subnet mask, default gateway, and DNS servers. Also select the correct physical network adapter for management traffic.
Access the Host Client Web Interface for Further Configuration
From a computer on the same network, open a web browser and go to the ESXi host’s IP address. Log in with the root credentials. From here, you can create datastores, configure virtual networking, enable services, and prepare the host for vCenter management.
Imagine you are a junior IT administrator at a mid-sized company that just purchased three new Dell PowerEdge servers to host their virtualised infrastructure. Your manager hands you the server specifications and says, “We need these ready for VMware production by Friday.” Here is exactly what an IT professional would do with ESXi installation and configuration.
First, you physically rack the servers (mount them in a server cabinet) and connect them to power and network cables. You then download the latest ESXi ISO from VMware’s website, matching the hardware compatibility list (HCL) to confirm the servers are supported. Using a tool like Rufus or balenaEtcher, you create a bootable USB drive with the ISO.
You insert the USB into the first server, boot it, and press a key to enter the boot menu (often F11 on Dell hardware). You select the USB drive as the boot device. The ESXi installer loads and presents a welcome screen. You press Enter to continue, accept the End User License Agreement (EULA) by pressing F11, and then select the target disk. In a modern datacenter, you might install ESXi onto a mirrored pair of SD cards or a small SSD, not the large-capacity drives intended for VMs. You confirm the installation and watch a progress bar fill. Once done, you remove the USB and reboot.
The server boots into the DCUI. You press F2, log in as root with the password you set during installation, and navigate to “Configure Management Network”. You select “Network Adapters” and ensure the correct physical NIC (network interface card) is selected — often the one labelled for management. You then choose “IPv4 Configuration” and enter the static IP address, subnet mask, and default gateway that your network team assigned. You also set the hostname, for example “esxi-prod-01.example.com”. Finally, you set DNS servers like “8.8.8.8” and “8.8.4.4”.
You then enable SSH to perform further configuration via command line, but you note this service should be disabled once done. You also configure NTP by entering a time server like “pool.ntp.org”. These DCUI settings are saved and the host is now ready for remote management.
You open a web browser on your laptop, type the host’s IP address, and the VMware Host Client login page appears. You log in with the root credentials. From here, you create a datastore using the server’s local storage — a large disk array formatted with VMFS (Virtual Machine File System), VMware’s high-performance file system for VMs. You also create a virtual switch to connect future VMs to the corporate network.
Your next step is to join the ESXi host to a VMware vCenter Server (a central management platform). This requires providing the vCenter IP and credentials. Once joined, the host is part of a cluster, allowing for advanced features like vMotion (live migration of running VMs) and High Availability (automatic restart of VMs if a host fails).
During this entire process, you document every configuration step: IP addresses, hostnames, storage layouts, and any deviations from the standard. This documentation is crucial for troubleshooting and for future administrators who will manage the infrastructure.
The VCP-DCV exam objective 1.2 specifically tests your ability to “Install and configure ESXi hosts.” VMware expects you to know the process, options, and best practices. Here is exactly what they test and how they try to trip you up.
First, expect multiple-choice questions that ask about installation media. They love to ask: “Which of the following is a supported boot method for installing ESXi?” The correct answers include USB, CD/DVD, and PXE boot. The trap is that some options sound plausible but are not supported, like installing from an external hard drive formatted as NTFS.
Second, they test configuration steps through scenario-based questions. For example: “An administrator has installed ESXi on a server but cannot connect to it from the management network. What is the most likely cause?” The correct answer usually relates to a mismatched subnet mask or an incorrect default gateway — not a firewall issue or a hardware failure. They want you to think about basic network configuration first.
Third, the exam heavily tests your knowledge of the DCUI and its functions. You need to know:
- How to configure management network (F2 → Configure Management Network) - How to restart management agents (F2 → Troubleshooting Options → Restart Management Agents) without rebooting the entire host - How to reset the system configuration (F2 → Rest System Configuration) — a last-resort option - That the DCUI is accessed locally, not remotely (before the IP is set) Fourth, expect questions about services like SSH and ESXi Shell. VMware’s official stance is that these should be disabled by default and only enabled temporarily for troubleshooting. The exam will test this with statements like: “Which service should be disabled to maintain a secure ESXi host?” The answer is SSH and ESXi Shell. They might include a distractor like “NTPService” which should actually remain enabled. Fifth, they test storage configuration during installation. Questions will ask about supported VMFS versions (VMFS-6 is the current standard), boot device considerations (use a separate device, not shared with VMs), and the concept of a scratch partition (a small partition for logs, which can be on a USB/SD boot device if a separate persistent location is configured). Finally, the exam loves to test the order of operations. For instance: “After installing ESXi, what is the correct next step?” The answer is to configure the management network so the host is accessible. A common trap is suggesting you first create a datastore — but you cannot manage the host remotely without a network, and the DCUI doesn’t allow datastore creation. Key traps to watch out for:
- Confusing ESXi installation with vCenter installation. They are separate products — ESXi is the hypervisor installed on a host; vCenter is a management server that manages multiple ESXi hosts. - Assuming all network adapters are management adapters. The DCUI allows you to select which NIC is used for management — the wrong selection makes the host unreachable. - Forgetting that the root password must meet complexity requirements (7+ characters, mix of types). - Thinking that the installation of ESXi automatically configures DNS — it does not; you must do it manually in the DCUI or via the Host Client. To memorise these points, create flashcards for each of the DCUI menu options, installation methods, and service default states. The exam rewards precise, detailed knowledge of these configuration elements.
ESXi is a type-1 hypervisor that installs directly on server hardware and cannot share the boot disk with another operating system.
Supported ESXi installation methods include bootable USB, CD/DVD, and PXE network boot, but not installation from within Windows.
The Direct Console User Interface (DCUI) is accessed by pressing F2 and is used for initial network configuration when the host is not yet reachable over the network.
During installation, only the selected target disk is erased; other disks in the server remain untouched until explicitly formatted.
After installation, the management network must be configured with a static IP address, subnet mask, gateway, and DNS settings before the host can be managed remotely.
SSH and ESXi Shell services are disabled by default for security and should only be enabled temporarily for troubleshooting.
The root password set during installation can be changed later via DCUI, Host Client, or command line.
These come up on the exam all the time. Here's how to tell them apart.
ESXi Hypervisor
Installed directly on a physical server as a type-1 hypervisor
Manages a single host and its local VMs
Requires manual configuration of each host separately via DCUI or Host Client
vCenter Server
Installed as a virtual machine or appliance on a cluster of ESXi hosts
Centrally manages multiple ESXi hosts, VMs, and advanced features
Provides a single pane of glass for cluster-wide management and automation
Static IP Address
Manually configured and never changes unless you change it
Required for production ESXi hosts to ensure consistent management access
Must be set in the DCUI under ‘IPv4 Configuration’
DHCP-Assigned IP Address
Automatically assigned by a DHCP server and can change over time
Suitable for evaluation or lab environments where address changes are acceptable
Can be used during initial installation but is typically replaced with a static IP
Local Storage (Internal Disks)
Disks physically inside the ESXi host; managed directly by the host
Data is not accessible to other ESXi hosts unless manually transferred
Used for scratch partition, logs, and optionally for VM storage in smaller deployments
Shared Storage (SAN/NFS/iSCSI)
Storage array accessible by multiple hosts over the network
Enables vMotion, HA, and other cluster features because VMs can be moved between hosts
Must be configured as a VMFS or NFS datastore before VMs can be placed on it
Mistake
ESXi is an operating system like Windows, so you can install it on a partition alongside Windows.
Correct
ESXi is a bare-metal hypervisor that must be the only operating system on the server. It takes over the entire disk and boots directly. It cannot co-exist with another OS like Windows or Linux in a dual-boot setup.
Beginners are used to the idea of installing multiple OSes on one machine (dual boot). ESXi does not support this because it needs exclusive access to hardware resources.
Mistake
After installing ESXi, you can immediately manage it from vCenter without any further configuration.
Correct
Before vCenter can manage an ESXi host, the host must have a properly configured IP address, subnet mask, and gateway so it is reachable on the network. You also need to add the host to vCenter using its IP address or FQDN.
Newcomers often assume vCenter auto-discovers hosts on the network, but vCenter requires explicit registration and network connectivity first.
Mistake
The ESXi installation wipes all data on all disks connected to the server.
Correct
The ESXi installer only erases the disk or partition you specifically choose for installation. Other disks, especially those intended for VM storage, remain untouched unless you deliberately format them later.
The installer’s warning about data destruction can be intimidating, leading users to believe all drives will be affected. In reality, you control the target disk.
Mistake
You cannot install ESXi on a laptop or desktop computer because the hardware is not compatible.
Correct
While VMware officially supports only servers on the Hardware Compatibility List (HCL), ESXi can be installed on many laptops and desktops for learning purposes. Common issues include unsupported network and storage controllers, but these can be overcome with community drivers or by disabling Secure Boot.
Beginners often think ESXi is locked to server hardware only, missing the fact that VMware provides a free version for personal lab use that works on many consumer machines.
Mistake
The root password set during installation cannot be changed afterwards.
Correct
The root password can be changed at any time using the DCUI, the Host Client (under Administration → Users), or through the command line via SSH if enabled.
Many new administrators incorrectly assume the installation-time password is permanent because the installer doesn’t show a change option at that point.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Yes, you can install ESXi on many laptops and desktops, but you may encounter hardware compatibility issues with unsupported network controllers or storage controllers. Using the VMware Fling community drivers or disabling Secure Boot can help.
ESXi is the hypervisor installed on a single server to run virtual machines. vCenter is a separate management server that allows you to manage multiple ESXi hosts centrally, enabling features like vMotion and High Availability.
No, you do not need an internet connection during the installation process. The ESXi ISO contains all necessary files. However, you will need network connectivity after installation to download patches or connect to vCenter.
The installer only formats the specific disk or partition you select for installation. Other drives remain untouched. The warning is to prevent accidental data loss if you choose a disk that already contains important data.
You can reset the root password by rebooting the ESXi host and entering the DCUI. From the main menu, press F2 and select ‘Troubleshooting Options’ > ‘Rest System Configuration’. This resets all configuration including the password, but also loses other settings.
The default username is ‘root’. During installation, you set a root password. There is no default password; you must create one during the installation process.
You've finished ESXi Installation and Configuration. Continue through the VCP-DCV study guide to build a complete picture of the exam.
Done with this chapter?