This article covers the process of creating a basic vSphere Host Profile and the steps to remediate an ESXi host using it.
vSphere 8.0
[Pre-Confirmation]
The version of the target ESXi host to be remediated using the Host Profile must be the same as or a later version than the source ESXi host (Reference Host) from which the Host Profile was configured.
For details, please refer to the [Version Check] section of the official documentation.
[Procedure for Creating a Host Profile]
For detailed steps on creating a new Host Profile, please refer to: How Do You Create a vSphere Host Profile?.
[Procedure for Remediating an ESXi Host Using a Host Profile]
1. Attach the ESXi host (to be remediated) to the Host Profile.
For detailed steps, refer to: How Do You Attach or Detach Hosts and Clusters to a vSphere Host Profile?.
2. Perform a compliance check to confirm the differences between the Host Profile configuration and the ESXi host configuration.
For detailed instructions on performing a compliance check, refer to: How Do You Check Compliance of Hosts or Clusters to a vSphere Host Profile?.
3. To view the compliance results, select the Host Profile for which the compliance check was performed, and select the [Monitor] tab.
Note: If the [Customization Required] column is displayed as [Yes], the Host Profile must be customized before remediation can be performed.
4. If the [Customization Required] column is [Yes], check the box next to the attached ESXi host displayed under [Monitor] - [Compliance] and select [EDIT HOST CUSTOMIZATIONS].
5. In the [Customize hosts] menu, manually enter the [Value] for properties that are blank in the [Value] column, but where the [Required] column is [Yes], then select [OK].
6. Once the [Customization Required] column changes to [No], check the box next to the ESXi host again and select [REMEDIATE].
For a detailed explanation, refer to: How Do You Remediate a Host to Comply with a vSphere Host Profile Configuration?.
7. After the host reboots, perform a compliance check again (Step 2 above) to confirm that the host is compliant with the Host Profile.
If the host is non-compliant, display the compliance check results (Step 3) to identify which parameters are non-compliant.