8.0

Table Of Contents
Figure 4-7. vSphere Auto Deploy Installation, Subsequent Boots
Subsequent Boot with Image Update
Subsequent Boot with No Update
Reboot host
vCenter Server
provisions host using
host and image pofiles
Use updated
image profile
Update the host and image
profile associations stored
in vCenter Server
Check rule set
compliance
Edit and update rule set
(Optional)
Provisioning of Systems that Have Distributed Switches
You can configure the host profile of a vSphere Auto Deploy reference host with a distributed
switch.
When you configure the distributed switch, the boot configuration parameters policy is
automatically set to match the network parameters required for host connectivity after a reboot.
When vSphere Auto Deploy provisions the ESXi host with the host profile, the host goes through a
two-step process.
1 The host creates a standard virtual switch with the properties specified in the boot
configuration parameters field.
2 The host creates the VMkernel NICs. The VMkernel NICs allow the host to connect to vSphere
Auto Deploy and to the vCenter Server system.
When the host is added to vCenter Server, vCenter Server removes the standard switch and
reapplies the distributed switch to the host.
Note Do not change the boot configuration parameters to avoid problems with your distributed
switch.
Provision a Host (First Boot)
Provisioning a host that has never been provisioned with vSphere Auto Deploy (first boot) differs
from subsequent boot processes. You must prepare the host and fulfill all other prerequisites
before you can provision the host. You can optionally define a custom image profile with vSphere
ESXi Image Builder by using the vSphere Client or PowerCLI cmdlets.
Prerequisites
n Make sure your host meets the hardware requirements for ESXi hosts.
See ESXi Hardware Requirements.
n Prepare the system for vSphere Auto Deploy. See Install and Configure vSphere Auto Deploy.
VMware ESXi Installation and Setup
VMware, Inc. 159