8.0

Table Of Contents
Cause
After the host has been added to a vCenter Server system, the boot configuration is determined
by the vCenter Server system. The vCenter Server system associates an image profile, host profile,
or folder location with the host.
Solution
u Use the Test-DeployRuleSetCompliance and Repair-DeployRuleSetCompliance
vSphere PowerCLI cmdlets to reevalute the rules and to associate the correct image profile,
host profile, or folder location with the host.
Host Is Not Redirected to vSphere Auto Deploy Server
During boot, a host that you want to provision with vSphere Auto Deploy loads iPXE. The host is
not redirected to the vSphere Auto Deploy server.
Problem
During boot, a host that you want to provision with vSphere Auto Deploy loads iPXE. The host is
not redirected to the vSphere Auto Deploy server.
Cause
The tramp file that is included in the TFTP ZIP file has the wrong IP address for the vSphere Auto
Deploy server.
Solution
u Correct the IP address of the vSphere Auto Deploy server in the tramp file, as explained in the
vSphere Installation and Setup
documentation.
Package Warning Message When You Assign an Image Profile to a vSphere
Auto Deploy Host
When you run a vSphere PowerCLI cmdlet that assigns an image profile that is not vSphere Auto
Deploy ready, a warning message appears.
Problem
When you write or modify rules to assign an image profile to one or more hosts, the following
error results:
Warning: Image Profile <name-here> contains one or more software packages
that are not stateless-ready. You may experience problems when using this
profile with Auto Deploy.
VMware ESXi Installation and Setup
VMware, Inc. 214