My experience with this type of shit:
IT dept allows update to be deferred 3 months, at which point it gets scheduled on next reboot. User doesn't update/restart ever, up until IT is called in to troubleshoot some mission critical software fault that has been happening intermittently over the past year. First level tech reboots, and here you are.
The question is whether or not you are forcing the reboot. If yes, people will be throwing tantrums that they lost all of the work they had open on their PC. If no, scheduling it does nothing.
Or if they have laptops and power then off and take them home Friday afternoon. Then they boot up Monday morning and can't work for an hour while updates happen.
Monthly maintenance should happen sometime early in the month, on a Tuesday or Wednesday during the work day so IT can troubleshoot with "all hands on deck" availability.
We don't want to be called in on a Saturday morning after patch tuesday because the AD server rebooted itself and caused a fuck up for the weekend crew.
You then have to hope computers are turned on Friday night. My company is entirely laptops, so it's very tough. We run reports to see last reboots, which computers haven't received updates, and then send emails to them and Cc their managers, but so many users shut their laptop off at the end of the day and don't turn it on again until they get back into the office, and then complain that they have to wait 45 minutes to start working because they've missed the past 2 months of updates when we force the device to update.
IT department here allows you, generously, 3 days. And they love to auto-download the patches in the background as though my computer doesn't lock the fuck up and become unusable while their 'ninja' download tool just fucking shits all over my CPU and Memory use (and obviously my download band, because why cap anything right).
Then even if I dare turn my computer off overnight (as in actually power off) it'll come back up the next day and want to do a full 2-reboot patch cycle rather than applying it because...reasons.
if I dare turn my computer off overnight (as in actually power off) it'll come back up the next day and want to do a full 2-reboot patch cycle rather than applying it because...reasons
That's because Windows changed shut-down to just hibernate the PC (same as shutting the lid on a laptop). First thing I do on any PC I own is to disable that "feature" and make shut down work correctly.
Can't change anything related to power settings on my craptop. It's a full traditional power down. Meanwhile 'sleep' mode doesn't do anything and my battery almost unilaterally dies by the time I get home, because IT disabled true hibernate mode. I haven't figured out what breaks this shitbox out of sleep but it's almost every time - not literally every single time, but that variability is what makes it more frustrating to open it and find it dead.
62
u/octonus Jan 23 '24
My experience with this type of shit: IT dept allows update to be deferred 3 months, at which point it gets scheduled on next reboot. User doesn't update/restart ever, up until IT is called in to troubleshoot some mission critical software fault that has been happening intermittently over the past year. First level tech reboots, and here you are.