Capture 7290 with UEFI

[Tom]

Dear All,

Fog 1.5
Client: Latitude 7290 with Windows 10

I have Latitude E7290. The boot is uefi and it seems that I cannot change it to legacy.
In addition, it seems that there bitlocker signature on dev\sda3 header. I disable the bitlocker service, but that did not help.

How can I capture\deploy this laptop with FOG?

Please keep in mind that our FOG is servicing other laptop models with legacy bios.

Thank you,

Tom

[Tom]

Here is a short movie of the issue:
Short Video

[george1421]

First I would go throught this article and setup bios/uefi coexistence to keep you from going insane having to deal with both platforms: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy

Bitlocker is a problem that you must address on the reference computer. You must completely disable bitlocker and unencrypt the drive. FOG will copy it encrypted but it won’t ever boot on the target computer because the TPM chip will not be configured correctly. Always enable bitlocker on the target system after fog has done its business.

[Tom]

Complete the settings as described in the article.
Does anyone knows which uefi architecture E7290 has? I called Dell support, they do not have a clue,

Thanks,

Tom

[george1421]

@tom If you setup wireshark on the same subnet as the 7290, you can tell. If you use this capture filter port 67 or port 68 then pxe boot the target computer. Your answer will be in the first discover packet. Just make sure the mac address matches your 7290. But I would setup for both uefi BC (7) and X64 (9) just to be sure.

[Tom]

@george1421 The following steps allowed me to capture and deploy 7290 image:

1. Followed the steps in the article, set the policy to Architecture 00009.
2. Build Windows 10 from scratch to eliminate hard drive bitlocker encryption.
3. Disabled TPM in the Bios. (Just to be safe)

Although, everything seems to work, there ACPI errors which I am not sure if it’s a concern.
Please see Video 2 HERE

Thanks,

Tom

[george1421]

@tom Those errors are warning, and not a problem. The system should image fine.

[Tom]

@george1421 In that case, the issue resolved. Thank you for all the help.
Tom