8.0

Table Of Contents
Table 4-9. Input and Output to the vSphere ESXi Image Builder Cmdlets
Parameter Description
Input Image profiles and VIBs that are located in a software
depot are used as input to PowerCLI cmdlets running on a
Windows client.
Output PowerCLI cmdlets create custom image profiles that can
be exported to an ISO image or an offline depot ZIP
file. ISO images are used for installation. The ZIP depot
can be used by vSphere Lifecycle Manager or by esxcli
software commands to update or install images. Image
profiles are also used in vSphere Auto Deploy rules to
customize the software to provision ESXi hosts with.
Watch the video "Using Image Builder CLI" for information about vSphere ESXi Image Builder:
(Using Image Builder CLI )
Image Profiles
Image profiles define the set of VIBs that an ESXi installation or update process uses. Image
profiles apply to ESXi hosts provisioned with vSphere Auto Deploy. You define and manipulate
image profiles with vSphere ESXi Image Builder.
Image Profile Requirements
You can create a custom image profile from scratch or clone an existing profile and add or remove
VIBs. A profile must meet the following requirements to be valid.
n Each image profile must have a unique name and vendor combination.
n Each image profile has an acceptance level. When you add a VIB to an image profile with
an vSphere ESXi Image Builder cmdlet, Image Builder checks that the VIB matches the
acceptance level defined for the profile.
n You cannot remove VIBs that are required by other VIBs.
n You cannot include two versions of the same VIB in an image profile. When you add a new
version of a VIB, the new version replaces the existing version of the VIB.
Image Profile Validation
An image profile and its VIBs must meet several criteria to be valid.
n Image profiles must contain at least one base VIB and one bootable kernel module.
n If any VIB in the image profile depends on another VIB, that other VIB must also be included
in the image profile. VIB creators store that information in the SoftwarePackage object's
Depends property.
n VIBs must not conflict with each other. VIB creators store conflict information in the
SoftwarePackage object's Conflicts property.
VMware ESXi Installation and Setup
VMware, Inc. 34