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 Auto Deploy.

About this task

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.