Did you try to perform EEPC Emergency Boot procedure to see if it resolves problem on affected systems?
We didn't bother, as recovery is not required - these are freshly built machines.
The issue is that this will effect every new and re-built laptop, so we need a set of files/installation process that will work with our build process...
Fortunately we have discovered this in our test environment, but with a dozen or so of these new laptops due for deployment next week we need to find a solution!
Further to my other post it looks like 'McAfee_EEM_525' and 'McAfee_EEPC_525' are the upgrade options for our 5.1.6 installation.
I see there is also McAfeeEEPC6 and a patch (601), but cannot see any docs in these downloads... Presumably there is no related EEM for v6 as this is now managed in ePO? Is there any news on how to upgrade from v5.x to v6 so that we can integrate our safeboot deployment into our existing ePO?
You need to wait for EEPC v6.1 public release to have migration from 5.x feature. But test it well first.
Going back to your original question, I suggest that you try EEPC Emergency Boot procedure.
Thanks Peter, butI really don't see the point. This is a build process (which is frequently used), that fails in this manner every time. We are not going to deploy with something in this state and so need to establish the underlying cause and a fix.
We have an incident open with McAfee, and hopefully they can advise us of a way forward
If a new build fails with this error, you may try EEPC 5.2.5 in eval mode to see if it resolves your issue.
Do not use RAID configuration in BIOS of those machines. What other SATA options do you have?
how do you install SafeBoot? using the EXE, or have you "baked it in" somehow?
As peter says, what drive mode are you using in the BIOS? ACHI, SATA etc?
Thanks for the replies.
We use the .exe, as generated via the Safeboot Administrator (create installation set, online, etc. etc.) - this gets called in the final phase of our build process (for laptops only)
All our machines are set to use AHCI mode (and always have been).
This process have been working for nearly two years, and nothing has changed regarding the safeboot backend or installation files.
This issue has only occurred since we had to update the intel drivers for the build (as per intial post).
Again, the build work fine, it is only after safeboot has modified the mbr and started encrypting the disks that the issue occurs
If drivers are fully established before SafeBoot installs, then look into your storage drivers configuration. Maybe you have dormant/inactive driver(s) that confuses SafeBoot.
David, Did you manage to find a fix to this? I've just build an image for a new Dell Latitude E6410 and am having the exact same problem......