• Buttflapper@lemmy.world
    link
    fedilink
    English
    arrow-up
    29
    arrow-down
    4
    ·
    7 hours ago

    Do system administrators still exist? Honest question. I was one of those years ago and layoffs, forced back to office bullshit drove me away

    • superkret@feddit.orgOP
      link
      fedilink
      English
      arrow-up
      34
      ·
      6 hours ago

      yes, but we spend most of our time in meetings with cloud service vendors now.
      I haven’t been inside the server room for a month.

    • Passerby6497@lemmy.world
      link
      fedilink
      English
      arrow-up
      10
      ·
      6 hours ago

      There are dozens of us (working for MSPs because in house doesn’t pay as well and companies are cheap and want to outsource that cost center)!

      • superkret@feddit.orgOP
        link
        fedilink
        English
        arrow-up
        16
        ·
        6 hours ago

        I switched from an MSP to a unionized in-house position, doubled my salary and my days of paid time off.

        • Passerby6497@lemmy.world
          link
          fedilink
          English
          arrow-up
          4
          ·
          edit-2
          5 hours ago

          Nice! I’ve job hopped a few times and tripped my salary in 5 years and am at a unicorn msp with unlimited PTO and management that cares about employees.

          I wish I could find a union IT shop, but nothing around that I’ve seen available. Happy to hear my first statement isn’t as universal as my experience suggests!

          • superkret@feddit.orgOP
            link
            fedilink
            English
            arrow-up
            5
            ·
            edit-2
            1 hour ago

            “Unlimited PTO” is a meaningless term, and a trap.
            I have 42 days of PTO per year, plus 13 state holidays.
            I have a right to take those days off, they can’t be denied by anyone.
            And if I don’t take them, my team lead will have a talk with me in October at the latest, because the company would get in legal trouble if I didn’t get them.

            With “unlimited PTO” you have no such right to any amount of PTO.
            Sure, you could try to schedule lots of PTO, but it can just be denied (“not possible right now”), or if you take too many, you’re just fired.

            • Johnny5@lemm.ee
              link
              fedilink
              English
              arrow-up
              2
              ·
              31 minutes ago

              Plus they don’t have to book the liability on the balance sheet!

    • Baggie
      link
      fedilink
      English
      arrow-up
      4
      ·
      7 hours ago

      Idk dude, I got a redundancy about a year ago. There are still jobs out there but it feels like it’s dwindling.

  • MonkderVierte@lemmy.ml
    link
    fedilink
    English
    arrow-up
    62
    ·
    9 hours 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
        15
        ·
        5 hours 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
          9
          ·
          5 hours 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.

  • GreeNRG@slrpnk.net
    link
    fedilink
    English
    arrow-up
    193
    arrow-down
    2
    ·
    edit-2
    11 hours 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
      135
      ·
      11 hours ago

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

    • Maestro@fedia.io
      link
      fedilink
      arrow-up
      60
      arrow-down
      3
      ·
      10 hours 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
        59
        arrow-down
        8
        ·
        10 hours 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
          58
          ·
          9 hours 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
            5
            arrow-down
            19
            ·
            9 hours 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
              25
              arrow-down
              2
              ·
              8 hours 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
                22
                arrow-down
                2
                ·
                8 hours 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 hours 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
              4
              arrow-down
              1
              ·
              edit-2
              8 hours 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.

  • Kokesh@lemmy.world
    link
    fedilink
    English
    arrow-up
    35
    arrow-down
    1
    ·
    10 hours 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 :)