Usage guide: Configuration Manager (SCCM) client continuity


This workflow automatically enables you to resolve and filter out common Configuration Manager (SCCM) issues and ensure compliance across the landscape. This saves significant time for any support team, enabling them to investigate and focus on more serious problems.

Ensure your workflow is properly configured by following the steps highlighted in its configuration guide:

Configuration guide: Configuration Manager (SCCM) client continuity

Workflow Structure

This section describes the key steps in this workflow:

At the start of this workflow, there is a "Get Configuration Manager Client Status" thinklet configured to automate the retrieval of Configuration Manager (SCCM) client status information using a remote action.

Based on the results of this remote action, the workflow determines its further actions:

  • Check if WMI service is running. If not, restore the WMI service state using a remote action before moving on to the next steps.

The workflow then checks for the presence of a Configuration Manager client on the device. If the client is not installed, it starts client installation using a remote action and re-runs the Get Configuration Manager client status remote action to get updated status information.

The workflow then checks the status of the Configuration Manager client service and any underlying operating system services (BITS, RPCS, WTS) required for the client to function. If a problem is detected in any of these services, the workflow initiates a recovery procedure and then reruns the Get Configuration Manager Client Status remote action to obtain updated status information.

After the client is restored, the workflow checks to see if the client service is running. Otherwise, it reports the device using an ITSM ticket. If the client service is running, the Invoke Configuration Manager policy synchronization remote action is triggered to synchronize client policies. It then checks to see if the device has received operating system updates in the last 45 days. Otherwise, the device will be reported using an ITSM ticket.


Last updated