Thanks guys!

We’re using an external RHEL server to run DHCP for the campus, so DHCP isn’t hosted on the FOG server. We confirmed in DHCP that the redirect lists undionly.kpxe as the filename. Thanks especially to @Sebastian-Roth for suggesting trying the realtek option. We switched filename to realtek.kpxe and the laptop is booting!

For fun, we tested booting two Dell desktops and two HP desktops after the realtek change. The Dells boot perfectly, while the HPs now having the same issue the laptop had (i.e. DHCP failed). Looks like we’ll use the realtek file to take care of this laptop, then change back to undionly for our general use.

Thanks for all the help!

Thanks for the quick replies!

Tom: I found the post we used to upgrade (https://forums.fogproject.org/topic/6508/upload-image-from-hp-probook-450-g3/10). We used the directions @Sebastian-Roth provided (starts with “service xinetd stop”) to pull the current tftp files from the svn repository last week. I looked in the web interface & in Linux, but I don’t see where the version is listed. Where should I look & which info should I provide?

@ch3i: Did the directions we followed do what you’re asking us to try? If not, I can ask our server engineer to create a clone so we can play with a dev environment.

Hey Folks,

We’ve been using FOG 1.2.0 on RHEL since the summer and everyone in the IT staff at the college I work at loves it! Definite improvement over Symantec Ghost.

We have a new laptop (HP ProBook 455 G3) that is refusing to PXE boot (see attached image). The G1 and G2 revisions are marked as supported devices, but I haven’t been able to find info for the G3. We’ve had success with 10+ other models, including a few HPs. After some research, we found a post suggesting that we pull the most current iPXE files, which doesn’t appear to have changed anything. We also tried disabling UEFI boot options to no avail.

Any suggestions?

-Joel