SCCM Scripts get stuck on creating client job

Thomas Faherty 151 Reputation points
2021-09-23T23:43:15.267+00:00

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

Microsoft Configuration Manager
0 comments
Accepted answer
  1. Amandayou-MSFT 11,046 Reputation points
    2021-09-24T02:45:32.587+00:00

    Hi @Thomas Faherty ,

    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.

    1 person found this answer helpful.

3 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jason Sandys 31,171 Reputation points Microsoft Employee
    2021-09-24T04:19:23.397+00:00

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

    ANd, does your script have parameters in it?

    0 comments
  2. Thomas Faherty 151 Reputation points
    2021-09-24T15:31:09.89+00:00

    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

    }

    0 comments
  3. Thomas Faherty 151 Reputation points
    2021-09-24T16:28:47.017+00:00

    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.