8.0

Table Of Contents
You can also list all components in a sofware depot with the Get-DepotComponents cmdlet:
PS C:\> Get-DepotComponents -Depot C:\Intel-
i40en_1.12.3.0-1OEM.700.1.0.15843807_18058526.zip
The command output is:
Name Version
ID Vendor
---- -------
-- ------
Intel-i40en 1.12.3.0-1OEM.xxxxx Intel-i40en:1.12.3.0-1OEM.xxxxx
Intel
You can use any number and combination of online and offline software depots.
2 Create a software specification. For example:
{
"base_image": {
"version": "8.0.xxxxx"
},
"add_on": {
"name": "testaddonv1",
"version": "1.0.0-1"
},
"components": {
"Intel-i40en": "1.12.3.0-1OEM.xxxxx"
}
}
The software specification is a JSON file that contains information about the ESXi base image
and additional packages, such as a vendor add-on.
3 Generate a custom PXE image by running the New-PxeImage cmdlet with the parameters
Depots,SoftwareSpec and Destination. For example:
New-PxeImage -Depots “c:\temp\VMware-ESXi-8.0xxxxx-xxxxx-depot.zip” ,
“c:\temp\HPE-8.0xxxxx-xxx-Synergy-Addon-depot.zip” -SoftwareSpec “c:\temp\HPE-xxx-
custom.JSON” –Destination “C:\pxe-image”
The depot(s) include the path to the zip files for the supported ESXi version and vendor
add-on. The destination include the path and file name for the custom PXE file.
You can pass additional kernel options, create a live image, overwrite existing files, or
check acceptance levels for individual VIBs used during the creation of the image. For
more information about the New-PxeImage cmdlet, see https://code.vmware.com/docs/11794/
cmdletreference/doc/New-PxeImage.html.
What to do next
You can use the PXE image in remediation workflows of PXE booted ESXi hosts.
VMware ESXi Installation and Setup
VMware, Inc. 56