Process workflow for SCCM Deployment Remediation

For SCCM/Configuration Manager remediation workflow, the available guidance in the provided material is centered on Microsoft Intune Remediations rather than a dedicated SCCM remediation workflow guide.

Relevant guidance:

• Remediations in Intune are script packages used to detect and fix common support issues.
• A remediation package contains:
  • a detection script
  • a remediation script
  • metadata
• In the Intune admin center, Remediations are located at: Devices > Manage devices > Scripts and remediations
• For custom script packages:
  1. The detection and remediation scripts must be in the same package.
  2. The detection script must return exit 1 when the issue is detected.
  3. If any other exit code is returned, the remediation script won’t run.
  4. Recommended settings listed in the guidance include:
     • Run this script using the logged-on credentials: depends on the script
     • Enforce script signature check: No
     • Run script in 64-bit PowerShell: No
  5. Assign the package to device groups and complete Review + Create.

If the goal is specifically SCCM application detection/remediation behavior after changing a detection method, the provided guidance says:

• Existing clients do not immediately receive the updated detection logic.
• Clients evaluate it during the regular deployment reevaluation cycle, which by default is every 7 days.
• To accelerate this, in the SCCM console: right-click the device collection > Client Notification > Evaluate Application Deployments
• Update Content is not required when only the detection method changes.

• Remediations
• Remediations
• SCCM : What are actions to do after updating the detection method - Microsoft Q&A