5 Replies Latest reply on Sep 2, 2016 9:40 AM by Kevin Barry

    Component template compliance issue with "disable all remediation"

    Kevin Barry

      Hi All,


      I currently have an issue with compliance and remediation that looks something like this: I need to verify a file system is present before installing a package in it, so I have two rules that look something like this:


      Rule 1: check for filesystem. On failure: disable all remediation

      Rule 2: check if package is installed. On failure: deploy package


      My problem is this: if the first check fails, remediation is forever disabled on that component. Even after someone has created the file system and rerun the discovery/compliance the package will not deploy. I have to manually delete the component and rerun for it to work. Is this by design? Is there no way I can force a discovery job to replace components? Perhaps I am going about this the wrong way.