8.0

Table Of Contents
Table 4-18. Rule Engine PowerCLI Cmdlets (continued)
Command Description
Add-CustomCertificate
Adds a custom certificate to the VMware Endpoint
Certificate Store and associates it with an ESXi host.
The certificate becomes active upon host reboot.
You can use the Get-CustomCertificate cmdlet to
retrieve the custom host certificate key. You can run
the command with the
-HostId [MAC_Address |
BIOS_UUID] parameter to associate the certificate to the
host, specifying a
-Key [file:///path/to/key.key] and
-Cert [file:///path/to/cert.crt]. Using this cmdlet
requires the
AutoDeploy.Rule.Create privilege on the root
folder of vCenter Server.
Remove-CustomCertificate
Removes a set of custom host certificates from Auto Deploy.
The certificate entries are deleted from the database and
the certificate files are removed from the filestore. Hosts
that have already booted with a custom certificate must be
rebooted to receive a new certificate. You must provide
at least one of -Cert or -HostId parameters. Using this
cmdlet requires the
AutoDeploy.Rule.Create privilege on
the root folder of vCenter Server.
Assign an Image Profile to Hosts
Before you can provision a host, you must create rules that assign an image profile to each host
that you want to provision by using vSphere Auto Deploy.
vSphere Auto Deploy extensibility rules enforce that VIBs at the CommunitySupported level can
only contain files from certain predefined locations, such as the ESXCLI plug-in path, jumpstart
plug-in path, and so on. If you add a VIB that is in a different location to an image profile, a
warning results. You can override the warning by using the force option.
If you call the New-DeployRule cmdlet on an image profile that includes VIBs at the
CommunitySupported level which violate the rule, set $DeployNoSignatureCheck = $true before
adding the image profile. With that setting, the system ignores signature validation and does not
perform the extensibility rules check.
Note Image profiles that include VIBs at the CommunitySupported level are not supported on
production systems.
Procedure
1 In a PowerCLI session, run the Connect-VIServer cmdlet to connect to the vCenter Server
system that vSphere Auto Deploy is registered with.
Connect-VIServer ipv4_or_ipv6_address
VMware ESXi Installation and Setup
VMware, Inc. 131