Configuration Manager (SCCM) Clients not updating their status

Question

I have issues where the configuration manager CAS server is showing the clients as "Pending System Restart". When you look at the client it's referring to, it shows the status as having been sent, and no status of restarting pending is shown in the registry (client was restarted anyway).

Re-running the summarization and refreshing has not worked over a period of hours.

enter image description here

The client log (server1) files below: enter image description here

Is there any way to clear the client status on the CAS server, and is there a fault with the Management Points in not passing on the status messages?

Unfortunately not, restarting the agent service or the client didn't help. — Mark, May 21 '14 at 23:03
@BigHomie Have you resolved this before? I'm seeing basically the same thing occur here. — alx9r, Aug 19 '15 at 21:21
@ALX9R Sorry I didn't check this sooner, will add a script that fixes it. — Mark, Sep 10 '15 at 13:55

Mark · Accepted Answer · 2015-09-10T22:31:27.827

2

Found a script that does fix the issue most of the time. This was buried in the SCCM 2012 unleashed book.

Copy this to .vbs, run it on the client machine having issues. Then restart the sms service and re-run your cycle (software update, etc).

That should force it to recheck it's check state.

' Initialize the UpdatesStore variable.
dim newCCMUpdatesStore
' Create the COM object.
set newCCMUpdatesStore = CreateObject ("Microsoft.CCM.UpdatesStore")
' Refresh the server compliance state by running the RefreshServerComplianceState method.
newCCMUpdatesStore.RefreshServerComplianceState
' Output success message.
wscript.echo "Ran RefreshServerComplianceState."

edited Sep 10 '15 at 22:31

answered Sep 10 '15 at 13:59

Mark

93
1
1
7

No problems. It's an older script but you'll be amazed at how well it fixes stuck clients. – Mark Sep 10 '15 at 14:03
Just to be clear. Do you run this on the client? – alx9r Sep 10 '15 at 14:07
Correct, run on the client. Will update the answer. – Mark Sep 10 '15 at 22:31

score 2 · Answer 2 · answered Mar 18 '19 at 14:00

2

To build on Mark's answer, you can this:

Invoke-Command -ComputerName $ComputerName -AsJob {(New-Object -ComObject Microsoft.CCM.UpdatesStore).RefreshServerComplianceState()}

answered Mar 18 '19 at 14:00

CircaLucid

121
2

Configuration Manager (SCCM) Clients not updating their status

2 Answers2