6.7
Table Of Contents
- vSphere Host Profiles
- Contents
- About vSphere Host Profiles
- Introduction To vSphere Host Profiles
- Using Host Profiles
- Access Host Profiles
- Create a Host Profile
- Attach Entities to a Host Profile
- Detach Entities from a Host Profile
- Check Compliance
- Remediate a Host
- Edit a Host Profile
- Duplicate a Host Profile
- Copy Settings from Host
- Host Profiles and vSphere Auto Deploy
- Import a Host Profile
- Export a Host Profile
- Copy Settings to Host Profile in the vSphere Web Client
- Configuring Host Profiles
- Recommended Host Profiles Upgrade Workflows
- vCenter Server Upgrade from 6.0 to 6.7 With Stateful ESXi Hosts Version 6.0 or Earlier
- vCenter Server Upgrade from 6.5 to 6.7 With Stateful ESXi Hosts Version 6.5 or Earlier
- vCenter Server Upgrade from 6.0 to 6.7 in Environment With Stateless ESXi 6.0 Hosts Only
- vCenter Server Upgrade from 6.5 to 6.7 in Environment With Stateless ESXi 6.5 Hosts Only
- Answer File Field and Host Profile Extraction
- Troubleshooting Host Profiles
A non-compliant status indicates a discovered and specific inconsistency between the profile and the
host. To resolve this, you should remediate the host. Any unknown status indicates that the compliance of
the host could not be verified; to resolve the issue, remediate the host through the host profile. Very often
the compliance check fails because the host is disconnected.
Note Host profiles do not capture offline or unpresented devices. Any changes made to offline devices
after extracting a host profile will not make a difference to the compliance check results.
What to do next
To see more detail on compliance failures, select a host profile from the Host Profiles main view for
which the last compliance check produced one or more failures. In order to see specific detail on which
parameters differ between the host that failed compliance and the host profile, click on the Monitor tab
and select the Compliance view. Then select the failing host. The differing parameters are displayed in
the Compliance window, below the host list.
Remediate a Host
In the event of a compliance failure, use the Remediate function to apply the host profile settings onto the
host. This action changes all host profile managed parameters to the values contained in the profile
attached to the host.
Prerequisites
Verify that the profile is attached to the host.
Procedure
1 Navigate to Host Profiles main view.
2 Right-click the host profile and select Remediate.
Note Certain Host Profile policy configurations require that the host be rebooted after remediation.
In those cases, you are prompted to place the host into maintenance mode. You might be required to
place hosts into maintenance mode before remediation. Hosts that are in a fully-automated DRS
cluster are placed into maintenance mode at remediation. For other cases, the remediation process
stops if the host is not placed into maintenance mode when it is needed to remediate a host.
3 Select the host or hosts you want to remediate with the host profile.
The host profile will be applied to each host that you select.
4 (Optional) Enter the host customizations to specify host properties or browse to import a host
customization file.
You can update or change the user input parameters for the Host Profiles policies by customizing the
host, and click Next.
Note See Host Profiles and vSphere Auto Deploy for more information about vSphere Auto Deploy.
vSphere Host Profiles
VMware, Inc. 11