Therefore, I have to unfortunately make the recommendation: Manually enabling SecureBoot can be a labor intensive process. This sucks for customers that need to use tools to make changes at scale. I have tried to explain this point to Lenovo, but to no success. However, Enabling secure boot has no such requirement (that I can find), and Dell, HP, and Lenovo ThinkPad devices do support enabling SecureBoot programmatically. In all cases, end user must be physically present to establish proof of possession (POP) associated with the changes. Each manufacturer has its own interface for this option. Users may disable Secure Boot entirely, using a system setup screen enabled at boot time. Lenovo is only half right, Disabling Secure Boot must always require physical presence, that is clearly documented by UEFI spec: I did contact Lenovo directly, and their official response is that they are aware of the issue, but the lack of support for API access to/from SecureBoot on desktop models is “by-Design”.
On Lenovo Laptops, we can change from BIOS to UEFI with SecureBoot, but they don’t offer the ability to move from BIOS to UEFI without SecureBoot.That’s great! Unfortunately there are two areas where their implementation is lacking compared to Dell or HP:
Lenovo does have an WMI API for programmatically making changes to the BIOS from within Windows (either the full OS or WinPE). Been working with several IT departments trying to get our BIOS to UEFI solution qualified on as many OEM hardware models as possible, but unfortunately we have hit a snag that will affect Lenovo customers who need to move from BIOS to UEFI with SecureBoot using automated tools.
0 kommentar(er)
