Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

Compliance state always 'Compliant' when remediation script runs

Use the output from Remediation to test and see if it was actually successful rather than assuming it was successful. Only way is to have a true non-compliance is to throw a non-zero exit code when using a script.

For more details see: https://social.technet.microsoft.com/Forums/windows/en-US/0f0f3e6f-7e9f-4376-a926-fc0b6aef5bf1/sccm-compliance-state-always-compliant-when-remediation-script-runs

15 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Mike Terrill shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

1 comment

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • Anonymous commented  ·   ·  Flag as inappropriate

    This is not my experience. If I have my remediation script produce output that is not the same as the detection script for determining compliance (e.g. STRING NOT EQUAL 'OK'), my CI/baseline will return non-compliance - which in the non-compliance string produced by the script and returned through the state message, I detail the reason for the non-compliance (e.g. '[X] was less than the threshold for compliance [Y]').

Feedback and Knowledge Base