This is quite bad as you can probably only fix this by having access to the physical device (except probably virtual cloud servers). Holy shit.
Yes, most servers do include some sort of remote management interface (ie. ILOM, etc), so you can access server remotely as if you were in front of it....however its going to be fixing these issues one at a time....and there are companies reporting 50k+ machines offline.
Some corporate desktops support vPro - which is a similar remote management interface.
However the manual fix is stymied if hard drive is encrypted.
So best case is manual fix takes ~10 mins per device (but you need either physical access or access to remote interface).... so a company with 50,000 affected machines will be 500,000 minutes for repair time....
Its a shitshow!
reply
You can probably do some automation and bring down the time to fix it but even then its horrible.
I guess everyone working in an affected corp will be a sysadmin for a day :)
reply
I guess everyone working in an affected corp will be a sysadmin for a day :)
I was thinking the exact same thing. Probably quickest automation is to type out one-page step-by-step instructions and enlist every random corporate cubicle worker as mechanical turks to fix.
reply
the question is how to send the instructions to the worker. By fax? :)
reply
I've actually been there.
After doing a few by hand I thought, "I can write a Perl script for this." So I did. That's how I got through it.
reply
Windows 10 was released in 2015
reply