VirtualBox driver error when deploying an image (ThinkPad E14 Gen 3
-
Hi all,
I’ve lurked here for awhile and absorbed so much information from this forum, it’s wonderful. I have a FOG server for deploying mainly Lenovo images and I’m having issues with one of them. When deploying to a ThinkPad E14 Gen 3, I get an unsigned driver error for a VirtualBox driver (I built my images in VirtualBox then captured to the FOG server, and deploying using the postdownload scripts in the “holy grail” thread by @george1421). I’m wondering if anyone else has encountered this issue and how others solved this. I saw in the postdownload thread that someone had to run the driver install without checking for signed drivers… which I would like to avoid.So is it safe to remove that driver from my VM image before capture without it breaking the VM? Anyone know?
Thanks!
-
I figured it out. Don’t turn Secure Boot back on until the image has booted, gone through OOBE and installed the drivers.
-
@bofh said in VirtualBox driver error when deploying an image (ThinkPad E14 Gen 3:
until the image has booted, gone through OOBE and installed the drivers
yes use the setupcomplete.cmd batch file to do this. This is the same one used to reenable the fog client if you are using it.
-
@bofh said in VirtualBox driver error when deploying an image (ThinkPad E14 Gen 3:
Don’t turn Secure Boot back on
Sorry about the broken post but this covers a different topic than my first post. You CAN clone a disk drive with secure boot/bitlocker encrypted. BUT it will fail to boot once it is deployed to the target computer. This is because the target image doesn’t match the signature held in the TPM chip. Also it would kind of defeat the purpose of bitlocker if you could just clone an encrypted image and boot it on another computer. That is kind of the point of whole disk encryption (to protect the content of the disk).
Well done on getting it worked out.
-
@george1421 yep! That’s how I have it set up. Works beautifully now
re: bitlocker - yeah, that makes sense regarding mismatched TPM signatures. Luckily I don’t have to worry about that at the moment
