Configuration guide: Configuration Manager (SCCM) client continuity

Introduction

To get started with this workflow, please ensure all related content is installed and configured appropriately. This page provides guidance on which content is included and how to configure it.

Please keep in mind this is just a guide and represents suggested configurations. You are free to customize and edit content as you see fit based on your specific environment.

Pre-requisites

This library pack contains content from the following expansion products

• Flow - Workflows

Content list and dependency

This library pack contains the following content and dependencies:

Type	Name	Description	Dependencies
Workflows	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.
Remote Actions	Get Configuration Manager SCCM client status	Gets Configuration Manager client services status (SMS Agent, BITS, WMI, etc.) and information about SCCM client on devices.
	Repair WMI	Checks and repairs the Windows Management Instrumentation (WMI) service on the device.
	Restore Configuration Manager SCCM client	Restores Configuration Manager -related client services (SMS Agent, BITS, WMI, etc) and retrieves information about Configuration Manager client on devices.
	Invoke Configuration Manager SCCM client policy actions	Triggers the execution of the desired Microsoft Configuration Manager execution policy on the device.
	Install Configuration Manager SCCM client	Installs Microsoft Configuration Manager client in the target machine.

Configuration guide

To effectively use this library pack, the content must be installed and configured appropriately. Below are some suggested steps to install and configure the content properly before use.

Step 1) Install library pack content

Go to the Nexthink Library and install all required content.

Step 2) Configure ITSM API connector credentials

This workflow contains ServiceNow Incident management connector thinklets that need to be configured using the appropriate connector credentials. For more information, see ServiceNow - Incident management.

Step 3) Configure remote actions

This workflow uses the following remote actions. Make sure to install the latest versions and complete the setup as below.

Name	Trigger	Parameters to edit
Get Configuration Manager SCCM client status	API trigger should be enabled so that it can be triggered from the Workflow	N/A
Repair WMI	API trigger should be enabled so that it can be triggered from the Workflow	N/A
Restore Configuration Manager SCCM client	API trigger should be enabled so that it can be triggered from the Workflow	N/A
Invoke Configuration Manager SCCM client policy actions	API trigger should be enabled so that it can be triggered from the Workflow	MaximumDelayInSeconds PolicyToTrigger
Install Configuration Manager SCCM client	API trigger should be enabled so that it can be triggered from the Workflow	MaximumDelayInSeconds InstallerPath InstallationParameters

Invoke Configuration Manager SCCM client policy actions

The workflow uses this remote action to trigger synchronization of Configuration Manager client policies when operating system updates have not been installed on a device in the last 45 days or more.

The following RA input parameters must be configured:

Name	Value	Description
MaximumDelayInSeconds	120
PolicyToTrigger	AppDeployment DiscoveryData MachinePolicy UpdatesDeployment UpdatesScan	This parameter must be configured with a list of Configuration Manager policies that should be synchronized on the client.

Install Configuration Manager SCCM client

This remote action uses your local Configuration Manager server instance to install the client on the device.

The following RA input parameters must be configured:

Name	Value	Description
MaximumDelayInSeconds	300
InstallerPath		Configure this parameter by specifying the location where the Configuration Manager client installer is located. NOTE: This can either be locally on the device or on a share which allows all domain devices read access. Configuration example with installation from a shared folder: The remote action's "InstallerPath" input parameter must be populated with the UNC path to the client installation file, which is often similar to this: "\\<Configuration Manager server name>\sms_<site code>\Client\CCMSetup.exe" Grant client devices permission to access the shared folder specified in the "InstallerPath" input parameter.
InstallationParameters		Configure this parameter with additional installation settings that you want to pass to the Configuration Manager client that installs on devices. To get a fully working client immediately after installation, we recommend that you specify the following parameters in the "Installation Parameters" input parameter: /mp:<Configuration Manager server name>/logon SMSSITECODE=<site code>

Step 4) Maintain workflow trigger

Schedule trigger

This workflow has been designed primarily to run automatically using the schedule trigger however it can be useful to also enable the manual trigger to allow on-the-fly client remediations to be sent.

When configuring the scheduler we recommend the following settings as a baseline:

NQL:

devices during past 7d
| where operating_system.platform == Windows
 and operating_system.name !in ["*server*"]

Recurrence: Weekly - select at least one day.

Manual trigger

The manual trigger must be enabled in the workflow settings so that it can be triggered by L1 agents from Device View and Amplify on a subset of affected devices.

Usage guide

Your content is now configured and ready to be used. For usage overview and recommendations, you can visit the usage guide:

Usage guide: Configuration Manager (SCCM) client continuity

---

RELATED TOPICS

• Manage Workflows