SC Task Sequences being stuck in „Installing“

Wie können wir helfen?

SC Task Sequences being stuck in „Installing“

Aktualisiert
Du bist hier:
< Alle Themen

1.) Are you seeing task sequences enter invalid states? For example, where State = „Completed“ but CompletionState = „Failure“:

gwmi -Namespace root\ccm\SoftMgmtAgent -Class CCM_TSExecutionRequest -Filter "State = 'Completed' And CompletionState = 'Failure'"

This can help clear them out if so:

$c=(gwmi -Namespace root\ccm\SoftMgmtAgent -Class CCM_TSExecutionRequest -Filter "State = 'Completed' And CompletionState = 'Failure'"); if ($c) {$c.Delete(); Restart-Service ccmexec -force}

This was one of the main reasons behind stuck „installing“ task sequences for us.

2.) I’ve seen something similar on TSes that error out without truly exiting. Only solution I found, even after a ticket to MS, was to run these commands as admin.

  1. net stop winmgmt /y
  2. winmgmt /resetrepository
  3. reboot PC
  4. c:\windows\ccm\ccmrepair.exe

3.) other solution:

2019.12.24 – Help Reset TS’s that are having issues starting. „Stuck at Installing…“

    if (Get-WmiObject -Namespace Root\CCM\SoftMgmtAgent -Class CCM_TSExecutionRequest)
        {
        Write-output "Removing TS Excustion Request from WMI"
        Get-WmiObject -Namespace Root\CCM\SoftMgmtAgent -Class CCM_TSExecutionRequest | Remove-WmiObject
        Get-CimInstance -Namespace root/ccm -ClassName SMS_MaintenanceTaskRequests | Remove-CimInstance
        Set-Service smstsmgr -StartupType manual
        Start-Service smstsmgr
        Start-Sleep -Seconds 5
        if ((Get-Process CcmExec -ea SilentlyContinue) -ne $Null) {Get-Process CcmExec | Stop-Process -Force}
        if ((Get-Process TSManager -ea SilentlyContinue) -ne $Null) {Get-Process TSManager| Stop-Process -Force}
        Start-Sleep -Seconds 5
        Start-Service ccmexec
        Start-Sleep -Seconds 5
        Start-Service smstsmgr
        restart-service ccmexec -force -ErrorAction SilentlyContinue
        Start-Process -FilePath C:\windows\ccm\CcmEval.exe
        start-sleep -Seconds 15
        #Invoke Machine Policy
        Invoke-WMIMethod -Namespace root\ccm -Class SMS_CLIENT -Name TriggerSchedule "{00000000-0000-0000-0000-000000000021}" |Out-Null
        Invoke-WMIMethod -Namespace root\ccm -Class SMS_CLIENT -Name TriggerSchedule "{00000000-0000-0000-0000-000000000022}" |Out-Null

        }
    Else {Write-output "No TS Excustion Request in WMI"}

Inhaltsverzeichnis