@sebastian-roth Looks like I am getting a little bit further as I had secure boot turned on and that wasn’t allowed as ipxe.efi isn’t signed so was causing issues. I’m nearly there however it’s now when it’s booting into the PXE mode it starts, connects to the fog server however when it trys to connect to the servic/ipxe/boot.php the ipaddress it is using is an old IP address that the server as using when we were testing. I have changed the IP address as detailed in this article but obviously I have missed something somewhere.

Any ideas where this old address is saved so that I can change that reference as well.

@sebastian-roth Thanks very much for your swift reply.

That would make sense as yes you are correct in that we are using UEFI mode for booting. I have modified the DHCP Server (Windows Server 2019) to add the policy as detailed in the wiki link that you provided. I left the option for 067 set in scope options as well to allow for non-UEFI clients that we have a few legacy systems on our network but I did modify this to add the extra k that I was missing before. The policy seems to be working as it’s now downloading the ipxe.efi successfully however it then doesn’t boot into the ipxe.efi environment it is still booting into windows and displaying the logons screen.

Hopefully, you can provide some further assistance.

Kind Regards

Good Afternoon All,

I am new to FOG and getting it set up and configured in our environment. I have successfully got it all set up and working and have gone to do a PXE boot to capture the first image from a machine. The PXE IPv4 boot starts and it connects to our FOG Server, it get an IP address finds the nbp file (undionly.kpxe) downloads it successfully, then it starts an IPv6 PXE boot for which there isn’t anything and then boots into windows.

Can someone please provide some guidance on this. My system is as follows:

Fog 1.5.9 on Ubuntu 20.04
DHCP on separate windows server configured as this article

Thanks in advanced

Frosty