Matthew Thompson
shared this idea
4 comments
-
Vladimir Zelenov commented
It would be great if all options have an ability for remediation.
-
Anonymous
commented
I also agree with this point the renediation is work only for equal to operator not for other.
In our case we want to use one of operator if any of value is meet it should not remediate or vice versa but as remediation is not supported this is big stucking point for us -
Martin Kupka
commented
I would specifically like to have remediation available for script based baselines. When you are running script for discovery then you are automatically running script for remediation too - that means the governance of the remediation process is in your hands anyway. By blocking the remediation to work only with "equal" condition for returned values from the script discovery you are artificially cutting the functionality.
Great example would be checking for folder size - if it goes over a threshold run remediation script. You can return true / false and do the check inside of the discovery script but then you are loosing the actual value (folder size in this example) in the process and you can't see it in the console (for cases when you don't want to remediate on some deployments).
-
Kevin Myrup - ConfigMgr Product Team
commented
With Greater than operator, what would the remediation do? It is difficult to guess what value the admin would want as the expected value. One greater than the value in the rule? 10 greater?
What value would you suggest?