6.7

Table Of Contents
Table 59. vSphere ESXi Image Builder Cmdlets (Continued)
Cmdlet Description
Set-EsxImageProfile
Modifies a local ImageProfile object and performs validation tests on the modified profile. The
cmdlet returns the modified object but does not persist it.
Export-EsxImageProfile
Exports an image profile as either an ESXi ISO image for ESXi installation, or as a ZIP file.
Compare-EsxImageProfile
Returns an ImageProfileDiff structure that shows whether the two profiles have the same VIB
list and acceptance level. See Acceptance Levels.
Remove-EsxImageProfile
Removes the image profile from the software depot.
Add-EsxSoftwarePackage
Adds one or more new packages (VIBs) to an existing image profile.
Remove-
EsxSoftwarePackage
Removes one or more packages (VIBs) from an image profile.
Image Profiles
Image profiles define the set of VIBs that an ESXi installation or update process uses. Image profiles
apply to hosts provisioned with vSphere Auto Deploy and to other ESXi 5.x hosts. 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.
n
Two VIBs with the same name, but two different versions, cannot coexist. When you add a new
version of a VIB, the new version replaces the existing version of the VIB.
n
No acceptance level validation issues exist.
VMware ESXi Installation and Setup
VMware, Inc. 36