Good morning, We have been working extremely hard getting our patch compliance numbers up. We recently, for the first time, hit over 90% compliance for last month.
A question came up recently about scheduling reboots on servers. I decided to run a last reboot / uptime report against all servers in the environment. I found a good handful of servers that had not removed since August. And several servers that has not removed since last month. One suggestion brought the table was to schedule an automated refill for the servers to help increase our paths one effort. Management is telling me they see no reason to schedule reboot as long as patching work. I am looking to justify this need. I’d be interested to hear what other folks would suggest would be legitimate reasons for scheduled reboots. Basically they are saying SCCM how do you must not be working if servers aren’t getting rebooted. I have, for example, found some servers don’t receive patches if there are disconnected user logged into the server. By bouncing the server, I was able to deploy patches no problem. Any other use cases samples to support this would be extremely helpful. I appreciate any help or suggestions with this. Thanks! Brian Sent from my iPhone
