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

      We have an app running on CentOS 6. The vendor of the app informed us they expect to have a new version that can run on RHEL 8 by the end of the year - 2025.

  • MonkderVierte@lemmy.ml
    link
    fedilink
    English
    arrow-up
    60
    arrow-down
    4
    ·
    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
        19
        arrow-down
        2
        ·
        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
          21
          ·
          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
              6
              ·
              edit-2
              8 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
              7
              arrow-down
              1
              ·
              8 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.

  • Aceticon@lemmy.world
    link
    fedilink
    English
    arrow-up
    59
    arrow-down
    4
    ·
    8 days ago

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

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

      Basically AD and the workstation management that uses it. Could all be run on a VM and snapshotted because you know it’s going to fuck up an update eventually. Perhaps SQL Server but that’s getting harder to justify the expense of anymore.

    • Hobo@lemmy.world
      link
      fedilink
      English
      arrow-up
      44
      arrow-down
      1
      ·
      8 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…

    • uniquethrowagay@feddit.org
      link
      fedilink
      English
      arrow-up
      6
      ·
      7 days ago

      We run a lot of Windows servers for specialized applications that don’t really have viable alternatives. It sucks, but it’s the same reason we use Windows clients.

  • Kokesh@lemmy.world
    link
    fedilink
    English
    arrow-up
    28
    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 :)

    • funkajunk@lemm.ee
      link
      fedilink
      English
      arrow-up
      28
      arrow-down
      2
      ·
      8 days ago

      One of the few things that accursed software actually got right!

  • DirkMcCallahan@lemmy.world
    link
    fedilink
    English
    arrow-up
    24
    arrow-down
    1
    ·
    8 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.

  • Buttflapper@lemmy.world
    link
    fedilink
    English
    arrow-up
    28
    arrow-down
    6
    ·
    8 days 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
      41
      arrow-down
      1
      ·
      8 days 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.

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

        I’m not necessarily talking about being in the server room, I’m talking about more like doing power shell stuff and the stuff you would think system administrators do. They are still teaching active directory in IT classes in college

    • Passerby6497@lemmy.world
      link
      fedilink
      English
      arrow-up
      9
      ·
      8 days 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
        21
        ·
        8 days ago

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

        • Lettuce eat lettuce@lemmy.ml
          link
          fedilink
          English
          arrow-up
          7
          ·
          8 days ago

          I worked for a classic MSP a while back, barely lasted 3 months. Such a toxic environment, tons of pressure to spread yourself thinner and thinner.

          It was one of those places where you were expected to be there an hour early, stay an hour late, and work through your lunch.

          Even though that’s illegal, it was never explicit, just one of those, wink wink type things. But the workload was always so heavy, you couldn’t stay on top of everything unless you were working 50+ hours a week.

          And of course, all salary, no overtime or double time for weekend work.

          I do internal IT now, much better. Trying to get my own one-person shop going to eventually be fully self-employed. Actually, it would be really cool to become a worker-owned co-op, but that’s still a faint dream.

          • DokPsy@lemmy.world
            link
            fedilink
            English
            arrow-up
            3
            ·
            8 days ago

            Currently in an MSP. It’s all on the company culture as to if it’s shit or not. We’re fully wfh with no plans to move back to the office.

            Overtime is never forced. If we have to work through lunch because all hell is breaking loose, we’re practically encouraged to leave an hour early unless the CEO is allowing ot and we want it. No pressure either direction.

            If users are rude or generally hard to deal with, manager has our back in dealing with them.

            Pay isn’t top dollar but there’s trade-offs

          • Trainguyrom@reddthat.com
            link
            fedilink
            English
            arrow-up
            2
            ·
            edit-2
            7 days ago

            I just accepted a job with a small MSP starting early next year. I kept a close ear out during the interview for signs of the classic MSP hell stuff that would chew through techs but it does look like I got a good one (small 8 or so man shop) but check in in about 3 months and we’ll see how I’m feeling haha

            My longer term plan is to use this as a stepping stone to then move onto being in-house then figuring out my exit strategy before burnout takes me, which I’m thinking I’ll either be aiming to move into IT management or possibly moving into a business analytics or cloud administration type role. Technical sales probably wouldn’t be too bad either.

        • Passerby6497@lemmy.world
          link
          fedilink
          English
          arrow-up
          6
          ·
          edit-2
          8 days 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
            8
            ·
            edit-2
            8 days 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.

  • CriticalMiss@lemmy.world
    link
    fedilink
    English
    arrow-up
    18
    arrow-down
    6
    ·
    7 days ago

    Hate to be that guy but if you automatically patch critical infrastructure or apply patches without reading their description first, you kinda did it to yourself. There’s a very good reason not a single Linux distribution patches itself (by default) and wants you to read and understand the packages you’re updating and their potential effects on your system

    • festus@lemmy.ca
      link
      fedilink
      English
      arrow-up
      10
      ·
      7 days ago

      Many distros (at least Ubuntu) auto-installs security updates, and here a mislabeled “security update” was auto-installed. This is not the fault of the sysadmins.