I'm curious how everyone handles system reboots in their environments. Do you have policies in place to enforce reboots after certain uptime periods? How do you approach preventing systems from running for too long without a restart?
5 Answers
At my previous job, we would remind users who reached a month of uptime every day at 5 PM. They could decline, but if they were facing issues, it encouraged them to reboot before calling IT for help.
Honestly, if everything's working fine, I tend to stick with the "if it ain't broke, don't fix it" mentality. Regular updates usually prompt reboots anyhow, so that keeps the systems refreshed without me having to interfere too much.
I do quarterly reboots on my work laptop and haven’t had any issues!
We use a tool to schedule nightly reboots for critical desktops. It keeps things running smoothly without causing interruptions during work hours.
That sounds great! I’ll have to see if my RMM can support that feature too.
I make sure none of my servers go longer than 30 days without a reboot, mainly because of Windows patching. Regular updates mean regular restarts in my experience.
Absolutely. Most organizations I know schedule monthly patches, so reboots happen pretty consistently just from that.
In my setup, we do weekly reboots unless we have a good reason not to. Keeps everything running well and minimizes random support requests from users.
Exactly, we’ve got about 90% compliance with those weekly reboots for end user devices, which really helps reduce downtime.
I used to work in support where we struggled with many clients not patching. Turns out, the majority of those issues were fixed just by rebooting. We even discussed adding a feature to remind users to reboot before patching to reduce support tickets.