question

SimonBerg-2911 avatar image
0 Votes"
SimonBerg-2911 asked SimonBerg-2911 commented

SCCM Push Notification - run script - client jobs slowing down and stalls

Hi

We are running scripts directly on devices via SCCM with the run script functionality.
But the SCCM is very slow pushing out to the clients and sometimes it cant.

It seams to me that there is some kind of bottleneck

We are running a simple script on 600 devices. We are doing it for each device with the "Invoke-CMScript" cmdlet which means the SCCM creates a job per device we are pushing a script to.
In the BgbServer.log i can see its starting the client jobs with 2-3 seconds between the devices until its started on the first 25 devices. then the time starts to extend to almost 2-3 minutes between the client jobs on the devices.
Some times it even don start any client jobs at all and i cant find any logging telling why it wont start any client jobs.
When we started doing this there was no bottleneck the first 3-5 days, then it started.

Does anyone have some troubleshooting inputs for this?
We would really like to use the SCCM for pushing and executing scripts via the run script functionality.

Best Regards
Simon

windows-server-powershell
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

LimitlessTechnology-2700 avatar image
0 Votes"
LimitlessTechnology-2700 answered LimitlessTechnology-2700 published

Hello @SimonBerg-2911

If a script does not run or runs with lag, for example, because a target device is turned off during the one-hour time period, you must run it again.

If the problem still persists, then move to the next step

After you have initiated running a script on a collection of devices, use the following procedure to monitor the operation. You are able to monitor a script in real-time as it executes, and later return to the status and results for a given Run Script execution.

  1. In the Configuration Manager console, click Monitoring.

  2. In the Monitoring workspace, click Script Status.

  3. In the Script Status list, you view the results for each script you ran on client devices. A script exit code of 0 generally indicates that the script ran successfully.

This will give you a detailed idea about, what actually creating lag with the process.

Hope this answers all your queries, if not please do repost back.
If an Answer is helpful, please click "Accept Answer" and upvote it : )

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

LimitlessTechnology-2700 avatar image
0 Votes"
LimitlessTechnology-2700 answered LimitlessTechnology-2700 published

Hello @SimonBerg-2911

If a script does not run or runs with lag, for example, because a target device is turned off during the one-hour time period, you must run it again.

If the problem still persists, then move to the next step

After you have initiated running a script on a collection of devices, use the following procedure to monitor the operation. You are able to monitor a script in real-time as it executes, and later return to the status and results for a given Run Script execution.

  1. In the Configuration Manager console, click Monitoring.

  2. In the Monitoring workspace, click Script Status.

  3. In the Script Status list, you view the results for each script you ran on client devices. A script exit code of 0 generally indicates that the script ran successfully.

This will give you a detailed idea about, what actually creating lag with the process.

Hope this answers all your queries, if not please do repost back.
If an Answer is helpful, please click "Accept Answer" and upvote it : )

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

LimitlessTechnology-2700 avatar image
0 Votes"
LimitlessTechnology-2700 answered SimonBerg-2911 commented

Hello @SimonBerg-2911

If a script does not run or runs with lag, for example, because a target device is turned off during the one-hour time period, you must run it again.

If the problem still persists, then move to the next step

After you have initiated running a script on a collection of devices, use the following procedure to monitor the operation. You are able to monitor a script in real-time as it executes, and later return to the status and results for a given Run Script execution.

  1. In the Configuration Manager console, click Monitoring.

  2. In the Monitoring workspace, click Script Status.

  3. In the Script Status list, you view the results for each script you ran on client devices. A script exit code of 0 generally indicates that the script ran successfully.

This will give you a detailed idea about, what actually creating lag with the process.

Hope this answers all your queries, if not please do repost back.
If an Answer is helpful, please click "Accept Answer" and upvote it : )

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi

The issue is that the push execution graduatly slowing down and stalls in a sploradic behavior.
Eg. yesterday i ran a simple script on 585 devices, and after 4 hours all clients had returned the result.
Today we are running the same script on the same clients at the same time of day and after 4 hours it only received results from 193 clients.....

So the SCCM is starting to "stall" or throttle the workflow.

0 Votes 0 ·