Not getting much by Googling.

If not, what’s the ETA?

  • Kit
    link
    fedilink
    arrow-up
    14
    ·
    2 months ago

    Yeah we good. The fix was ezpz and even a company with several thousand servers should be up now. End user workstations may take more effort, but it’s a 5 min fix per user.

    Honestly this was half as stressful as Print Nightmare was, from an IT perspective.

    • Psychodelic@lemmy.world
      link
      fedilink
      arrow-up
      13
      ·
      2 months ago

      Glad it wasn’t too bad for you/y’all.

      Unfortunately, I wiped my computer Thursday night before our company mentioned anything. lol. I ended up finding out about the issue on Lemmy/Reddit. My company didn’t send anything out until this morning - which I still find insane, my laptop crashed and started looping around 7p (took them like 12 hours).

      My laptop just rebooted while I was working so I assumed some program I’d installed caused it (explorerpatcher). I tried everything, safe mode, system restore, uninstall updates. I figured the only option left was to reinstall windows. Done it plenty of times on my personal PC

      Oh well, lesson learned. Shit’s totally fucked now. It won’t even connect to the Internet. lol. Definitely a Monday problem though

      • vrek@programming.dev
        link
        fedilink
        English
        arrow-up
        26
        ·
        2 months ago

        Hold up… You thought maybe you downloaded malware (which in this case that was not the only cause) so you took it upon yourself to reinstall windows on a company issued laptop?

        1. Why are you trying to fix it? Submit It ticket and it’s their problem.

        2. If you suspect malware alert it security immediately. Many malware act as a gateway to lock other systems. Yes you might get in trouble but I’d rather be yelled at for downloading something then yelled at for infecting my company servers will ransomware/malware.

        3. Atleast in my company a computer connecting without a company supplied image of windows will be denied. Completely understand you not connecting to the internet.

        4. This problem was not caused by you but could of been… Take this as a lesson to be more proactive in the future.

        • bassomitron@lemmy.world
          link
          fedilink
          English
          arrow-up
          5
          ·
          2 months ago

          They might have a BYOD policy at work where they remote into an azure desktop or something and then reinstalled Windows on their physical device. Who knows. But yeah, they still should have notified their security personnel at the very least before taking any further action, lol.

        • CoopaLoopa@lemmy.dbzer0.com
          link
          fedilink
          arrow-up
          4
          ·
          2 months ago

          This is actually the worst type of end-user.

          Doesn’t make a ticket or notify anyone that there is a problem and then proceeds to try and fix it themselves incorrectly. When it does become a ticket, they won’t remember exactly what steps they took to troubleshoot and will waste 5x as much time from support staff trying to fix it than if they just didn’t touch it in the first place.

          Guaranteed didn’t wipe the machine from the built in reset/recovery screen and instead used a windows installer that was created on a different computer and doesn’t have the correct network drivers in the image.

        • Shadow@lemmy.ca
          link
          fedilink
          arrow-up
          2
          ·
          2 months ago

          Yeah #2 is a big one. I’ve had to deal with a user who got hit by a supply chain attack, and doing forensics on their box was invaluable.

          If they’d wiped their desktop as soon as it got compromised, we’d have nothing to go off of. I’d expect that user to be in some pretty serious trouble tbh for violating our security policy by not notifying us immediately.