@ConJon said in DHCP Booting Fails and enters wrong IP Address:

It does seem to be working now. Thanks!!!

just changing that default.ipxe doesn’t fix the problem. There are a few other places where there is hard coded IP addresses.

in the fog server OS in /opt/fog/.fogsettings file
In the web ui
FOG Configuration -> FOG Settings->Expand All (search for the old IP address)
FOG Storage->Storage Node-> Default

Fix it there and save then back to the FOG Server command prompt and then rerun the fog installer to fix the remaining bits. If you don’t do these steps you will have a painful fog experience.

@george1421 Awesome! Thank you, George!

@Sebastian-Roth That makes sense, to be honest, just didn’t think it would make a big difference. I actually followed those exact instructions to get UEFI working. All machines were able to boot to UEFI before. But now it’s just the one. The only thing that I changed was I reverted the changes I made for the driver injection that george1421 made. Now as I said only one machine that can boot with UEFI. It’s weird though, I can image the other machines with a UEFI format through the legacy Onboard NIC.

@Fernando-Gietz @george1421 Oh, well now I just feel dumb. That’s on me. Sorry guys. And thank you

@ConJon @jmason As we haven’t heard from other users this being a problem I suspect pretty much all current UEFI firmwares are able to find Windows bootloaders by themselves and I don’t see why we should mess with this if there is no need for 99% of users. I’ll put this to the archive unless I hear otherwise from someone.

If you still see this issue talk to your mainboard manufacturer first to provide an updated UEFI firmware.

@george1421 Oh, my apologies. Thank you very much for your help. You’re truly a wizard as your profile picture shows. 😉 Thank you again!

@ConJon said in Boot to Image:

We only image one kind of machine. I am wondering if it’s possible to skip everything on the host side and when we boot to the NIC, it skips every menu and starts the only image we use. Anyone know of any way to do that.

Hi, what you want sounds dangerous, what if a client boots via network by accident? You will wipe the hdd/ssd and deploy a new image.

A good idea would be something like waiting for admin to approve. Like IBM Tovoli does.

Regards X23

@george1421 Hahaha, it’s all good. Thank you! Merry Christmas!

Fixed. I needed to run the command “service mysql restart”