Topics created by PvWinters

@pvwinters said in Ipxe boot to Uefi shell reboot afther +/- 5 min:

Question is there a way to hold the old ipxe server and remove the WDS and combine it with the new fog server?

I want to keep the IPXE Server as the default one and when my tech guys want to deploy or capture a image to can boot to the FOG server and do there thing.

Ok this changes the context a bit but its still possible. So let me tell you how FOG works then we can see what fits best for you. Personally I would remove the old pxe boot server and just use FOG for everything, but that is just my opinion not understanding your requirements.

So in a clean fog environment you have dhcp option 66 with the fog server IP address and dhcp option 67 to point to the ipxe boot loader you want to use (there are other options for this but lets not muddy the water right now). The client pxe boots and FOG’s ipxe boot loader is transferred to the client computer. That client computer then boots, requests dhcp address then starts running a script built into the ipxe boot loader where it uses dhcp option 66 to get the IP address of the FOG server and then chains to a file called default.ipxe. default.ipxe then again chains and loads boot.php which builds the FOG iPXE menu.

So with that said, from your current (legacy) ipxe boot server you can chain to tftp://<fogserverip>/default.ipxe to jump into FOG. As long as your legacy ipxe server is running a somewhat current version of iPXE that should work.

Now WDS has 2 ways you can configure it. One is using dhcp option 66 and 67, the other is with a ProxyDHCP service that will send out the pxe boot information that will override dhcp options 66 and 67. FWIW, you can chain from FOG into WDS if needed (I assume ipxe too) with the right chain command.