I’m having similar issues on a newly created Windows 11 24H2 FOG image. (Please note that the sysprep answer file I created is bypassing the Secure Boot check allowing FOG to pxeboot from the VM for capture). Once I bring the image down on a physical device and try to encrypt the drive I get the identical error shown above. If I go into the BIOS and enable Secure Boot the device begins encrypting automatically after a restart. NOTE: The drive will fully encrypt and the recovery key is populated successfully in Active Directory. I was feeling confident until I restarted again, then got a BSOD (unrecoverable). Windows 10/11 without secure boot enabled at the time of installation/imaging does not like having secure boot suddenly enabled.
So, if my thinking is correct this has something to do with secure boot, or more precisely the act of bypassing the secure boot check during Windows setup that was done in the sysprep answer file.
FOG can’t pxe boot on devices with secure boot enabled, but those same machines can’t be encrypted without secure boot and enabling secure boot after imaging only ends in a BSOD (unrecoverable).
FOG 1.5.10 on Ubuntu 2204
-
0
Votes5
Posts146
Views -
0
Votes1
Posts47
Views -
0
Votes21
Posts977
Views -
0
Votes5
Posts139
Views -
0
Votes10
Posts115
Views -
0
Votes4
Posts71
Views -
0
Votes5
Posts296
Views -
0
Votes3
Posts526
Views -
0
Votes4
Posts384
Views -
0
Votes7
Posts398
Views -
0
Votes3
Posts126
Views -
0
Votes2
Posts238
Views -
Solved Fog Client replaced powershell script with "Please update your FOG Client, this is old and insecure"
• • MatMurdock0
Votes12
Posts208
Views -
0
Votes5
Posts414
Views -
0
Votes4
Posts458
Views -
0
Votes5
Posts242
Views -
0
Votes6
Posts361
Views -
0
Votes3
Posts281
Views -
0
Votes8
Posts385
Views -
0
Votes2
Posts326
Views