Service ntpd doesn't meet the policy on <HOSTNAME>.vSphere 7.x.
vSphere 8.x.
The startup policy for the "NTP Daemon" (ntpd) service on the target host is configured differently than the policy defined in the Host Profile.
For example, the profile may expect the service to "Start and stop with host," while the non-compliant host is set to "Start and stop manually."
To resolve the compliance failure, update the startup policy of the NTP Daemon service on the non-compliant host to match the cluster's reference configuration.
Select the affected ESXi host within the vSphere Client inventory.
Navigate to the Configure tab.
Under the System section, select Services.
Search for or locate the NTP Daemon service in the services list.
Select the service and click Edit Startup Policy....
Change the Startup Policy to align with the rest of the cluster (typically Start and stop with host).
Click OK to save the changes.
Re-run the Check Host Profile Compliance task to verify the host is now compliant.