@maximeguidez I ran into this issue in the past, and if I remember right switching the bootfile to snp.efi was what fixed the issue. I’ve stopped using ipxe.efi altogether, since snp.efi seems to cover all of the devices I end up imaging.

If that doesn’t work, I’d recommend updating the kernel version.

@george1421 I had already used that article you linked to set up DHCP for UEFI and BIOS coexistence, but it only has information for 5 of the architectures (00002, 00006, 00007, 00008, 00009). I need to know what to point the remaining 4 types to, because there’s 4 remaining that don’t have any association.

That’s why I was wondering if there’s any simple way to view the boot architecture on any specific PC, so I could go PC by PC and set up the policies that way

I’m looking into setting up FOG servers for multiple of our customers for simple workstation captures, and I’m worried about the pxe boot process with such a wide variety of PCs.

I currently have Windows DHCP set to look at the architecture type, then pick a bootfile based on that.

Is there a way to view what pre-boot architecture type a PC has? If I could do that, it would make my life much easier. Then I would be able to make the correct DHCP policies for each architecture, so I can avoid PXE boot related issues.

I’d be willing to share the DHCP policies to help others, I just need to figure this out first so I can get them configured correctly.

I’d like to remove a few of the questions when performing a Full Host Registration & Inventory. Is there any simple way to do this? I just want it to ask for the name, image ID, and whether or not it wants to image the PC or not.

Any help is appreciated, even if it’s just a suggestion.

To start, I’m following the following link to setup UEFI and BIOS to PXE boot correctly:
https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy

I have the vendor classes setup, but I’m not sure what architectures to assign to bootfiles. For example, I’ve had ipxe.efi work 99% of the time, but there’s some models that only snp.efi and snponly.efi work on. As a result of this, I’m skeptical what bootfile I’m supposed to use for each architecture.

Just looking for guidance to see what has worked for others, because the tutorial I sent a link for only includes instructions for PXE client architecture 00007. Any help/ suggestions are appreciated. I want to make sure I have everything setup correctly before I put this in a live environment

@sebastian-roth Fair enough. Out of curiosity, when I entered an IP for the DHCP server during FOG installation, what exactly did that do then?

I’m currently using a sonicwall for DHCP on my FOG server, but I’ll bet setting up a DHCP on a windows server to replace it. How do I change the IP of the DHCP server FOG is pointed at?

I know I set it during the initial FOG installation, but I can’t find anywhere I can change it.

@sebastian-roth Thanks to your suggestions I took a deeper look at the host server I was provided for this project, and there was a lot of driver packages missing. Once I installed those drivers, everything loads at a good speed now.

In the end it was my mistake not looking over the host server my colleague prepared for me, but I learned a lot more about FOG in the process so it wasn’t all time wasted.

I appreciate the help though, sorry if I confused you there

@sebastian-roth I tested on another machine, and it ran into the same issue with bzImage and init.xz loading slowly. I confirmed I don’t have this issue on my other FOG server using this same machine & bootfile that I’m testing with. What would you reccomend doing next? I’ve updated to the most recent kernel & have the most recent init files that I could find.

@sebastian-roth I’ll give that a shot. Do you think changing bootfiles will resolve this issue on certain models?