Skip to main content
The Microsoft Configuration Manager integration, also known as SCCM, lets you automate the diagnosis and maintenance of its client on Windows devices managed with FlexxClient. When you turn it on, the flows and microservices needed to manage client health, policies, inventories and the evaluation of existing deployments are created. The microservices use FlexxAgent’s execution capability on the devices. The flows determine when they run and on which devices.
The integration automates local SCCM client operations with FlexxAgent’s existing execution capability. Collection synchronization, central queries to the server and installing or uninstalling the SCCM client are not part of its scope.

Automations created by the integration

Requirements

  • Windows devices managed with FlexxClient and with FlexxAgent running.
  • SCCM client installed and configured to run Configuration Manager actions.
  • Permissions to manage the integration, configure flows and run device microservices.
  • Connectivity of the SCCM client with its infrastructure for the operations that require it.
On devices co-managed with Intune, enable the automations according to the workloads that remain under Configuration Manager management.

Turn on the integration

  1. Go to Settings → Integrations → Microsoft Configuration Manager (SCCM).
  2. Select the organization in which you want the SCCM automations to be available.
  3. Turn on the integration. FlexxClient creates the flows and microservices associated with the package.
  4. Review the created resources before putting them into operation.
  5. Run the diagnostic microservice on the pilot devices and review the results before applying fixes.
  6. Configure each flow:
    • Targets. Devices, workspace groups or reporting groups that receive the automation. Start with a representative pilot group.
    • Conditions and schedule. When the flow runs and the minimum time between runs.
    • Recoveries. Recovery actions you want to enable.
  7. Enable the necessary flows once their behavior has been validated in the pilot group, and gradually expand the target devices.
Flows are created disabled. The package includes a diagnostic microservice that queries the client status without applying fixes.
Detection only evaluates the flow conditions without running its actions. If the SCCM diagnosis is inside a microservice, this mode does not run it. To check the client, use the diagnostic microservice.

How each run works

Each automation follows the same operating cycle:
  1. Check. The microservice reviews the prerequisites and the local status of the SCCM client.
  2. Determine whether action is needed. If the check does not detect the expected condition, it finishes without running the fix.
  3. Run the enabled action. The microservice uses the client’s local interfaces to request the corresponding operation.
  4. Verify and log. It collects the result of the request and, when it can be checked, the subsequent evidence on the device. If a review is needed, it says so in the output.

How the automations work

Client health

The diagnosis checks for the presence of the client, the status of the SMS Agent Host service (CcmExec) and access to the local interfaces the actions need. It identifies the issues that prevent the client from working and provides useful information for support. If the service is stopped and recovery is enabled, the microservice starts it and checks its status again. Microsoft documents this check as part of the client health checks. If the client is not installed, is damaged or the recovery does not resolve the issue, the result indicates that intervention is needed. Installing or reinstalling the client and deep Windows repairs are outside the scope of this integration.

Machine policies

The flow requests the client to retrieve and evaluate machine policies through Configuration Manager’s local actions. It lets you review devices that are not processing their policies correctly. The verification distinguishes an accepted request from evidence that the policy has been processed. Policy assignments and content are still managed in SCCM.

Hardware and software inventories

The flow requests the SCCM client’s hardware and software inventory cycles. Each cycle uses the configuration assigned to the client in Configuration Manager. The result reports the request and the available local evidence. To confirm the update on the server, check in SCCM that the inventory has been received and processed.

Deployment evaluation

The flow requests the re-evaluation of existing application and software update assignments through the Configuration Manager client actions. SCCM continues to control assignments, deadlines, content, maintenance windows and restart behavior. The re-evaluation can lead to actions on already assigned deployments, depending on this configuration and its exceptions.
Before enabling this automation, review the pilot group’s deployments and the effect a re-evaluation can have on the devices.

View the results

  1. Go to Operations.
  2. Open the operation details.
  3. View the microservice output in the Workspaces tab. The output identifies the device, the check performed, the requested action and the result of the local verification. Issues that need intervention include a description that lets you continue the diagnosis.
A successful response from the TriggerSchedule method proves the call succeeded, but not that the cycle finished or that the server records were updated. Confirm in Configuration Manager the results that depend on the server.

Resolve common issues

  • The flow does not act. Check whether it is enabled, whether the device is within scope and whether the conditions are met. Also check Detection only and the minimum time between runs.
  • The microservice cannot run. Check FlexxAgent availability, permissions and the prerequisites indicated in the output.
  • The SCCM client is not operational. Check the service, the local logs and connectivity with the Configuration Manager infrastructure.
  • The request is successful, but SCCM does not show the result. Check the local cycle and the processing on the server before repeating the action.

Manage or stop the automations

You can adjust the scope and configuration of each flow:
  • To stop a specific automation, disable its flow.
  • To stop all automations managed by the integration, turn off the integration. Turning it off prevents new runs and cancels requests that are still in the platform queue and have not yet been sent to the device. Requests already sent can complete, and operations the SCCM client has already accepted continue under its control.

Manage the integration resources

FlexxClient links the package’s flows and microservices to the integration. Their configuration is kept when the integration is turned off and on again.
  • Activation and reactivation. Turning on again an integration that is already active does not duplicate its resources or change its configuration. When you reactivate a turned-off integration, its resources are reused and the flows remain disabled until you enable them again.
  • Devices that reconnect. They do not receive the pending requests that were canceled when the integration was turned off, and reactivation does not recover them. New runs depend on the enabled flows and their conditions.
  • Customizations. Customized copies are managed independently: they do not receive package updates and are not disabled when the integration is turned off. Review and stop them separately when necessary.
  • Updates. Package updates keep the configured scope, schedule and parameters. They do not enable disabled flows or expand the target devices, and new flows are created disabled. If a resource contains local changes, the update does not overwrite them automatically; review them before applying the new version.
  • Manual execution. Manual execution of the microservices remains subject to platform permissions and the status of each microservice.

Related information