6.0.3

Table Of Contents
ESXi Provisioning and VMCA
When you boot an ESXi host from installation media, the host initially has an autogenerated certicate.
When the host is added to the vCenter Server system, it is provisioned with a certicate that is signed by
VMCA as the root CA.
The process is similar for hosts that are provisioned with Auto Deploy. However, because those host do not
store any state, the signed certicate is stored by the Auto Deploy server in its local certicate store. The
certicate is reused upon subsequent boots of the ESXi hosts. An Auto Deploy server is part of any
embedded deployment or management node.
If VMCA is not available when an Auto Deploy host boots the rst time, the host rst aempts to connect,
and then cycles through shut down and reboot until VMCA becomes available and the host can be
provisioned with a signed certicate.
Host Name and IP Address Changes
In vSphere 6.0 and later, a host name or IP address change might aect whether vCenter Server considers a
host's certicate valid. How you added the host to vCenter Server aects whether manual intervention is
necessary. Manual intervention means that you either reconnect the host, or you remove the host from
vCenter Server and add it back.
Table 52. When Host Name or IP Address Changes Require Manual Intervention
Host added to vCenter Server
using... Host name changes IP address changes
Host name vCenter Server connectivity problem.
Manual intervention required.
No intervention required.
IP address No intervention required. vCenter Server connectivity problem.
Manual intervention required.
ESXi Certicate Management (hp://link.brightcove.com/services/player/bcpid2296383276001?
bctid=ref:video_esxi_certs_in_vsphere)
Chapter 5 Securing ESXi Hosts
VMware, Inc. 161