Configuration guide: Configuration Manager (SCCM) client health

Introduction

This library pack will help you monitor Configuration Manager (SCCM) client presence, compliance, and stability across your entire devices to quickly diagnose and remediate client issues.

Content list and dependency

This library pack contains the following content and dependencies:

Type	Name	Description	Dependencies
Live dashboards	Configuration Manager (SCCM) client health	Helps to monitor Configuration Manager (SCCM) client presence, compliance, and stability across your entire devices to quickly diagnose and remediate client issues.
Remote actions	Get Configuration Manager SCCM client status (Windows only)	Gathers information about different aspects of the Configuration Manager (SCCM) client, like the client connection to a site, the last update or deployment performed, and others.	Required to populate specific dashboard widgets.
	Get Configuration Manager SCCM client health (Windows only)	Gathers information about different aspects of the Configuration Manager (SCCM) client: from the client connection to a site to the last update or deployment performed.	Required to populate specific dashboard widgets.
	System Cleanup	Remotely cleans up unused files in several Windows system folders.
	Restore Configuration Manager SCCM client (Windows only)	Restores Configuration Manager-related Windows services (SMS Agent, BITS, WMI, RPC, Windows Time) and retrieves information about Configuration Manager (SCCM) clients on devices.
	Install Configuration Manager SCCM client (Windows only)	Installs the Configuration Manager client on devices.
	Uninstall Configuration Manager SCCM client (Windows only)	Uninstalls the Configuration Manager client from devices.

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 remote action(s)

Navigate to the manage remote action administration page to review and edit your remote actions.

We recommend the following configurations for these remote actions:

Name	Trigger	Schedule query	Parameters to edit
Get Configuration Manager SCCM client status (Windows only)	Scheduled, daily	Code 1 devices 2 | where operating_system.platform == Windows 3 and operating_system.name !in ["*server*"]
Get Configuration Manager SCCM client health (Windows only)	Scheduled, daily	Code 1 devices 2 | where operating_system.platform == Windows 3 and operating_system.name !in ["*server*"]
System Cleanup	Manual, can be triggered on multiple devices
Restore Configuration Manager SCCM client (Windows only)	Manual, can be triggered on multiple devices
Install Configuration Manager SCCM client (Windows only)	Manual, can be triggered on multiple devices		See the configuration notes for the Configuration Manager SCCM client remote action section.
Uninstall Configuration Manager SCCM client (Windows only)	Manual, can be triggered on multiple devices

Configuration notes for the ‘Install Configuration Manager SCCM client' remote action

This remote action comes unsigned and must be signed before use.

Nexthink at this point is unable to provide a copy of the remote action "Install Configuration Manager SCCM client" signed with a digital signature. The aforementioned remote action is used to install content from a network share (on the customer environment), however as Nexthink is unable to verify the integrity of the installer at this point (as we are not in control of the customer content), the trustworthiness of the source cannot be guaranteed. Hence Nexthink is currently unable to provide a signed copy.

• Configure the parameter location where the Configuration Manager client installer resides. 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.

• For the RA to function properly, we recommend that you specify the following parameters in the Installation Parameters input parameter: /mp:<Configuration Manager server name>/logon SMSSITECODE=<site code>

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 health