Yes, that does the same thing as the E-Boot. We are running in autoboot mode until we can deploy PBA and we frequently have users whose autoboot config breaks. We have a process our helpdesk can do to initiate a decrypt of the drive, and re-encrypting results in the machine's configuration being reloaded again like a new setup does.
Don't know if it will help with your unsupported algorithm error though. I've had no luck recovering from that.
1 of 1 people found this helpful
remove also decrypts, eBoot only replaces the SBFS.
Oh yeah, there is that aspect of it
We've run into this occasionally. Boot into WinTech and mount SBFS as a drive. (Assuming you know how to do a whole lotta steps to get here...) Using your fav file manager in WinTech open the SBFS drive then the SbAlgs folder. When we get this error we find there's nothing in this folder. We fix it by copying the SbAlg.dlm file from a known working client into this folder (could even be the C: drive on the same machine--just unlock encryption using SDB file instead of SBFS--or put it on the WinTech CD in advance). Reboot and you're back in business. No clue why it happens. It's rare but continues to happen from time to time. We have only one version of EEPC (5.2.2) running in our organization. Don't know if it matters but if you run multiple versions I guess I'd suggest you use the SbAlg.dlm file that matches the machine you're fixing. Maybe one of the McAfee guys on here could tell you if that matters.