571
Sysadmin shock as Windows Server 2025 installs itself (www.theregister.com)
submitted 2 years ago by to c/technology@lemmy.world
94 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 33 points 2 years ago (5 children)

When the OS becomes the virus

  • permalink
  • fedilink
  • source
  • hideshow 5 child comments
    •
  • [–] 7 points 2 years ago (4 children)

    When reading comprehension is limited to the title.
    MS mislabeled the update
    Heimdal (apparently a patchmanagement) auto-installed the falsely labeled update.

    If OP (this was reported by a Redditor on r/sysadmin) and their company is unable to properly set grace periods for windows updates I can't help them either.
    IMHO you are supposed to manually review and release updates either on a WSUS or the management interface of your patching solution.
    Not just "Hehe, auto install and see what happens".
    And if you do that shit, set a timeout for 14 days at least for uncritical rated updates.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 4 points 2 years ago (1 child)

    They said they believe it was a mislabeled update. MS didn't respond. Before criticizing others for their reading comprehension, I think you could work on yourself too.

    There is a world, and it may be ours, where MS purposefully pushes this out. As the end of the article makes clear, this will be only a minor issue for those with good backup (which they probably all should but they don't), but for those who don't they'll be stuck with the new version and have to pay for the license of it. This is a large benefit to MS while they also get to pretend like it's just a mistake and not having backups makes it your issue, not theirs.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •