Join us at Experience '19: The Digital Employee Experience Conference. Learn More

cookie alert

We use cookies to offer you a better browsing experience, analyze site traffic, personalize content, and serve targeted advertisements. If you continue to use this site, you consent to our use of cookies.

Nexthink Library

SCCM Management

Retrieve information about the SCCM-related client services and restore them if necessary. Execute the Configuration Manager repair as per Microsoft guidelines.

Get SCCM Client Status Restore SCCM Client Invoke SCCM Client Auto-repair Start Task Sequence

Content

Remote actions - 4

Required Modules

Nexthink Act

Platforms

Windows

Compatibility

V6.14 and later
Install
  • 2.0.0.0 - Added "Start Task Sequence" Remote Action
  • 1.0.1.0 - Added new output fields to Get SCCM Client Status
  • 1.0.0.0 - Initial release

Description

This Library pack is a collection of different Remote Action scripts which collect SCCM-related client services information and restore them if needed.Please use the links on the left menu to learn more about the function and range of action of each script.

Get SCCM Client Status

Script Description

Gets SCCM-related client services status (SMS Agent, BITS, WMI, etc.) and information about SCCM client on devices.

Execution context and suggested scheduling

Run the script as 'local system'. The script should be executed manually.

A timeout of 120 seconds is recommended.

Parameters

None.

Outputs

LabelTypeDescription
SMS Agent StatusStringStatus of the SMS Agent Service
Background Intelligent Transfer Service StatusStringStatus of the Background Intelligent Transfer Service
Windows Management Instrumentation StatusStringStatus of the Windows Management Instrumentation Service
Remote Procedure Call Subsystem StatusStringStatus of the Remote Procedure Call Subsystem Service
Windows Time Service StatusStringStatus of the Windows Time Service
Client InstalledBoolIf SCCM client is installed or is not
Management SiteStringSite where the device is connecting to
Last CommunicationDateTimeLast communication date with server
Days Since Last CommunicationIntDays since last communication with server
Last Cumulative UpdateStringLast cumulative update installed on the device
Months Since Last Cumulative UpdateIntMonths since last cumulative update installed on the device
Last ScanDateTimeLast scan date
Days Since Last ScanIntDays since last scan
Missing Software UpdatesIntNumber of missing software updates

Test Scenarios

No missing updates
Test CaseThere is no missing software updates.
There is data for all fields.
EnvironmentWindows 10 Pro x64
ResultsSuccessful - All output fields show the correct data.
Missing data
Test CaseThere is no data about the last cumulative update.
EnvironmentWindows 10 Pro x64
ResultsAll output fields show the correct data.
LastCumulativeUpdate is empty.
MonthsSinceLastCumulativeUpdate is "01.01.1970 @ 01:00:00".

Restore SCCM Client

Script Description

Restores SCCM-related client services (SMS Agent, BITS, WMI, etc) and retrieves information about SCCM client on devices.

Execution context and suggested scheduling

Run the script as 'local system'. The script should be executed manually.

A timeout of 120 seconds is recommended.

Parameters

None.

Outputs

LabelTypeDescription
SMS Agent StatusStringStatus of the SMS Agent Service
Background Intelligent Transfer Service StatusStringStatus of the Background Intelligent Transfer Service
Windows Management Instrumentation StatusStringStatus of the Windows Management Instrumentation Service
Remote Procedure Call Subsystem StatusStringStatus of the Remote Procedure Call Subsystem Service
Windows Time Service StatusStringStatus of the Windows Time Service
Client InstalledBoolIf SCCM client is installed or is not
Management SiteStringSite where the device is connecting to
Last CommunicationDateTimeLast communication date with server
Last Cumulative UpdateStringLast cumulative update installed on the device

Restrictions

Further Information

When restarting SCCM-related services, services with dependent services are not stopped in the first place. For safety considerations, those services are just started in case they were previously stopped.
Keep in mind that many dependent services may affect directly critical functionality of Collector (network, etc).

Invoke SCCM Client Auto-repair

Script Description

Executes the Configuration Manager repair based on Microsoft's script center recommendations.

Execution context and suggested scheduling

Run the script as 'local system'. The script should be executed manually.

A timeout of 1080 seconds is recommended.

Parameters

LabelDescription
Maximum Delay In SecondsMaximum random delay set to avoid overloading the network. Provide number of seconds less than 600

Outputs

None.

Further Information

The repair tool can take up to 7 minutes to finish the execution, beyond that the repair will be considered stuck.

Start Task Sequence

Script Description

Triggers any SCCM Task Sequence, application or program, based on its ID.

Execution context and suggested scheduling

Run the script as 'interactive user'. The script should be executed manually.

A timeout of 720 seconds is recommended.

Parameters

LabelDescription
Maximum Delay In SecondsMaximum random delay set to avoid overloading the network. Provide number of seconds less than 600
Task Sequence IdID of the Task Sequence

Outputs

None.

Further Information

This Remote Action only works on Windows 10 devices.
In order to obtain the TaskSequenceId you can perform the following commands depending on whether it is an application or a program.
For applications - Get-CimInstance -ClassName CCM_Application -Namespace 'rootccmclientSDK'.
For programs - Get-CimInstance -ClassName CCM_Program -Namespace 'rootccmclientSDK'.

Test Scenarios

ExecutionTest
Test CaseTested that the RA triggers the specified Task Sequence
EnvironmentVM Windows 10 x86
ResultsThe Task Sequence was successfully triggered.
WrongTaskSequenceProvided
Test CaseThe Task Sequence provided is wrong
EnvironmentVM Windows 10 x86
ResultsFailure as expected providing an error message, that it has not been able to find the specified Task Sequence.
Thank you!