I love how this doesn’t even begin to cover bad kbs ms pushed out. The fact that windows admins think testing updates before deploying them is a routine operation that should always be done boggles my mind.
The third party software did exactly what it was designed to do:
Push security updates automatically, while holding back feature updates for testing.
This is standard operating procedure. Security updates are not supposed to change anything about how a server works, so the risk of breakage is very low.
And they need to be installed as fast as possible, to patch holes that are now known to every attacker.
Microsoft were the ones who pushed out a new Server OS installation and labelled it as security update.
I still remember the update that sent domain controllers into a bootloop.
That was fun!
And the one that bluescreened all Windows servers.
No, the other one!
Oh, and the one that did an in-place-upgrade by itself, then locked your server cause it wasn’t licensed for the new OS version.
I love how this doesn’t even begin to cover bad kbs ms pushed out. The fact that windows admins think testing updates before deploying them is a routine operation that should always be done boggles my mind.
If we can generate energy from outrage, /r/sysadmin could’ve powered the whole planet multiple times in the last 6-8 years.
They’re doing it on purpose, they’re using sysadmins for electricity for AI obviously
deleted by creator
The third party software did exactly what it was designed to do:
Push security updates automatically, while holding back feature updates for testing.
This is standard operating procedure. Security updates are not supposed to change anything about how a server works, so the risk of breakage is very low.
And they need to be installed as fast as possible, to patch holes that are now known to every attacker.
Microsoft were the ones who pushed out a new Server OS installation and labelled it as security update.