Install VMware ESXi on a Dedicated Server: Licensing and Setup

To install VMware ESXi on a dedicated server, confirm hardware support, choose a suitable license path, and boot the server from an approved installer ISO through its remote console. Install ESXi on the correct disk, configure management access, then prepare VM storage, guest networking, and backups before moving workloads onto the host.

The installer is one part of the job. A host can boot successfully and still lack a supported network driver, a working backup method, or the license features your team needs.

We cover a fresh ESXi 8 installation on one rented fysieke server. The guide also explains licensing limits, public IP options, common faults, and alternatives.

Version note: The documented free edition discussed here is ESXi 8.0 Update 3e. Choose the appropriate supported build for your hardware and entitlement. This guide does not claim that ESXi 8 is the newest VMware release or that a specific Atal Networks configuration has been tested with it.

ESXi Installation at a Glance

An ESXi dedicated server deployment follows seven main steps:

  1. Back up existing data and test remote console access.
  2. Download the correct ESXi installer.
  3. Mount the ISO and boot the server from it.
  4. Select the target disk and install ESXi.
  5. Remove the installer media and boot from local storage.
  6. Configure the management network in DCUI.
  7. Open the Host Client and check the host and license status.

After installation, configure guest networking, create a datastore, deploy a test VM, and prove that backups can restore usable data.

Data-loss warning: A fresh ESXi installation can overwrite the selected disk. Creating a datastore can also erase its target storage. Keep verified copies of required data outside the server before either action. Broadcom documents the installer’s disk formatting behavior in its ESXi 8 installation guidance.

What Is an ESXi Dedicated Server?

An ESXi dedicated server is a physical server that runs VMware’s hypervisor directly on its hardware. ESXi assigns CPU time, memory, storage, and network access to virtual machines. Each VM runs its own guest operating system, while the VMkernel manages the host’s physical resources.

For example, one server can host a Linux application VM, a Windows VM, and a separate testing environment. That is an example of workload separation, not a guarantee that those workloads cannot affect each other’s performance.

The VMs still share the server’s CPU capacity, disks, uplinks, and failure risks. If the only host stops, its running VMs stop too.

Onze bare metal versus virtualization guide explains the hardware and virtualization layers in more detail.

ESXi, vSphere, and vCenter: What Is the Difference?

These terms describe different parts of a VMware environment.

Bestanddeel Rol What it means for this setup
ESXi Hypervisor on the physical host Runs the virtual machines
vSphere VMware virtualization platform Provides the broader product and feature context
ESXi Host Client Web interface for an individual host Supports direct administration of the server
vCenter Server Central management platform Manages eligible hosts and supports features that depend on it

You can manage one ESXi host without vCenter. Features such as cluster management and workload migration depend on more than the basic ESXi installation, including the relevant licensing and infrastructure.

Renting the physical server does not, by itself, include VMware software rights or support.

Which ESXi License Do You Need on a Dedicated Server?

Choose the license path from the features, support, and permitted use your deployment requires. Check those requirements before buying hardware or selecting a backup product.

License path Wat te controleren? Belangrijkste beslissing
Free ESXi 8.0 U3e VM limits, management limits, terms, and maintenance options Can the deployment operate within the free edition’s restrictions?
Evaluation, where available Eligibility, expiry, and behavior after expiry Can testing finish before the evaluation ends?
Existing entitlement Version rights, capacity, support, and permitted hosted use Does the agreement cover the planned deployment?
Paid subscription Product edition, included features, core capacity, and support Does the quote cover the full operating plan?

Free ESXi 8: Features, Limits, and Support

Broadcom documents a free ESXi 8.0 U3e download. Its listed limits include two physical CPUs per host and eight vCPUs per VM. The free edition cannot join vCenter and excludes vMotion, HA, DRS, VADP-based backup, and official Broadcom support.

The free installer includes its license. Broadcom states that a separate free key does not need to be entered after installation.

We recommend checking three items before choosing it: whether the VM size limit fits, whether the backup method works without VADP, and whether the update path meets your security needs. Confirm the applicable terms for the intended use.

Paid Subscriptions, Existing Licenses, and Hosted Use

A license that activates successfully is not proof that every use of it is covered.

Before using an existing VMware entitlement on rented hardware, confirm:

  • The product version and features it covers.
  • The capacity available for the host.
  • Who owns and administers the entitlement.
  • Whether the agreement permits the intended deployment on third-party hardware.
  • Whether the workloads serve your organization or customers outside it.
  • Who can download updates and open a support case.

Internal IT workloads and a business that sells hosted VMs can have different licensing requirements. Get the applicable position from Broadcom or an authorized licensing partner for your agreement.

Also check guest software separately. A VMware license does not license Windows Server, databases, or other applications inside the VMs.

How to Count Licensed CPU Cores

For the VCF and VVF per-core rules documented by Broadcom, count physical cores across the hosts and apply a minimum of 16 cores to each installed CPU.

For each CPU:

Required core capacity = greater of 16 or that CPU’s physical core count

Host capacity = sum of required capacity for all installed CPUs

Example hardware Actual physical cores Capacity under this rule
One 12-core CPU 12 16 cores
Two 12-core CPUs 24 32 cores
One 24-core CPU 24 24 cores
Two 24-core CPUs 48 48 cores

These are calculations, not price quotes. Logical threads and the vCPUs assigned to guests are different counts. A seller’s minimum order can also differ from the capacity calculation.

This creates a useful purchasing check: a low-cost dual-socket server can require more license capacity than a single-socket server. Compare the full quote before choosing either.

ESXi 8 and ESX 9 Use Different Licensing Workflows

Do not apply ESXi 8 license instructions to a newer release without checking its documentation. Broadcom’s VCF/VVF 9 workflow uses subscription license files and VCF Operations instead of the traditional 25-character key process.

There is also a lifecycle decision. Broadcom lists October 11, 2027 as the end of general support for vSphere 8. A new ESXi 8 deployment should include a migration or upgrade plan within its expected operating life.

What Must You Check Before Installing ESXi 8?

Before installation, confirm the exact hardware, installer, storage layout, and network design. A product family name such as Dell PowerEdge or Intel Xeon does not prove that every component supports the chosen build.

Confirm Hardware, Drivers, and Firmware

Check the server and devices against the Broadcom Compatibility Guide and the hardware vendor’s supported combinations.

Item Record before installation Waarom het ertoe doet
Server Exact model and configuration Establishes the hardware support context
CPU Model, sockets, and physical cores Affects compatibility, capacity, and licensing
NIC Model, device identifiers, driver, and firmware Determines whether ESXi can use the required uplinks
Storage controller Model, mode, driver, and firmware Determines how installation and VM disks appear
Boot device Type, capacity, and health Holds the installed host system
Installer Release, build, and OEM image where required Must match the supported hardware design

An OEM image can include components needed by the server vendor. Dell’s ESXi guidance explains its customized ISO and firmware/driver checks.

If the only way to make a production server boot is to bypass a hardware support check, review the hardware choice before continuing.

Plan CPU, RAM, and Storage for the Workload

Size the host for the applications, not just the ability to launch the installer.

For RAM planning, use this starting structure:

Host RAM budget = guest RAM allocations

                + host and management overhead

                + operating headroom

For example, four VMs assigned 8 GB each account for 32 GB of guest RAM. That is not a complete host RAM recommendation. Host services, management tools, backup activity, and growth need their own allowance.

For a fresh ESXi 8 installation, Broadcom documents a boot disk of at least 32 GB of persistent storage, such as HDD, SSD, or NVMe. We recommend choosing a supported SSD boot design with enough space for the intended system layout and maintenance needs, rather than buying to the minimum alone.

Keep these storage roles distinct:

  • Boot and system storage: Holds ESXi and its system data, including ESX-OSData.
  • VM datastore: Stores VM files, including virtual disks in VMDK format.
  • Backup storage: Holds recoverable copies outside the local failure risk.

ESXi does not provide Linux MDAM software RAID. Use a supported hardware RAID or other supported storage design that fits the workload. RAID can reduce the impact of a drive failure, but it does not replace backup.

Collect Remote Access and Network Details

Ask the provider for these inputs before removing the current OS:

Invoer Required detail
console op afstand How to open it when the host OS is unavailable
virtuele media Whether the access level supports mounting an ISO
Management network IP address, prefix or subnet mask, gateway, and VLAN
Physical uplink Which NIC and port connect to the required network
DNS Approved resolvers, hostname, and domain settings
Guest addressing Bridged addresses, routed subnet, private network, or router VM
Mac-beleid Whether extra virtual MAC addresses need approval
Herstel Support contact and recovery method after a network fault

IPMI, iDRAC, iLO, and remote KVM provide access to the physical server. Remote KVM here means keyboard, video, and mouse access. It is separate from the KVM virtualization technology used by platforms such as Proxmox VE.

How to Install VMware ESXi 8 on a Dedicated Server

Use an interactive installation through remote media for this single-host setup. Broadcom lists remotely mounted ISO media as an installation method. The checks below assume a fresh deployment, not an in-place upgrade.

Step 1: Back Up Data and Confirm the Recovery Path

Copy required data and configuration records to storage outside the server. Confirm that you can retrieve those copies.

Then open the remote console and check that it shows the server’s screen during boot. Record the disk inventory, current boot mode, network inputs, and recovery contact.

Checkpoint: You can control the host without relying on its installed OS, and the required data exists elsewhere.

If the remote console does not work, resolve that issue before reinstalling.

Step 2: Download the Correct ESXi Installer

Sign in to the Broadcom Support Portal. Choose the download route available under the selected entitlement or free-software option. Confirm the release, build, and image type.

Use the matching vendor image where the supported hardware design requires it. Download an installer ISO for virtual media. An offline update ZIP serves a different purpose.

Check the downloaded file against the publisher’s supplied checksum where available. Keep the image name and checksum in the deployment record.

Checkpoint: The ISO matches the intended hardware and license path. Do not select an old image only because it is easier to download.

Step 3: Mount the ISO and Boot the Installer

Open the management controller’s remote console. Attach the ISO through virtual media, then select the virtual optical drive for the next boot. Dell documents this route through iDRAC on supported PowerEdge systems.

Review the hardware settings required by the selected release, including hardware virtualization, NX/XD, and the supported boot mode. Keep Secure Boot settings consistent with the vendor’s supported configuration.

Checkpoint: The ESXi installer loads. If it fails before disk selection, capture the message and review hardware support and image integrity.

Step 4: Select the Installation Disk and Install ESXi

Continue through the installer and review the software agreement. Identify the intended boot disk from the inventory before selecting it.

Check its model, capacity, and available identifiers. If an existing installation is detected, stop and confirm that the selected option matches a fresh install.

Choose the keyboard layout and set a strong root password. Review the final disk warning before starting the write operation.

Checkpoint: Installation completes on the intended disk. If the disk list is unclear, resolve the identities before proceeding.

Step 5: Remove the ISO and Boot from Local Storage

Disconnect the installer ISO or restore the intended boot order. Reboot the server.

Confirm that the installed host reaches the Direct Console User Interface, or DCUI. Record the displayed version and build.

Checkpoint: The server boots from its installed storage. If it returns to the installer, check virtual media and boot priority before repeating installation.

Step 6: Configure the Management Network in DCUI

Press F2 and sign in. Open Configure Management Network. Select the correct adapter, set the required VLAN if the provider uses one, then configure the approved static address, mask, gateway, DNS, and hostname.

Apply the settings and use Test Management Network. Broadcom documents management address and DNS configuration through the direct console.

Keep the remote console open while checking access from the administration network. A failed ping can reflect filtering, so assess it with the provider’s policy and other connectivity checks.

Checkpoint: The host is reachable through the intended management path. If access fails, correct the NIC, VLAN, or addressing through DCUI.

Step 7: Open the Host Client and Check License Status

From the approved administration network, open https://<management-address>/ui/. Confirm the host’s identity and certificate trust before entering credentials.

After signing in, check the build, visible hardware, storage, and license mode. For an eligible ESXi 8 paid key, the Host Client provides a licensing view under Host → Manage → Licensing.

Confirm the resulting features and expiry information, where applicable. An installed hypervisor is not yet proof of a production-ready deployment.

Configure Guest Networking for Your Provider’s IP Rules

Guest networking must match the provider’s addressing and MAC policy. Copying settings from a different hosting company can leave VMs unreachable even when the ESXi management address works.

Separate Host Management from VM Traffic

A VMkernel management interface gives the administrator access to ESXi. A VM’s virtual network adapter connects its guest OS to a port group. A standard vSwitch connects the relevant ports and physical uplinks.

Use clear names for management and guest networks. Where the design permits, restrict management through a private network, VPN, or tightly scoped access controls.

A VLAN separates traffic at the network layer where it is configured. It does not automatically supply the firewall policy between those networks.

Choose an Addressing Design

Design How guest connectivity works Bevestig met de provider
Public address on each VM Guest traffic uses an approved uplink and assigned addresses Permitted MACs, gateway, VLAN, and address allocation
Routed public subnet A router forwards the assigned subnet toward the guests Next hop, routing responsibility, and return path
Private guests behind a router VM A guest router/firewall provides routing or NAT WAN addressing, port forwarding, and recovery access
Private VM network Guests communicate on an internal network Whether and how that network reaches other hosts or the internet

ESXi’s standard vSwitch is not a general-purpose NAT router. NAT requires a suitable router, firewall, or other network service.

Hetzner’s documentation provides one example of host-specific MAC and routed-subnet requirements. Those rules are provider-specific, not universal Atal Networks settings.

If a router VM runs on the only host, it can also become part of the management recovery dependency. Keep out-of-band access available when that router is stopped or broken.

Plan IPv6 as its own routed design. Our IPv6 deployment guide covers related dual-stack planning.

Create a Datastore and Deploy the First VM

Create or select usable VM storage, then deploy a small test guest before adding important workloads. This checks the storage and network paths without making the first application migration the test.

Create VMFS Storage

In the Host Client, open Opslag and inspect the existing datastores. If you need a new local datastore:

  1. Kiezen New datastore.
  2. Choose the VMFS creation option.
  3. Give it a clear name, such as vm-storage-01.
  4. Identify the correct disk or logical volume.
  5. Review the partition selection and capacity.
  6. Confirm only after checking the erase warning.

Broadcom notes that a VMFS datastore normally does not require command-line formatting. Do not use a disk-format command simply because a copied tutorial includes one.

If the installer already created a datastore, review its available space before adding another. System partitions and storage formatting reduce the space available for guest files.

Install a Test Guest

Upload a supported guest OS ISO to the datastore. Open Virtual Machines → Create / Register VM, then choose the new VM option. Select its guest type, storage, resources, and approved port group. Attach the ISO and install the OS.

For a light Linux test, 2 vCPUs, 4 GB RAM, and a 32 GB virtual disk are example starting allocations. They are not application sizing advice or measured performance results. Check the guest OS requirements.

After installation, add the supported guest tools, such as open-vm-tools where appropriate. Check:

  • The guest sees its assigned CPU, RAM, and disk.
  • The expected IP address and route are present.
  • DNS resolution works.
  • Required outbound connections work.
  • Approved inbound services are reachable from a separate machine.
  • Blocked services remain inaccessible.

Also check reboot behavior. If VMs must start automatically after host recovery, configure and test the appropriate startup order. A router or identity service may need to start before an application that depends on it.

Watch Thin-Provisioned Storage

A thin-provisioned virtual disk can grow as the guest writes data. Its advertised size is not necessarily its current physical use.

We recommend monitoring actual datastore free space and growth. Include snapshots, logs, backup staging, and future writes in the capacity plan. A VM that appears to have free space inside its OS can still face problems when the host datastore fills.

Secure, Patch, and Back Up the ESXi Host

Before production, restrict administration, establish a supported update process, and complete an off-host restore test. These tasks determine whether the host can be maintained and recovered after installation.

Restrict Administrative Access

We recommend the following baseline for a remote host:

  • Restrict management access to approved networks and administrators.
  • Use named accounts with suitable permissions where possible.
  • Store root credentials securely and control emergency access.
  • Keep SSH stopped when it is not needed.
  • Protect the remote management controller separately.
  • Record the host’s management and guest network configuration.
  • Test the recovery route before applying access restrictions.

Keep management services out of broad public access. A reachable guest website does not require public access to the ESXi administration interface.

Configure Time and Remote Logs

Use approved NTP servers so host time remains consistent. Check that the service starts as intended and that synchronization works. Broadcom provides NTP configuration guidance for ESXi 8

Send relevant logs to a remote syslog service. This preserves useful evidence when a host or local disk becomes unavailable. Broadcom documents both local log storage and remote forwarding.

Treat the log server as a service that also needs retention, access control, and monitoring. Configuring a destination on ESXi does not manage that remote system for you.

Establish the Patch and Maintenance Path

Choose the update procedure for the actual edition, build, OEM components, and entitlement. Read the target release notes and check product interoperability before applying changes. Broadcom documents an esxcli update route, but it requires the correct image and preparation.

The free U3e edition needs particular care. Broadcom documents a Lifecycle Manager incompatibility for that edition and states that patching it through LCM is not supported. Do not assume that a free host can follow the same update process as a vCenter-managed host.

Before accepting a maintenance plan, confirm that you can obtain and apply the required fixes through a supported path. An old image being available to download is not enough for an ongoing security plan.

For one host, plan for guest downtime when the work requires it. A license with migration features does not create a second server to receive the VMs.

Separate VM Backup, Host Configuration, and Snapshots

Different copies solve different recovery problems.

Copy or record Doel Limit
VM backup Recover a guest and its data Must include the required application state
Guest-agent backup Protect data from inside the guest OS May require rebuilding the guest before recovery
Host configuration backup or records Rebuild host settings Does not contain all guest disks
VM snapshot Support short-term change recovery Does not replace an independent backup
Inval Reduce the effect of some drive failures Does not protect against deletion or loss of the whole host

Check backup product support for the exact host edition. Free ESXi’s VADP restriction matters to products that depend on that interface. A guest-based method may still be available, but it needs its own restore procedure.

Keep required copies outside the server. Another virtual disk on the same datastore remains exposed to the same local failure.

Prove That a Restore Works

Define two targets before testing:

  • Herstelpuntdoelstelling of RPO: How much recent data the business can lose.
  • Hersteltijddoelstelling of RTO: How long the service can remain unavailable.

As an example, a six-hour RPO and a four-hour RTO mean the backup schedule and recovery procedure must support those goals. They are planning targets, not promised outcomes.

Restore a test VM or application copy onto an isolated network. Confirm that it boots, contains the expected data, and runs the required service. Record the time and dependencies involved.

Plan for the backup catalog, encryption keys, credentials, and destination capacity too. Recovery can fail if any of those exist only inside the failed host.

Troubleshoot ESXi Installation and Access Problems

Start with the observed symptom and the last change. Keep the remote console open while investigating network faults, and avoid changing several settings at once.

Symptoom Controleer eerst Volgende actie
No network adapters detected NIC model, supported native driver, image, and firmware Compare the hardware with the supported combination; use the approved OEM image where needed
No target disk shown Controller mode, logical volume, cabling/health, and driver Confirm what the controller presents to ESXi before changing storage settings
Installer returns after reboot Mounted media and boot priority Disconnect the ISO and select the installed boot device
Host Client unreachable Management NIC, address, mask, gateway, VLAN, and access policy Inspect and correct the settings through DCUI
VM has no internet access Port group, uplink, guest route, and provider MAC policy Compare each layer with the agreed network design
License capacity is insufficient Installed CPU/core inventory and available entitlement Recalculate applicable capacity and review the license allocation
Free host cannot join vCenter Applied edition Check the documented free-edition restriction before troubleshooting it as a network fault
Datastore missing or nearly full System layout, disk health, used space, and snapshot growth Identify the cause before formatting or deleting files

For a lost management connection, use the console to reverse the most recent network change. Broadcom documents DCUI management configuration and notes that changing a host’s management address can disconnect it from vCenter.

For storage faults, do not delete VM files or recreate a datastore as an initial test. Capture the state and confirm which data must be recovered first.

ESXi, Proxmox VE, or XCP-ng: Which Fits One Dedicated Server?

Choose the platform that supports the required applications, backup workflow, hardware, and staff skills. An existing VMware environment can favor ESXi; a new project should compare the full operating cost and recovery method across platforms.

Optie Management and backup context A practical reason to consider it
Free ESXi 8.0 U3e Direct host management with the documented integration limits A small standalone deployment that fits its terms and restrictions
Paid VMware environment Features and management depend on the edition and design Existing VMware integrations, skills, or application requirements
Proxmox VE Integrates KVM VMs, LXC containers, management, and backup functions A project seeking an open-source VM and container platform
XCP-ng with Xen Orchestra Xen-based hosts with a separate management and backup platform A team that prefers the Xen/Xen Orchestra operating model

Proxmox documents its KVM, LXC, clustering, and management features. XCP-ng documents Xen Orchestra’s role in backup and recovery. These platforms have different storage, networking, support, and migration details. Do not choose on a feature-name checklist alone.

Compare the Full Cost of Running the Host

Use the same billing period and scope for each option.

Operating cost = server rental

               + platform licensing or support

               + guest software

               + backup software and storage

               + IP and network options

               + administration and recovery work

Include any management appliance resources in host sizing. Also account for the work needed to move VM disks, replace guest tools, adjust drivers, and test applications during a platform migration.

Open-source software can remove a proprietary license requirement. It does not remove the need for supported updates, backup capacity, or staff time.

What to Confirm Before Ordering an ESXi Host

Send the provider a clear deployment specification: exact ESXi release, CPU sockets and cores, RAM needs, supported NIC/controller requirements, storage layout, remote ISO access, IP design, license responsibility, and backup method.

Onze Bare Metal Server-opties provide a starting point for hardware planning. For a VMware deployment, send us those requirements with your workload and recovery targets so we can review a suitable dedicated server configuration. Confirm ESXi compatibility, software rights, and support scope for the exact order.

Veelgestelde vragen

Can I Install VMware ESXi 8 on a Rented Dedicated Server?

Yes, if the hardware supports the intended ESXi build and the provider permits installation through remote media or an approved template. Confirm the NIC, storage controller, firmware, installer access, and license position first. Keep remote console recovery available before removing the existing OS.

Is VMware ESXi Free Again?

Broadcom documents a free ESXi 8.0 U3e edition. It has limits on VM size, central management, backup APIs, and support. Check those limits and the applicable terms before choosing it. Free availability does not mean it matches every operating or recovery requirement.

Do I Need vCenter for One ESXi Host?

You can administer a standalone host through its ESXi Host Client. Whether you need vCenter depends on the management functions and integrations required. Check the license and infrastructure dependencies for those features. Adding vCenter alone does not give a single physical server host-failure protection.

How Many Cores Must I License on a Dual-CPU Server?

Under Broadcom’s documented VCF/VVF rule, count each installed CPU’s physical cores with a floor of 16 per CPU. Two 12-core CPUs therefore require 32 cores of capacity under that rule. Confirm the applicable product and quote conditions separately from this calculation.

Can I Install ESXi Through IPMI or iDRAC?

Yes, where the server’s remote management access supports a console and virtual media. Mount the approved ISO and boot the physical host from it. Check the access level before ordering because virtual-media functions can depend on the management controller’s licensing or the provider’s configuration.

Can I Use Linux Software RAID with ESXi?

ESXi does not use Linux MDAM arrays as its local RAID implementation. Plan a supported hardware RAID or another supported storage arrangement. Confirm the exact controller, firmware, driver, and disk presentation. A server listing that mentions RAID does not establish that the design fits ESXi.

How Do ESXi VMs Get Public IP Addresses?

The provider’s network design determines the method. Guests may use approved public addresses and virtual MACs, a routed subnet, or private addressing behind a router/firewall VM. Ask for the gateway, VLAN, MAC, and routing requirements. Host management connectivity does not prove guest connectivity.

Can the Free ESXi Edition Use Image-Level Backup Tools?

Check the backup product’s required interfaces and edition support. The documented free U3e edition does not provide VADP-based backup. That affects products using VADP, but does not rule out every guest-based backup method. Test the actual restore path before relying on it.

What Happens if My Only ESXi Host Fails?

Its local VMs become unavailable. Recovery requires repairing the host or restoring onto suitable replacement capacity. Keep backups, recovery credentials, and configuration records outside that failure risk. Cluster high availability needs a separate multi-host design; a one-host installation cannot restart workloads on another server that does not exist.

Should I Choose ESXi 8 or a Newer ESX Release?

Compare hardware support, application integrations, licensing, maintenance access, and lifecycle. ESXi 8 may fit an existing environment, but include its support end date in planning. Newer releases can change both compatibility and licensing workflow. Do not treat a major-version upgrade as a routine patch.

Aanbevolen volgende stappen

Start with the license features, exact hardware, and network inputs. Then install ESXi, deploy one test guest, and complete an off-host restore check. Move important workloads only after the host’s access, maintenance, backup, and recovery procedures work as planned.

Scroll naar boven