Specmaster wrote: ↑Wed Jul 24, 2024 9:03 pm
tggzzz wrote: ↑Wed Jul 24, 2024 7:02 pm
Specmaster wrote: ↑Wed Jul 24, 2024 6:28 pm
This is interesting, a bit over my head to sort it out, but if this what he is saying is correct, then once you know what to look for then it should be easy to resolve.
I t didn't take long for the "reboot in safe mode, use CLI to delete some files, reboot" procedure to be stated. One of the early comments was "good, but how do I apply it to 70000 endpoints".
Err, 1 at a time
![Laughing :lol:](./images/smilies/icon_lol.gif)
Seriously, if you have that many, then you are in the do dos
For example
https://www.theregister.com/2024/07/19/ ... date_mess/ The second is predictably grim. The last is a doozy, and ought to have be considered while the installation was being configured.
He isn't alone. An administrator on Reddit said 40 percent of servers were affected, along with 70 percent of client computers stuck in a bootloop, or approximately 1,000 endpoints. Other administrators reported having 250,000 clients and servers all over the world to deal with.
...
He told us: "The fix, while pretty simple, requires hands on the machine, which is not great when most are remote. Talking a warehouse operator through the intricacies of BitLocker recovery keys and command prompts is not for the faint-hearted!"
BitLocker is Microsoft's encryption tool, and it makes a device's storage inaccessible without a recovery key. As such, trying to work through some of the current recovery options on a modern device will likely require the use of that recovery key. Pity the administrators who dutifully kept a list of those keys on a secure server share, only to find that the server is also now showing a screen of baleful blue.
...
Another Redditor posted: "They sent us a patch but it required we boot into safe mode. "We can't boot into safe mode because our BitLocker keys are stored inside of a service that we can't login to because our AD is down.