650
submitted 4 months ago by yesman@lemmy.world to c/linuxmemes@lemmy.world
you are viewing a single comment's thread
view the rest of the comments
[-] adhdplantdev@lemm.ee 4 points 4 months ago* (last edited 4 months ago)

It's going to be a grind. This is causing blue screen of death on Windows machines which can only be rectified if you have physical/console access.

In the cloud space if this is happening to you I think you're screwed. I mean theoretically there's a way to do it by installing Windows unmounting the disc from the virtual machine to another working virtual machine but it's a freaking bear.

Basically everyone's going to have to grind this whole thing out to fix this problem. There's not going to be an easy way to use automation unless they have a way to destroy and recreate all their computers.

I live in linuxland and it's been really fun watching this from the side. I really feel for this admins having to deal with this right now because it's going to just suck.

[-] Morphit@feddit.uk 2 points 4 months ago

I'd have thought the cloud side would be pretty easy to script over. Presumably the images aren't encrypted from the host filesystem so just ensure each VM is off, mount its image, delete the offending files, unmount the image and start the VM back up. Check it works for a few test machines then let it rip on the whole fleet.

[-] adhdplantdev@lemm.ee 8 points 4 months ago* (last edited 4 months ago)

Oh my friend. You think these companies do things in a logical scalable way? I have some really bad news....

Theoretically that could work but sometimes security measures require computers be BitLocker encrypted and certain softwares could make this difficult to achieve like fixing a domain controller.

this post was submitted on 20 Jul 2024
650 points (98.4% liked)

linuxmemes

21281 readers
320 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 1 year ago
    MODERATORS