Check ccmexec service health to avoid stuck SCCM agent based on long sleep/hibernate usage
Issue:
SCCM clients get stuck after a while when devices use only sleep/hibernate mode instead of restart. The ccmexec service still show running but logs are not updated anymore and not reporting at all. Only killing service and restart solve the problem. Two times showed during MS cases.
Idea: Improve Client health to check for instance once per day the health of ccmexec service and logs timestamp and restart service if required.
Michael Krueger
shared this idea
3 comments
-
92d4-ad940dc7a333
commented
This needs to be fixed. Having to resort to a third party script to keep the client alive and doing what it is is supposed to do is absurd.
-
bdam
commented
Yes please, doubly so on servers that just don't reboot for weeks at a time by their very design. The agent will have the lights on (service shows running) but clearly no one's home (no log action, none of the scheduled actions kick off).
-
Koenraad Rens
commented
I also encountered several problems which were fixed by rebooting the sms agent host service.
Let ccmeval restart the service when it hasn't restarted in X days. This would also fix issues that aren't explicitly detected with ccmeval.