▲ 571 ▼ Sysadmin shock as Windows Server 2025 installs itself (www.theregister.com) submitted 2 years ago by superkret@feddit.org to c/technology@lemmy.world 94 comments fedilink hide all child comments
[–] superkret@feddit.org [S] 119 points 2 years ago (7 children) They labelled an OS version upgrade as a security update. permalink fedilink source parent hideshow 7 child comments replies: [–] dditty@lemm.ee 27 points 2 years ago (5 children) Yet another reason to not do auto-updates in an enterprise environment for mission-critical services. permalink fedilink source parent hideshow 5 child comments replies: [–] superkret@feddit.org [S] 41 points 2 years ago (4 children) In an enterprise environment, you rely on a service that tracks CVEs, analyzes which ones apply to your environment, and prioritizes security critical updates. The issue here is that one of these services installed a release upgrade because Microsoft mislabelled it as security update. permalink fedilink source parent hideshow 4 child comments replies: [–] NocturnalEngineer@lemmy.world 12 points 2 years ago (3 children) Should still be doing phased rollouts of any patches, and where possible, implementing them on pre-prod first. permalink fedilink source parent hideshow 3 child comments replies: [–] mosiacmango@lemm.ee 11 points 2 years ago* Pre-prod is ideal, but a pipe dream for many. Lots of folks barely get prod. We still stagger patching so things like this only wipe some of the critical infrastructure, but that still causes needless issues. permalink fedilink source parent [–] SomeGuy69@lemmy.world 11 points 2 years ago (1 child) For security updates in critical infrastructure, no. You want that right away, in best case instant. You can't risk a zero day being used to kill people. permalink fedilink source parent hideshow 1 child comment replies: [–] Appoxo@lemmy.dbzer0.com 0 points 2 years ago* (last edited 2 years ago) Even security updates can be uncritical or supercritical. Consult the patch notes or get burned lol permalink fedilink source parent [–] realcaseyrollins 1 point 2 years ago To be fair, it is a security upgrade permalink fedilink source parent
[–] dditty@lemm.ee 27 points 2 years ago (5 children) Yet another reason to not do auto-updates in an enterprise environment for mission-critical services. permalink fedilink source parent hideshow 5 child comments replies: [–] superkret@feddit.org [S] 41 points 2 years ago (4 children) In an enterprise environment, you rely on a service that tracks CVEs, analyzes which ones apply to your environment, and prioritizes security critical updates. The issue here is that one of these services installed a release upgrade because Microsoft mislabelled it as security update. permalink fedilink source parent hideshow 4 child comments replies: [–] NocturnalEngineer@lemmy.world 12 points 2 years ago (3 children) Should still be doing phased rollouts of any patches, and where possible, implementing them on pre-prod first. permalink fedilink source parent hideshow 3 child comments replies: [–] mosiacmango@lemm.ee 11 points 2 years ago* Pre-prod is ideal, but a pipe dream for many. Lots of folks barely get prod. We still stagger patching so things like this only wipe some of the critical infrastructure, but that still causes needless issues. permalink fedilink source parent [–] SomeGuy69@lemmy.world 11 points 2 years ago (1 child) For security updates in critical infrastructure, no. You want that right away, in best case instant. You can't risk a zero day being used to kill people. permalink fedilink source parent hideshow 1 child comment replies: [–] Appoxo@lemmy.dbzer0.com 0 points 2 years ago* (last edited 2 years ago) Even security updates can be uncritical or supercritical. Consult the patch notes or get burned lol permalink fedilink source parent
[–] superkret@feddit.org [S] 41 points 2 years ago (4 children) In an enterprise environment, you rely on a service that tracks CVEs, analyzes which ones apply to your environment, and prioritizes security critical updates. The issue here is that one of these services installed a release upgrade because Microsoft mislabelled it as security update. permalink fedilink source parent hideshow 4 child comments replies: [–] NocturnalEngineer@lemmy.world 12 points 2 years ago (3 children) Should still be doing phased rollouts of any patches, and where possible, implementing them on pre-prod first. permalink fedilink source parent hideshow 3 child comments replies: [–] mosiacmango@lemm.ee 11 points 2 years ago* Pre-prod is ideal, but a pipe dream for many. Lots of folks barely get prod. We still stagger patching so things like this only wipe some of the critical infrastructure, but that still causes needless issues. permalink fedilink source parent [–] SomeGuy69@lemmy.world 11 points 2 years ago (1 child) For security updates in critical infrastructure, no. You want that right away, in best case instant. You can't risk a zero day being used to kill people. permalink fedilink source parent hideshow 1 child comment replies: [–] Appoxo@lemmy.dbzer0.com 0 points 2 years ago* (last edited 2 years ago) Even security updates can be uncritical or supercritical. Consult the patch notes or get burned lol permalink fedilink source parent
[–] NocturnalEngineer@lemmy.world 12 points 2 years ago (3 children) Should still be doing phased rollouts of any patches, and where possible, implementing them on pre-prod first. permalink fedilink source parent hideshow 3 child comments replies: [–] mosiacmango@lemm.ee 11 points 2 years ago* Pre-prod is ideal, but a pipe dream for many. Lots of folks barely get prod. We still stagger patching so things like this only wipe some of the critical infrastructure, but that still causes needless issues. permalink fedilink source parent [–] SomeGuy69@lemmy.world 11 points 2 years ago (1 child) For security updates in critical infrastructure, no. You want that right away, in best case instant. You can't risk a zero day being used to kill people. permalink fedilink source parent hideshow 1 child comment replies: [–] Appoxo@lemmy.dbzer0.com 0 points 2 years ago* (last edited 2 years ago) Even security updates can be uncritical or supercritical. Consult the patch notes or get burned lol permalink fedilink source parent
[–] mosiacmango@lemm.ee 11 points 2 years ago* Pre-prod is ideal, but a pipe dream for many. Lots of folks barely get prod. We still stagger patching so things like this only wipe some of the critical infrastructure, but that still causes needless issues. permalink fedilink source parent
[–] SomeGuy69@lemmy.world 11 points 2 years ago (1 child) For security updates in critical infrastructure, no. You want that right away, in best case instant. You can't risk a zero day being used to kill people. permalink fedilink source parent hideshow 1 child comment replies: [–] Appoxo@lemmy.dbzer0.com 0 points 2 years ago* (last edited 2 years ago) Even security updates can be uncritical or supercritical. Consult the patch notes or get burned lol permalink fedilink source parent
[–] Appoxo@lemmy.dbzer0.com 0 points 2 years ago* (last edited 2 years ago) Even security updates can be uncritical or supercritical. Consult the patch notes or get burned lol permalink fedilink source parent
[–] realcaseyrollins 1 point 2 years ago To be fair, it is a security upgrade permalink fedilink source parent