6.5.1

Table Of Contents
Figure 25. vSphere Auto Deploy Installation, First Boot
PXE
Host sends hardware
and network information
to Auto Deploy server
Auto Deploy server
streams host and image
profiles to the host
Host boots using
image profile
Subsequent Boots Without Updates
For hosts that are provisioned with vSphere Auto Deploy and managed by avCenter Server system,
subsequent boots can become completely automatic.
1 The administrator reboots the host.
2 As the host boots up, vSphere Auto Deploy provisions the host with its image profile and host profile.
3 Virtual machines are brought up or migrated to the host based on the settings of the host.
n
Standalone host. Virtual machines are powered on according to autostart rules defined on the
host.
n
DRS cluster host. Virtual machines that were successfully migrated to other hosts stay there.
Virtual machines for which no host had enough resources are registered to the rebooted host.
If the vCenter Server system is unavailable, the host contacts the vSphere Auto Deploy server and is
provisioned with an image profile. The host continues to contact the vSphere Auto Deploy server until
vSphere Auto Deploy reconnects to the vCenter Server system.
vSphere Auto Deploy cannot set up vSphere distributed switches if vCenter Server is unavailable, and
virtual machines are assigned to hosts only if they participate in an HA cluster. Until the host is
reconnected to vCenter Server and the host profile is applied, the switch cannot be created. Because the
host is in maintenance mode, virtual machines cannot start. See Reprovision Hosts with Simple Reboot
Operations.
Any hosts that are set up to require user input are placed in maintenance mode. See Update the Host
Customization in the vSphere Web Client.
vSphere Installation and Setup
VMware, Inc. 116