question

ThomasFaherty-0316 avatar image
0 Votes"
ThomasFaherty-0316 asked Amandayou-MSFT commented

SCCM Scripts get stuck on creating client job

Hello,

I am having an issue where script suddenly just started getting stuck on creating client job. In reporting it shows they ran but checking on the machine I can tell no changes were made.

Site health checks good.

Clients are checking in fine so no problem there.

The logs I have attached seem clean.

Checked IIS to make sure certs were still there and not expired.

Ran Wireshark to make sure the Palo Alto wasn't blocking it. Didn't see anything.

Running out of ideas. I am hoping someone can point me in the right direction.

134836-bgbserver.log


mem-cm-general
bgbserver.log (2.5 MiB)
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.

Amandayou-MSFT avatar image
1 Vote"
Amandayou-MSFT answered Amandayou-MSFT commented

Hi @ThomasFaherty-0316,

We could check Scripts.log on the side of client to see if any error in it, it records the activity of when Configuration Manager scripts run on the client.

And on the side of site server, we could check SMS_MESSAGE_PROCESSING_ENGINE.log, which the site uses to process results for client actions. For example, run scripts and CMPivot.

Besides, could we know that scripts don't work on all client? If so, it seems that something wrong with the script, if not, it may be related with some issued clients.



If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


· 2
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.

Looks like you were right. I assigned a service desk guy to test the script. Should have been simple, run it, did it work? He told me it did but when I went back and tested it did not. I also realized the script I was trying to use wasn't going to work for us anyway. Funny thing is it was still getting stuck on creating jobs, but reporting it ran successfully if I just left and looked at the report even though it never moved. Not sure why it was getting stuck but I went back the next day and it was just working right again. Thank you for your help.

0 Votes 0 ·
Amandayou-MSFT avatar image Amandayou-MSFT ThomasFaherty-0316 ·

Hi,

Thanks for your update.

If you have any other issues, please don't hesitate to let us know.

Thanks and have a nice day.

Best regards,
Amanda

0 Votes 0 ·
Jason-MSFT avatar image
0 Votes"
Jason-MSFT answered

Also, what version of ConfigMgr is running on the site and client?

ANd, does your script have parameters in 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.

ThomasFaherty-0316 avatar image
0 Votes"
ThomasFaherty-0316 answered

Hey guys, thanks for jumping in here.

I actually tried a few scripts. The new one is to disable hardware acceleration in Teams. However, my tried and true scripts that have been around a while don't run either. Increase client cache size, gpupdate, and client check in. None of them will get past creating client job.

Oddly the logs look clean, even like the scripts ran, but I am not seeing any results.

135087-sms-message-processing-engine.log

135103-scripts.log

My CfgMgr version is 2010

The main machine I am testing on is running client version 5.00.9040.1044

As for the script I primarily want to run, it looks like this:

$configPath = "$env:APPDATA\Microsoft\Teams\desktop-config.json"
$FileExists = Test-Path $configPath


if ($FileExists -eq $true) {


 $a = Get-Content $configPath | ConvertFrom-Json
 
 if ($a.appPreferenceSettings -match "disableGpu") {
     $a.appPreferenceSettings.disableGpu = $true
 } else {
     $a.appPreferenceSettings | Add-Member -Name "disableGpu" -MemberType NoteProperty -Value $true
 }
 
 $a | ConvertTo-Json | Set-Content $configPath

}





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.

ThomasFaherty-0316 avatar image
0 Votes"
ThomasFaherty-0316 answered Amandayou-MSFT commented

Well, I can see with testing that script wasn't going to work. I wrote it up and sent it over to a service desk guy who told me it worked great, but I don't see how that is possible.

I am going to retest with a different script. It's possible things are fine and I was mislead to believe that a script that doesn't work had.

· 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,

Thanks for your update. After testing the script works, we could deploy it to client by sccm. And I am looking forward to solving the problem.

Have a nice day!

Best regards,
Amanda

0 Votes 0 ·