• GreeNRG@slrpnk.net
    link
    fedilink
    English
    arrow-up
    220
    arrow-down
    2
    ·
    edit-2
    8 days ago

    Since rolling back to the previous configuration will present a challenge, affected users will be faced with finding out just how effective their backup strategy is or paying for the required license and dealing with all the changes that come with Windows Server 2025.

    Accidentally force your customers to have to spend money to upgrade, how convenient.

    • Dremor@lemmy.world
      link
      fedilink
      English
      arrow-up
      159
      ·
      8 days ago

      Congratulation, you are being upgraded. Please do not resist. And pay while we are at it.

    • Maestro@fedia.io
      link
      fedilink
      arrow-up
      69
      arrow-down
      3
      ·
      8 days ago

      Since MS forced the upgrade, you should get 2025 for free. That would probably be really easy to argue in court

      • boonhet@lemm.ee
        link
        fedilink
        English
        arrow-up
        67
        arrow-down
        10
        ·
        8 days ago

        Ah, but did you read the article?

        MS didn’t force it, Heimdal auto-updated it for their customers based on the assumption that Microsoft would label the update properly instead of it being labeled as a regular security patch. Microsoft however made a mistake (on purpose or not? Who knows…) in labeling it.

        • MaggiWuerze@feddit.org
          link
          fedilink
          English
          arrow-up
          75
          ·
          8 days ago

          Then it’s still on Microsoft for pushing that update through what is essentially a patch pipeline

          • boonhet@lemm.ee
            link
            fedilink
            English
            arrow-up
            6
            arrow-down
            26
            ·
            8 days ago

            It is, but they never forced anyone to take the update, so that might save their asses, or it might not

            • WhatAmLemmy@lemmy.world
              link
              fedilink
              English
              arrow-up
              39
              arrow-down
              2
              ·
              8 days ago

              This would be no different to you ordering food in a restaurant, them bringing you the wrong meal, you refusing because you didn’t order it, then they tell you to go fuck yourself and charge you for it anyway.

              If this argument is valid in your judicial system then you live in a clown world capitalist dictatorship.

              • Maestro@fedia.io
                link
                fedilink
                arrow-up
                30
                arrow-down
                2
                ·
                8 days ago

                Have you seen the state of the US? A “clown world capitalist dictatorship” is a pretty apt description

              • boonhet@lemm.ee
                link
                fedilink
                English
                arrow-up
                6
                ·
                8 days ago

                I’m saying they might send people the bill and then these people (well, companies) are going to have to fight it in court, where they’ll be right for sure, but Microsoft can make a lot of stupid arguments to prolong the whole thing, to the point where it’s cheaper to pay the license fee. For one they could say that continued use of the operating system constitutes agreement to licenses and pricing.

                Either way this is server 2025 not windows 12. We’re talking about companies here, not people.

            • NeoNachtwaechter@lemmy.world
              link
              fedilink
              English
              arrow-up
              9
              arrow-down
              1
              ·
              edit-2
              8 days ago

              M$'s mistake creates no obligation to pay, either way. They cannot sue anyone for the extra money.

              But some customers (depending on their legislation) might sue M$ to make broken systems running again, for example if these systems have stopped now with a ‘missing license’ error message.

  • MonkderVierte@lemmy.ml
    link
    fedilink
    English
    arrow-up
    79
    arrow-down
    5
    ·
    8 days ago

    Misleading title. It was installed by a third-party updater, Heimdall, but MS labeled a Windows 11 update wrong.

      • ditty@lemm.ee
        link
        fedilink
        English
        arrow-up
        25
        arrow-down
        1
        ·
        8 days ago

        Yet another reason to not do auto-updates in an enterprise environment for mission-critical services.

        • superkret@feddit.orgOP
          link
          fedilink
          English
          arrow-up
          23
          ·
          8 days ago

          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.

            • mosiacmango@lemm.ee
              link
              fedilink
              English
              arrow-up
              5
              ·
              edit-2
              7 days 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.

            • SomeGuy69@lemmy.world
              link
              fedilink
              English
              arrow-up
              4
              ·
              7 days ago

              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.

  • Kokesh@lemmy.world
    link
    fedilink
    English
    arrow-up
    43
    arrow-down
    1
    ·
    8 days ago

    It must have been the same fun as when back in 2012 (or 2013?) McAfee (at least I think it was them) identified /system32 as a threat and deleted it :)

  • Aceticon@lemmy.world
    link
    fedilink
    English
    arrow-up
    30
    arrow-down
    1
    ·
    7 days ago

    I’m truly, totally, completely shocked … that Windows is still being used on the server side.

    • Hobo@lemmy.world
      link
      fedilink
      English
      arrow-up
      10
      ·
      7 days ago

      A bunch of enterprise services are Windows only. Also Active Directory is by far the best and easiest way to manage users and computers in an org filled with a bunch of end users on Windows desktops. Not to mention the metric shitload of legacy internal asp applications…

  • DirkMcCallahan@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    7 days ago

    I know this has nothing to do with my home computer, but this just further affirms my decision to switch to Linux earlier this year.