VMware Cloud Community
HywelB
Enthusiast
Enthusiast
Jump to solution

Remove one symptom definition from a policy

Hi,

I am trying to remove one symptom definition from the vSphere Solution Defaul Policy, which was created on install. I am specifically trying to remove one of the hardening guide policies, CR-ROM disable. We are not concerned whether a CD-ROM is connected or not.

I have found the symptom definition but unable to change the state from "enabled (Force)"?


How do I overcome this?


Thanks

Tags (1)
1 Solution

Accepted Solutions
admin
Immortal
Immortal
Jump to solution

I would just remove (or clone and remove) the symptom from the Alert. The policy contains Alert Definitions (Two alerts, one for hosts and one for VMs are included in the vSphere Hardening Guide policy (localy enabled). So you could go to  Content -> Alert Definitions, Filter "hardening" and click on the cross symbol to remove this symptom from the alert.

Hope it helps!

tb_sc_2016-03-15_12-24-57_PM.png

View solution in original post

3 Replies
admin
Immortal
Immortal
Jump to solution

I would just remove (or clone and remove) the symptom from the Alert. The policy contains Alert Definitions (Two alerts, one for hosts and one for VMs are included in the vSphere Hardening Guide policy (localy enabled). So you could go to  Content -> Alert Definitions, Filter "hardening" and click on the cross symbol to remove this symptom from the alert.

Hope it helps!

tb_sc_2016-03-15_12-24-57_PM.png

HywelB
Enthusiast
Enthusiast
Jump to solution

Thanks Tomas, that worked however the cloned alerts are still being displayed. is there a simple way to disable that alert definition?

HG.JPG

0 Kudos
admin
Immortal
Immortal
Jump to solution

You can disable the original alert in the policy. If you just enabled the hardening guide policy as it supplied by default, you would need to go to the policy library and edit "vSphere 5.5. Hardening Guide" policy. Search for hardening and set the original policy from "local" to "disabled". (another possibility is that the alert is enabled in your default policy, may need to check that). tb_sc_2016-03-17_08-16-40_PM.png

0 Kudos