Install ESXi on a Dell PowerEdge

Install ESXi with iDRAC and configure static management networking.

Introduction

30 Second Summary

Remote server work gets tense when a reboot can cut off your only view of the machine. A clear plan protects the machine you mean to change while keeping it reachable from your desk.

In this project, you will remotely install VMware ESXi 8.0 Update 3j on a Dell PowerEdge server through iDRAC Virtual Media. By the end, the host opens in VMware Host Client from Windows through a stable management address with its detected hardware verified.

What You'll Build

Picture your ESXi host opening from a stable browser address on Windows with every detected disk plus network adapter recorded for the vCenter Server deployment.

By the end of this project, you'll have:

A PowerEdge server that returns to the Direct Console User Interface after a reboot. The screen shows the installed ESXi release.
A tested static management address that opens VMware Host Client in Microsoft Edge. You can sign in with the ESXi root account.
A hardware-detection record showing which expected storage devices plus physical NICs are visible to ESXi.
Secret Mission: Synchronize the ESXi host with your network's NTP server so vCenter authentication plus certificates have a reliable time source.

Are there any prerequisites?

Your Windows computer needs working access to iDRAC Virtual Console plus Virtual Media.

Your other prerequisites are an active VMware vSphere 8 entitlement in the Broadcom Support Portal, complete management-network values, plus an installation disk approved for erasure.

Treat this as a lab build because the PowerEdge model's hardware compatibility is unconfirmed.

Before We Start

This checkpoint commits you to building a standalone VMware ESXi host as the foundation for a later vCenter Server deployment. It also confirms that the approved installation disk can be erased as part of this lab build.

Prepare the Installer and Remote Console

Your Dell PowerEdge is becoming a standalone VMware ESXi foundation for a later vCenter Server deployment.

A remote installation becomes difficult to recover when the installation disk, management address, or remote-media path is undecided before the server reboots. Your installation disk is already approved.

This step locks in the management plan. It also prepares the official installer through Dell iDRAC.

In this step, get ready to:

Document the ESXi management identity in a worksheet.
Download the official ESXi installer through your entitled account.
Map the ISO through iDRAC while the Virtual Console remains visible.

Create the management worksheet

A management worksheet gives the host one stable IPv4 identity. It keeps every network value beside the physical switch port that carries management traffic.

The optional VLAN field applies when the switch port expects tagged management traffic. The field stays empty for untagged management traffic.

Create a management worksheet in the documentation tool your team uses on Windows.
Record the hostname as <ESXi-hostname>.
Record the static IPv4 address as <static-management-IPv4>.
Record the subnet mask as <subnet-mask>.
Record the default gateway as <default-gateway>.
Record the primary DNS server as <primary-DNS-server>.
Record the optional management VLAN ID as <management-VLAN-ID>.
Record the NTP server as <NTP-server>.

Why record the switch port?

The static values describe the host inside ESXi. The switch port identifies the physical path that must carry its management traffic.

Record the physical switch port carrying ESXi management traffic.

Your management plan is now pinned down before the first reboot.

Download the entitled ESXi installer

The Broadcom Support Portal is the entitled source for the installer. Microsoft Edge keeps the download available for the iDRAC mapping workflow.

Use Your Entitled Download

Broadcom only shows product versions covered by an active license. Your confirmed entitlement is the approved source for VMware ESXi 8.0 Update 3j.

This download uses your existing entitlement. This step adds no separate project charge.

Stop the download workflow if VMware-VMvisor-Installer-8.0U3j-25429389.x86_64.iso is unavailable.
Obtain access through your Broadcom account administrator before continuing.
Use only the official image supplied through the entitled account.

Press the Windows key to open the Windows search bar.
Type Microsoft Edge and press Enter to open it.

You'll see Microsoft Edge open on your Windows computer.

Navigate to the Broadcom Support Portal.
Sign in with the account that holds your active VMware vSphere entitlement.

You'll see your signed-in account instead of the sign-in form.

Select Products.

Broadcom places base installer releases under Products.

Locate VMware ESXi 8.0 Update 3j in the base releases list.
Download VMware-VMvisor-Installer-8.0U3j-25429389.x86_64.iso to your Windows computer.

Microsoft Edge shows the installer download in progress.

Wait for Microsoft Edge to finish the download.

You'll see VMware-VMvisor-Installer-8.0U3j-25429389.x86_64.iso in the completed downloads list.

Good, your Windows computer now holds the entitled ESXi installer that iDRAC will present to the server.

Can't Find the Installer?

Confirm that you signed in with the Broadcom account that holds the active license.
Stop here if the version or installer file remains unavailable.

help me understand why the entitled ESXi installer is missing from Broadcom Support Portal.

Map the ISO through iDRAC Virtual Media

Remote Virtual Media makes the ISO on your Windows computer appear to the PowerEdge as a CD or DVD. The Virtual Console lets you watch the server while that virtual device remains connected.

In Microsoft Edge from earlier, open a new browser tab.
Navigate to the iDRAC address you already use for this PowerEdge.

You'll see the iDRAC sign-in page for your server.

You'll see the iDRAC web interface for the PowerEdge.

This part is a little fiddly because the labels change between iDRAC generations. Choose the path that matches your interface.

iDRAC9

iDRAC9 provides a direct path from the web interface to the remote console.

Select Launch Virtual Console.

You'll see the PowerEdge server console from your Windows computer.

Select Connect Virtual Media.

You'll see the controls used to map a local image to the server.

Select Map CD/DVD.
Choose VMware-VMvisor-Installer-8.0U3j-25429389.x86_64.iso from your downloaded files.

You'll see the ESXi installer filename selected in the mapping controls.

Select Map Device.

iDRAC8 or iDRAC7

The newer iDRAC8 and iDRAC7 interfaces place the mapping controls inside the Virtual Media menu.

Use the Virtual Console control that you verified earlier to open the server console.

You'll see the PowerEdge server console from your Windows computer.

Select Virtual Media.
Select Connect Virtual Media.

You'll see the controls used to map a local image to the server.

Select Map CD/DVD.
Select Browse.

You'll see the Windows file picker.

Choose VMware-VMvisor-Installer-8.0U3j-25429389.x86_64.iso.
Select Open.

You'll see the ESXi installer filename selected in the mapping controls.

Select Map Device.

Before you check, predict what Virtual Media will show beside the visible server console.

Keep the iDRAC Virtual Console visible.
Open Virtual Media from the console.
Confirm that VMware-VMvisor-Installer-8.0U3j-25429389.x86_64.iso is mapped as the virtual CD or DVD device.

You'll see VMware-VMvisor-Installer-8.0U3j-25429389.x86_64.iso mapped in Virtual Media while the PowerEdge console remains visible.

ISO Not Showing as Mapped?

Select Map Device again when the correct filename is selected.
Return to Map CD/DVD when a different file appears.
Choose VMware-VMvisor-Installer-8.0U3j-25429389.x86_64.iso before mapping the device again.

help me troubleshoot why my ESXi ISO is not mapped in iDRAC Virtual Media.

That is the remote installation path secured. Next, you will boot the PowerEdge from the mapped ISO and watch the ESXi installer load.

Boot the ESXi Installer

Your installer ISO is already mapped through iDRAC Virtual Media. The next challenge is making the Dell PowerEdge start from that remote image instead of its existing local disk.

This boot test proves the complete remote installation path works before the approved disk is changed. You will stop at the VMware ESXi installer welcome screen.

In this step, get ready to:

Request a one-time boot from the mapped virtual CD/DVD device.
Restart the PowerEdge while watching the iDRAC Virtual Console.
Confirm the ESXi installer reaches its main welcome screen.

Request a one-time ISO boot

A one-time boot request tells iDRAC which source to use for this startup. The mapped ISO must remain connected so the PowerEdge can read it.

The control names depend on the iDRAC generation. Both paths select the mapped virtual CD/DVD device as the next boot source.

Follow the tab that matches your iDRAC generation.

iDRAC9

In the Virtual Console menu, select Boot.
Choose Virtual CD/DVD/ISO.
Confirm the one-time boot request by selecting Yes.

You should see Virtual CD boot Requested by iDRAC. This confirms iDRAC accepted the one-time boot request.

iDRAC8 or Newer-Style iDRAC7

In the Virtual Console menu, select Next Boot.
Choose Virtual CD/DVD/ISO.

The one-time virtual-media boot request is now queued for the next PowerEdge startup.

Missing the virtual boot option?

The virtual boot option depends on the remote media connection remaining active.

Confirm that Virtual Media from earlier is still connected.
Confirm that VMware-VMvisor-Installer-8.0U3j-25429389.x86_64.iso remains mapped as the virtual CD/DVD device.
Use the tab for your iDRAC generation to repeat the one-time boot request.

Help me diagnose a missing virtual CD boot option in iDRAC.

Restart the PowerEdge from the console

Restarting the server can feel risky when a disk has been approved for erasure. This step only boots the installer, so the approved disk remains unchanged.

Before you restart the server, which boot source do you expect iDRAC to choose?

Keep the Virtual Console from earlier visible.
Use the Virtual Console power controls to restart the PowerEdge if it is running.
Use the Virtual Console power controls to power on the PowerEdge if it is off.
Watch the startup messages for Virtual CD boot Requested by iDRAC.

You will see Virtual CD boot Requested by iDRAC when the one-time request is accepted. This confirms the mapped ISO has priority for this startup.

Did the local disk start instead?

A local-disk boot usually means the one-time request was inactive or the ISO mapping disconnected.

Return to the Virtual Console from earlier.
Confirm that Virtual Media remains connected.
Confirm that VMware-VMvisor-Installer-8.0U3j-25429389.x86_64.iso remains mapped.
Repeat the one-time boot selection for your iDRAC generation.
Restart the PowerEdge again.

Help me troubleshoot why my PowerEdge started from its local disk instead of the mapped ESXi ISO.

Wait for the installer welcome screen

The server now reads the installer from the remote virtual CD/DVD device. The Virtual Console may appear quiet for several minutes while the installer loads, so a short pause is expected.

Before loading finishes, what screen would prove the server booted from the mapped ISO?

Allow the ESXi installer to boot automatically.
Keep the Virtual Console visible during loading.
Keep the mapped ISO connected.
Wait until the installer main welcome screen appears.

You will see the VMware ESXi 8.0 Update 3j installer main welcome screen in the Virtual Console. This screen proves the PowerEdge booted from the mapped ISO.

You have cleared the remote-boot hurdle. Next, you will install ESXi on the approved disk.

Install ESXi

The mapped installer has carried your PowerEdge to the VMware ESXi welcome screen through Dell iDRAC. You are ready to turn that remote boot into a persistent host installation.

This step installs the bare-metal hypervisor on the approved disk. The first boot then exposes ESXi's default management behavior before you assign the host a permanent identity.

In this step, get ready to:

Choose the approved installation disk.
Install VMware ESXi with a protected root account.
Reboot into the initial management state.

Choose the installation settings

The installer needs three decisions before it can write VMware ESXi to the server. Your disk choice determines which existing contents are erased.

Confirm the approved disk

Installing VMware ESXi on <selected-ESXi-installation-disk> erases its previous contents. The approval you recorded earlier is your safety check before this destructive action.

Continue from the installer welcome screen using the key shown in the Virtual Console.
Press F11 to accept the license.
Select <selected-ESXi-installation-disk> as the installation destination.
Choose your intended keyboard layout.
Enter a unique password for the root account.
Store the root password in your approved password manager.
Continue to the final installation confirmation using the key shown on screen.

Why protect the root account?

The root account controls the entire ESXi host. A unique password stored in your approved password manager keeps that administrative access recoverable without exposing the credential.

Install the hypervisor

The final confirmation is your last opportunity to catch an incorrect disk selection. Check the destination against the approved disk before starting the installation.

Review the installation summary in the Virtual Console.
Match the displayed destination with <selected-ESXi-installation-disk>.
Press F11 to start the destructive installation.
Keep the Virtual Console visible while the installer writes VMware ESXi to the disk.

The installation can remain on one progress stage for several minutes. That pause is normal while the installer prepares the disk.

That is the destructive part complete. VMware ESXi is now stored on the approved installation disk.

Reboot into the default management state

The mapped installer ISO has finished its job. Removing it allows the PowerEdge to start from the new ESXi installation instead of returning to the installer.

Return to the Virtual Media panel in the iDRAC Virtual Console.
Locate VMware-VMvisor-Installer-8.0U3j-25429389.x86_64.iso in the mapped virtual CD/DVD device.
Use the device control beside the ISO to remove its mapping.
Confirm that the ISO no longer appears as mapped.
Return to the installer completion screen in the Virtual Console.

Before you restart, do you think the host's first management address will already provide the stable identity required by vCenter Server?

Restart the PowerEdge using the reboot instruction shown by the installer.
Keep the Virtual Console visible during the restart.
Wait for the Direct Console User Interface (DCUI) to finish loading.
Read the VMware ESXi release shown in the DCUI.
Inspect the management address shown in the DCUI.

You should see VMware ESXi 8.0 Update 3j with a temporary DHCP address, a 169.254.x.x link-local address, or no usable management address. This is the intended default-network limitation.

Why is the address temporary?

ESXi uses DHCP for management networking by default. Failed automatic configuration can leave the host with a link-local address.

The management worksheet still holds the host's planned identity. The next step applies that stable configuration.

Installer appears after reboot?

Return to the Virtual Media panel.
Remove the mapping for VMware-VMvisor-Installer-8.0U3j-25429389.x86_64.iso.
Restart the PowerEdge again from iDRAC.

If the PowerEdge still returns to the installer, help me troubleshoot why the new ESXi installation is not booting from the approved disk.

Your PowerEdge now boots into VMware ESXi from its installation disk. Next, you will replace the temporary management state with the static identity from your worksheet.

Configure the Static Management Network

Your VMware ESXi host is installed. Its Direct Console User Interface is visible through Dell iDRAC.

The temporary DHCP or link-local address can change or fail to route. That uncertainty makes the address unsuitable for dependable vCenter Server management.

This step uses the DCUI to apply the management identity from your worksheet. A successful network test opens the path to VMware Host Client on Windows.

In this step, get ready to:

Match the management uplink to the documented switch port.
Apply the planned static IPv4 identity.
Prove that Windows can reach the host through VMware Host Client.

Select the management uplink

ESXi sends management traffic through one selected physical NIC. The selected adapter must match the switch port recorded in your management worksheet.

Matching the correct adapter can be fiddly because the DCUI uses adapter names instead of switch-port labels. Keep the worksheet beside the iDRAC Virtual Console while you make the selection.

In the iDRAC Virtual Console from earlier, press F2 to access the Direct Console User Interface (DCUI) configuration options.
Authenticate with the root account using the password stored in your approved password manager.
Select Configure Management Network.
Select Network Adapters.
Choose the physical adapter connected to the management switch port recorded in your worksheet.
Confirm that the intended adapter is selected before leaving the screen.

The selected adapter now matches the physical path planned for ESXi management traffic.

When Should You Set a VLAN?

Tagged management traffic needs a VLAN ID that matches the physical management network. An untagged switch port uses VLAN 0.

Apply the worksheet VLAN only when the documented switch port expects tagged traffic. Matching both sides keeps management packets on the intended network.

Return to Configure Management Network.
Select VLAN (optional).
Enter <management-VLAN-ID> only when the worksheet requires tagged management traffic.
Keep 0 when the management switch port is untagged.
Confirm that the displayed VLAN value matches your worksheet.
Confirm that the switch port uses the same tagging mode.

Unsure About the Uplink or VLAN?

Compare the selected adapter with the physical switch port recorded in your worksheet. A different adapter can leave the new management address unreachable.

Verify the switch port tagging mode before applying a VLAN. A tagged host configuration must match the physical management network.

help me check whether my ESXi management uplink and VLAN match my switch configuration.

Assign the static identity

A static management identity keeps the host reachable at the same address. DNS links that address to the hostname required for dependable management.

From Configure Management Network, choose the option for IPv4 configuration.
Select the manual static addressing method.
Enter <static-management-IPv4> as the management IPv4 address.

The IPv4 address field now shows <static-management-IPv4>.

Enter <subnet-mask> as the subnet mask.
Enter <default-gateway> as the default gateway.

The subnet mask defines the local network boundary. The default gateway provides the route beyond that boundary.

Return to Configure Management Network.
Choose the option for DNS configuration.
Enter <primary-DNS-server> as the primary DNS server.
Enter <ESXi-hostname> as the hostname.

The DNS screen now shows <primary-DNS-server>. The hostname field shows <ESXi-hostname>.

Restarting the ESXi management network can briefly interrupt access to the host address. Your iDRAC Virtual Console remains available while the new identity is applied.

Apply the management settings when the DCUI prompts you.
Confirm the management network restart.

The DCUI returns with <static-management-IPv4> displayed as the management address. This is the first visible sign that the temporary identity has been replaced.

Static Address Missing?

Return to the IPv4 settings if the DCUI still shows the temporary address. Compare every field with the management worksheet.

Recheck the selected physical adapter if the static address appears but remains unreachable. Verify the VLAN setting against the documented switch port.

help me troubleshoot why my ESXi static management address is missing or unreachable.

Test access from Windows

The Test Management Network check tests the path to your default gateway plus primary DNS server. It also asks DNS to resolve the configured hostname.

Before you start the test, do you expect every check to complete with the settings you entered? Hold that prediction for the result.

Select Test Management Network in the DCUI.
Press Enter to start the test.

You should see the gateway test pass. You should also see the primary DNS test pass.

The hostname check should resolve <ESXi-hostname>. These results prove the host can use the management network identity you configured.

Before you load the host address, do you expect the Windows computer to reach VMware Host Client through the new static identity? Keep that prediction in mind as the page loads.

In Microsoft Edge from earlier, create a new browser tab.
Open https://<static-management-IPv4>/ui in the new tab.

You should see the VMware Host Client login screen. This confirms that Windows can reach the static management address.

This is the first browser sign-in with your ESXi root credential, so a careful pause is worthwhile. Your approved password manager remains the source of truth.

Enter root as the user name.
Enter the root account password stored in your approved password manager.
Select Login.
Choose your VMware Customer Experience Improvement Program preference.
Select OK to save the choice.

That is the network hurdle cleared. The VMware Host Client home page confirms that the static management path works from Windows.

Can't Reach VMware Host Client?

Confirm that the browser address exactly matches https://<static-management-IPv4>/ui. A missing /ui path can prevent the expected login page from loading.

Return to the DCUI network test if the page remains unreachable. A failed check points back to the uplink selection or network values.

help me troubleshoot why Windows cannot reach VMware Host Client at my static ESXi address.

Your ESXi host now has a tested static management identity. Next up, you will confirm that ESXi can see the storage devices and physical NICs expected inside the PowerEdge.

Validate Storage and Network Detection

Your tested static management address proves that VMware ESXi is reachable from Windows. A reachable host can still be unsuitable for vCenter Server if expected disks or physical uplinks are missing.

This step compares the hardware visible in VMware Host Client with the Dell iDRAC inventory.

You will identify the active management physical NIC. You will also document spare NICs for future VM traffic.

In this step, get ready to:

Inspect the storage devices visible to ESXi.
Identify the physical NICs detected by ESXi.
Capture a hardware validation record for vCenter readiness.

Inspect storage detection

ESXi must detect the expected storage hardware before the host can support vCenter Server or guest workloads. Comparing both interfaces gives each expected disk or RAID virtual disk a clear status.

In the VMware Host Client session from earlier, select Storage.
Select Devices.
Select each listed device to review its details.
Leave every partition table unchanged.
Return to the Dell iDRAC web interface from earlier.
Use the hardware inventory to list the storage devices expected in the server.
Compare the expected storage list with the devices visible in VMware Host Client.
Record each match or missing device in your hardware validation notes.

Why Compare Both Views?

iDRAC reports the hardware installed at the server level. VMware Host Client shows the hardware ESXi can use.

A difference between the two views exposes a detection problem before that missing device affects vCenter Server or a guest workload.

Good progress. Your storage comparison now separates detected devices from hardware that needs remediation.

Identify physical network adapters

The current uplink proves that one NIC can carry management traffic. The Physical NICs view reveals whether ESXi also sees the adapters reserved for future VM traffic.

Switch back to the VMware Host Client session from earlier.
Select Physical NICs.
Select each adapter to review its information.
Compare the visible adapters with the iDRAC hardware inventory.
Identify the adapter carrying the active management link by matching it with the documented switch port.
Record the active management NIC in your hardware validation notes.
Record the NICs available for future VM traffic.
Record any physical adapters that ESXi does not detect.

Your notes now identify the adapter carrying management traffic. They also show the network capacity available for future VM traffic.

Missing an Expected Device?

Confirm that the missing device appears in the iDRAC hardware inventory.
Compare the device model and slot details between iDRAC and VMware Host Client.
Keep the device in your missing hardware list until ESXi detects it.

Ask for help diagnosing why an expected device is absent from ESXi: help me investigate an ESXi hardware detection problem.

Create the hardware validation record

A hardware validation record turns these checks into an input for vCenter planning. It preserves the working network identity alongside every detected device and every remediation item.

Create a new document beside your management worksheet using the documentation tool from earlier.
Title the document ESXi hardware validation record.
Record the installed release as VMware ESXi 8.0 Update 3j.
Record the installed build as 25429389.
Add the storage devices visible under Storage and Devices.
Add the physical NICs visible under Physical NICs.
Add the comparison with the iDRAC hardware inventory.
Identify the NIC carrying the active management link.

What Does This Record Prove?

The record links ESXi-visible hardware to the physical server inventory. It gives every expected device either a confirmed match or a remediation status.

That evidence makes the host reviewable before vCenter Server depends on it.

Identify the NICs available for future VM traffic.
Record the management IPv4 address as <static-management-IPv4>.
Record the hostname as <ESXi-hostname>.
Record the DNS server as <primary-DNS-server>.
Record the gateway as <default-gateway>.
Record the result of your missing-hardware comparison.
Save the completed validation record.

Before the final comparison, predict whether every iDRAC device has a matching VMware Host Client entry.

Compare Storage and Devices with the iDRAC inventory one final time.
Compare Physical NICs with the iDRAC inventory one final time.
Confirm that each expected device has a recorded match or a remediation entry.
Confirm that every required field in the validation record is complete.
Save the final validation record.

What Should I See?

The installed release is VMware ESXi 8.0 Update 3j with build 25429389.
Every ESXi-visible storage device appears alongside its iDRAC comparison.
Every ESXi-visible physical NIC appears with its recorded role.
The active management link has a named physical NIC.
The management values include <static-management-IPv4>, <ESXi-hostname>, <primary-DNS-server>, and <default-gateway>.
Every missing device has a remediation entry for completion before vCenter deployment.

That is the physical foundation proven. Your host now has an auditable hardware record for vCenter planning.

Secret mission

Synchronize the ESXi Host Clock

Your ESXi host is reachable. vCenter Server also needs a trustworthy clock. Configure persistent NTP synchronization so the host follows your network's time source.

Clean Up Your Resources

VMware ESXi 8.0 Update 3j requires applicable VMware licensing beyond any evaluation period. Decide whether to keep the host running for vCenter Server, pause it for later, or erase the lab completely.

Cost warning

Your existing VMware vSphere 8 entitlement controls access to the installer. Continuing beyond any applicable evaluation period requires valid VMware licensing.

Choose a cleanup option below that matches your organization's plan for this host.

Resources you used:

Host state: ESXi installed on <selected-ESXi-installation-disk> with the management uplink, optional VLAN <management-VLAN-ID>, gateway <default-gateway>, primary DNS server <primary-DNS-server>, and NTP source <NTP-server> configured.
Network identity: Static IPv4 address <static-management-IPv4> and the DNS hostname <ESXi-hostname>.
Root credential: The ESXi root account stored in your approved password manager.
Local artifacts: The management worksheet, ESXi hardware validation record, and VMware-VMvisor-Installer-8.0U3j-25429389.x86_64.iso file on Windows.

Keep everything running

No action is needed. Choose this option when the host is ready to become the foundation for your vCenter Server project.

Keep the Dell PowerEdge server powered on.
Preserve the tested management network configuration on the host.
Retain the static address reservation and DNS record.
Keep the management worksheet, validation record, root credential, and installer ISO available.
Use the synchronized ESXi host for the next vCenter Server project.

Pause - I'll come back to this later

A clean shutdown stops the host while preserving its installation. Your network plan and local records remain ready for your return.

Switch back to the VMware Host Client session from earlier.
Initiate a clean shutdown from the host controls.
Monitor the shutdown in the Dell iDRAC Virtual Console.

The Virtual Console confirms that ESXi has stopped. The installation and configuration remain on the selected disk.

Keep <selected-ESXi-installation-disk> unchanged.
Retain the address reservation for <static-management-IPv4>.
Retain the DNS record for <ESXi-hostname>.
Preserve the management worksheet, validation record, root credential, and installer ISO.
Use the existing iDRAC server power controls when you are ready to resume.
Return to the VMware Host Client address recorded in your management worksheet after ESXi finishes booting.

You should see the VMware Host Client login screen at the same static management address.

Delete - I don't want to use this again

Erasing the selected installation disk is intentionally destructive. It removes ESXi with its management configuration, so choose this option only when the lab is being abandoned.

Confirm that <selected-ESXi-installation-disk> is still the disk approved for erasure.
Erase or reinstall <selected-ESXi-installation-disk> through your organization's approved process.

The existing iDRAC Virtual Console should no longer display the ESXi Direct Console User Interface after the erase or replacement installation completes. This confirms that the hypervisor is no longer present.

Release <static-management-IPv4> through your organization's address-management process.
Remove the DNS record for <ESXi-hostname> from the authoritative DNS service.
Delete the ESXi root credential from your approved password manager after confirming the disk erase.

That completes the destructive part of cleanup. Finish by removing the project artifacts stored on Windows.

Locate VMware-VMvisor-Installer-8.0U3j-25429389.x86_64.iso through Windows search.
Delete the installer ISO from its saved location.
Delete the management worksheet from its saved location.
Delete the ESXi hardware validation record from its saved location.
Verify the local cleanup by searching Windows for VMware-VMvisor-Installer-8.0U3j-25429389.x86_64.iso again.

Windows should return no local copy of the installer ISO. Your network records should no longer reserve the abandoned host's identity.

That closes the lab cleanly. The erased disk and released management identity are ready for their next approved use.

Nice Work!

Strong finish! Your Dell PowerEdge now runs VMware ESXi 8.0 Update 3j as a remotely manageable bare-metal hypervisor. The host is ready to become the physical foundation for vCenter Server.

You've learned how to:

Complete a remote installation through iDRAC Virtual Media. Confirm the host's first successful boot in the Direct Console User Interface.
Replace the temporary DHCP or link-local address with a tested static management identity. Reach VMware Host Client through the static IPv4 address.
Compare detected storage devices with the iDRAC hardware inventory. Document physical NIC visibility with the active management uplink identified.
Secret Mission: Configure persistent NTP synchronization against the planned network time source. Confirm the host clock matches the authoritative time source for vCenter Server.

Ready to quiz yourself?