Are you using vCM to feed the compliance info to vR Ops, or are you simply using the basic hardening symptoms/alerts within vR Ops (native) ?
No not using VCM
I see the same issue in the latest version of vrealize operations 6.5.
The esx host compliance check seems to be run only one time. After that I correct the hardening violation and want to check again the compliance.
But it will not be updated? What do I wrong?