1 person found this helpful
This is same discussed in the kb as below but removing the vib should not harm anything. I am unsure why it shows not compliant, possibly you can remove the one with 1493 kb and install the one with 1602kb
If you remove existing one available in the list, then there is only one which is removed so when scanned against the baseline, the vib is missing could lead to non-compliant behavior
Interesting. I see in the kb: "Workaround: Create a custom baseline without the conflicting vib."
I've done this and it does seem to work. With that vib removed, the host shows as non-compliant with the default built-in baseline. I'll have to make sure that default baseline remains unattached since another admin would be likely to come along in a few days/weeks and apply it (thus reinstalling the conflicting vib).
So I think I may brought this on myself by having the HPE vibsdepot as a patch source in addition to the default VMware repository. I just reset VUM back to defaults and it seems to have cleared all of this up.