Overview

During the investigation of SCCM Run Script execution failure, it was observed that the script deployment remained stuck at “Creating Client Jobs” in the SCCM Console and the PowerShell script did not reach the client endpoints.

After troubleshooting, the below were identified as the most probable causes for this issue:

Certificate/SSL-related communication issues
SQL Service Broker disabled in the SCCM database

Symptoms Observed

SCCM Run Script status stuck at “Creating Client Jobs”
Deployment status remained as Unknown
Scripts.log was not generated on client devices
PowerShell script execution did not start on endpoints
Notification-related errors were observed in SCCM logs

Possible Cause 1 – Certificate / SSL Issues

SCCM Run Script functionality depends on secure communication between the SCCM Server and client devices.

Certificate-related issues that can impact script execution include:

Expired or invalid SCCM certificates
SSL/TLS communication issues
IIS certificate binding problems
SSL/TLS inspection affecting SCCM notification communication

These issues can interrupt SCCM notification traffic and prevent the script payload from reaching the client devices.

Possible Cause 2 – SQL Service Broker Disabled

SCCM relies on SQL Service Broker for:

Client notification
BGB communication
Run Script execution
Client job creation processing

If SQL Service Broker is disabled, SCCM Run Script deployments may remain stuck at “Creating Client Jobs”, and scripts will fail to reach the endpoints.

How to Check SQL Service Broker Status

Run the below SQL query on the SCCM database server:

SELECT name, is_broker_enabled
FROM sys.databases
WHERE name = 'CM_<SiteCode>'

Example:

SELECT name, is_broker_enabled
FROM sys.databases
WHERE name = 'CM_PS1'

Expected Result:

is_broker_enabled = 1

1 = SQL Service Broker Enabled
0 = SQL Service Broker Disabled

Resolution

Enable SQL Service Broker using the below command:

ALTER DATABASE CM_<SiteCode> SET ENABLE_BROKER WITH ROLLBACK IMMEDIATE;