Hi, I am having the exact same issue, with the Optiplex 3020’s. Were you able to find a solution?

There is currently no way to work around the secure boot issue.

To boot with secure boot on the boot OS needs to have a signed certificate. This certification process requires both iPXE (from another FOSS project) and FOS (from the FOG Project) to be digitally signed. Getting these items signed and certified is time consuming and expensive (from a FOSS standpoint).

@Sebastian-Roth Thanks you!!! I swapped out the ipxe.kpxe file and it worked.

@george1421 Got it. I made the changes and in the process of deploying my first image now. Appreciate the help.

Server

FOG Version: 1.5.6 OS: Debian 9.9 Kernel: 4.19.48 TomElliott 64 and 4.19.48 TomElliott 32

Client

Model: Lenovo X1 Carbon Gen6 Dock: Lenovo Dock USB-C DK1633 OS: Windows 10 Pro 64 Secure boot: disabled

Description
Hello,

I’ve the same problem on Lenovo X1 Gen 6.
As @george1421 suggested, I turned to FOS. Unfortunately I don’t understand the documentation to build an image.

Thanks for your help.

Solution
This works well with the adapter provided by Lenovo.

@george1421 Just wanted to let you know that I updated to the latest kernel as suggested and it worked! Not sure if anyone else has the same issue, but now we can image about 630 PCs! You guys rock!

@Zark110 Just as a quick test an you connect a dumb unmanaged switch between the client and your main switch? Then try again.

@Sebastian-Roth Intel Core i5-7260U @ 2.2GHz * -shrugs- *

If I may interject with a very hypothetical statement. If you end up using the fog client portion of this solution on more than say a few hundred hosts, you may think about making the server a bit beefier. Here is my setup

For my 1500 hosts that check in with the client:

4 vcpu’s
8GB RAM
250GB storage (we use model specific images)

May be overkill but it works pretty well for me

@Sebastian-Roth So just out of a combination of desperation and curiosity, I tried a different computer with the same exact specs. Changing to AHCI worked. The original computer works fine except for this one FOG issue. I booted into Windows, ran chkdsk, installed a program, rebooted and everything worked like there wasn’t a problem. I reinstalled Windows with the Dell USB recovery disk and FOG was able to pull an AHCI mode image. Out of 15 computers, two had this issue. I think this is a fluke with Dell. Thanks for both your guys’ help.

@Sebastian-Roth Found a firmware update for the model and took a peek at it’s change log. Didn’t see anything relating to PXE in recent changes. Ran it anyway to bring it current. No changes in PXE boot behavior.

@george1421 Ran a capture job before I left Friday using the FOSLinux usb boot method. Checking the deploy sometime today.

As always, thanks for you help you two!

@tandersb the date is a nice to have feature and is not indicative of an issue. In particular the master node has a service that updates the sizes. To get the date, the image is updated once the capture task is completed. This, however, does not mean there is (or isn’t I suppose too) a problem with the image. Are you having issues using it?

And everything works!! Thank you for help!

@Zourous Sorry I should have asked this in the last round, does your fog server currently have multiple nic cards?

Dell switch, what model?

i figured out, i had to turn secure boot off!

Eric

@TBCS Mmmmmm cookies…

I’m glad you have it worked out and it was simple enough to just update your firmware (which you probably should have done anyways).

@Fernando-Gietz said in Dell Optiplex 7050 and UEFI boot. Failed:

I wonder if is a miracle that it has worked well until now in the other hardwares

I’m glad you have it working now. Yes its strange why you didn’t find another system with the same issues. But that is why I included both, I ran across a system that would boot with the netboot info alone.

@george1421 That was a really helpful guide. Easy to follow and now we’re ready for whatever type of boot we need.

@george1421 I’ve got two videos for you. The BIOS Firmware on the problematic one is newer than the one where it works. I’ll try a rollback and see if that makes a difference. Anyways…

This is for the remaining problematic 1040G3

Video 1: https://drive.google.com/open?id=1OEeLrkW2I8FIqLh092IHH03-zAhcM8X6
This is me using the USB Bootable Flash Drive

Video 2: https://drive.google.com/open?id=1Uz4cCiQf00VymXMKCqfiA7VK5-KKP3xl
PXE Booting without the USB Bootable Flash Drive

@JBrown-RCPD said in Panasonic Toughpad FZ-G1 Windows 10:

We have to disable UEFI, Secure Boot and select “Compatible” in Boot Mode to get the device to PXE boot to the FOG server however when continuing to boot to the hard drive it will not boot into Windows with UEFI still disabled.

Wow there is so much going on here.

why did you disable uefi? Is it because the device will not pxe boot in uefi mode? When the device is in uefi mode, what did you have configured for the boot file (in DHCP option 67)/ When the device is in uefi mode, you will need to disable secure boot that is a requirement since FOG doesn’t have signed boot kernels. If the target computer is in uefi mode, is your golden image also uefi? (fwiw you can’t deploy a bios captured image to a uefi based computer, or the other way around too. You can only deploy a uefi captured image to a uefi based computer. The same goes for bios based systems) Does the image deploy correctly, just the FOG is not setting the boot order correctly in the UEFI firmware, where if you manually pick the hard drive it boots correctly. What version of FOG are you using?