How to make a custom ESXi installation
you can make an ESXi ISO image with drivers you need, yourself. First of all you need to install the ESX Powershell on your Windows10 machine. To do is open a PowerShell in Administrator mode and install the VMWare PowerShell by typing:
Install-Module -Name VMware.PowerCLI
Step 1: Install ESXi PowerShell Module Run PowerShell with elevated privilege (run as administrator) PS D:\> Install-Module -Name PowerShellGet -Force PS D:\> Install-Module -Name VMware.PowerCLI Step 2: Changing the Windows PowerShell Script Execution Policy PS D:\Set-ExecutionPolicy Unrestricted Step 3: Download ESXi-Customizer-PS Go to https://www.v-front.de/p/esxi-customizer-ps.html and download ESXi-Customizer-PS-v2.5.1.ps1 and move the script to D:\ (to ease our job) Step 4: Run PowerShell script (see below)
this could take some time. Eventually you should have the ESXi-Customizer-PS-vX.X.X on your Desktop.
Next you need to know what drivers you are installing. Therefore you need list of available drivers. You can find this list by following this link:
Once you found the driver you need, make a note of the name like net55-r8168.
We now can create a ESXi ISO with the driver you need. To do this open your PowerShell as administrator and enter the following
C:\Users\Administrator\Desktop\ESXi-Customizer-PS-v2.6.0.ps1 -v67 -sip -vft -load net55-r8168,esx-ui,sata-xahci,esxcli-shell
OK to clarify this command line:
ESXI-Customizer-PSxxx is the ESXi PowerShell you just installed. Note that you need to know where you have put it. In this case it's on the Desktop.
Next -v67 is the ESXi Version you like to install like v55 or v60. In this case its ESXi Version 6.7 (v67)
-sip -vft -load are parameters to make sure everything is package in you ISO via an Online Repository.
Lastly we enter the packages we like to have in our ESXI ISO image.
Hit return and follow the instructions. It should finish with you ISO packaged with your drivers in it.
Next start RUFUS and make your bootable USB.
If you encounter the issue that your connection is refused/closed than enter the following command into an elevated PowerShell:
[Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Ssl3
Reboot the machine and try again. This issue is due to the use of SSL3.
Your ArtIT Team