Jaymon wrote: ↑Thu May 02, 2019 3:28 pmits not out of bounds, they should be giving you a grace period. critical patch available, you have 24 hours to install this patch which will require a rebootSkinypupy wrote: ↑Thu May 02, 2019 9:00 am Turned my work laptop on at 6:05 this morning, and it finally finished doing the major update (the one that requires 30 minutes, 4 restarts, and a partridge in a pear tree) at 6:32...when I had a webinar demo that started at 6:30. This is now the second time in a month that has happened.
I know nothing about IT, so I'll ask the smart folks here. Is it completely out of bounds to ask IT to give us a little heads-up when these sort of major updates are going happen? Something like a quick note that says "Hey, give yourself a little extra time next time you boot up?"
I don't know what is in and out of bounds but our WSUS works for crap, so I update by audit in the flesh when I run updates I advise that they can work as normal and need to restart (not shut down and turn but restart) at lunch. Count on the process taking upwards of 30 minutes and call me if you have problems.
I plan to audit our SHA-2 patching for my remaining 7 machines next week. Not looking forward to that.
2nd time in a month for desktop is odd. Windows 10 gets the two big rollouts a year. The monthly patches are a little pain, but not 1/2 hour every month pain.
Also, I can't speak to how your group policy is controlled but I'd think if they aren't watching the patching, then you should be able to reboot at your leisure. If Windows 10 ever asks you to reboot, always wait until your downtime if it is an option.