this post was submitted on 07 Nov 2024
570 points (98.1% liked)

Technology

59587 readers
2689 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
top 50 comments
sorted by: hot top controversial new old
[–] [email protected] 295 points 2 weeks ago* (last edited 2 weeks ago) (3 children)

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.

[–] [email protected] 203 points 2 weeks ago (2 children)

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

[–] [email protected] 80 points 2 weeks ago (1 children)

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

[–] [email protected] 69 points 2 weeks ago (1 children)

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.

[–] [email protected] 93 points 2 weeks ago (8 children)

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

[–] [email protected] 9 points 2 weeks ago

MS will be sued over this and they will lose. This is not an ambiguous case. They fucked up. It’s essentially an unconsentual/unilateral alteration to a contract, which kinda violates the principle of, you know, a contract.

load more comments (7 replies)
[–] [email protected] 10 points 2 weeks ago (1 children)

Uh, if they didn't ask for it, how is Microsoft going to make them pay for it?

[–] [email protected] 9 points 2 weeks ago

Good luck arguing with Ms if you aren't a giant company

[–] [email protected] 94 points 2 weeks ago (2 children)

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

[–] [email protected] 118 points 2 weeks ago (1 children)

They labelled an OS version upgrade as a security update.

[–] [email protected] 27 points 2 weeks ago (1 children)

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

[–] [email protected] 41 points 2 weeks ago (1 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.

[–] [email protected] 12 points 2 weeks ago (2 children)

Should still be doing phased rollouts of any patches, and where possible, implementing them on pre-prod first.

[–] [email protected] 11 points 2 weeks ago* (last edited 2 weeks 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.

[–] [email protected] 11 points 2 weeks ago (1 children)

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.

load more comments (1 replies)
[–] [email protected] 7 points 2 weeks ago (3 children)

Wrong.

Microsoft labelled the update as a security update

load more comments (3 replies)
[–] [email protected] 87 points 2 weeks ago (3 children)

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

[–] [email protected] 62 points 2 weeks ago (6 children)

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...

load more comments (6 replies)
[–] [email protected] 10 points 2 weeks 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.

load more comments (1 replies)
[–] [email protected] 46 points 2 weeks ago (2 children)

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 :)

[–] [email protected] 46 points 2 weeks ago

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

load more comments (1 replies)
[–] [email protected] 36 points 2 weeks ago (10 children)

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

[–] [email protected] 64 points 2 weeks ago (3 children)

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.

[–] [email protected] 21 points 2 weeks ago

I only go in the server room to t-pose in front of the giant air conditioner to cool off.

load more comments (2 replies)
[–] [email protected] 36 points 2 weeks ago (1 children)
[–] [email protected] 10 points 2 weeks ago

I knew a guy with almost that exact resume, except he told me it was chickens. He worked in Lagos during the week and went back to his chickens in rural Nigeria on the weekend.

[–] [email protected] 31 points 2 weeks ago (2 children)

I think they call them devops now.

load more comments (2 replies)
[–] [email protected] 17 points 2 weeks ago (1 children)

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)!

[–] [email protected] 30 points 2 weeks ago (5 children)

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

[–] [email protected] 9 points 2 weeks ago (3 children)

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.

load more comments (3 replies)
load more comments (4 replies)
[–] [email protected] 11 points 2 weeks ago

That's my job title.

load more comments (5 replies)
[–] [email protected] 35 points 2 weeks ago (1 children)

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.

[–] [email protected] 14 points 2 weeks ago* (last edited 2 weeks ago)

Copilot just forced itself onto my personal machines again so it's just typical Windows fuckery all around.

[–] [email protected] 33 points 2 weeks ago (5 children)

When the OS becomes the virus

load more comments (5 replies)
[–] [email protected] 20 points 2 weeks ago (5 children)

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

[–] [email protected] 25 points 2 weeks ago

While you are generally correct, in this case the release notes labeled this as a security update and not an OS upgrade. The fault for this is Microsoft's not the sysadmin.

[–] [email protected] 15 points 2 weeks ago (1 children)

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.

load more comments (1 replies)
load more comments (3 replies)
[–] [email protected] 17 points 2 weeks ago (1 children)

You thought you were in control?

load more comments (1 replies)
[–] [email protected] 12 points 2 weeks ago

Crowdstrike moment

[–] [email protected] 10 points 2 weeks ago (2 children)

Meanwhile I've still got customers who are running CentOS 6.

[–] [email protected] 10 points 2 weeks 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.

load more comments (1 replies)
[–] [email protected] 9 points 2 weeks ago

"Labeling error"

Lol, okay.

[–] [email protected] 7 points 2 weeks ago

Of all the people MS doesn't want to piss off.

load more comments
view more: next ›