@george1421 Attached is the file. Thank you so much for you help! 0_1479855472664_output.pcap

@george1421 I have the file on my Linux machine. I am not a Linux guru so I am not sure how to pull the file from Linux to get it to you. The Linux server is not GUI based. How would I retrieve these files to send them to you?

Update to RC-25 which also required a schema update. The BIOS is currently booting to legacy boot. Re-added the entries into DHCP. (My test machines in my office are a Dell Optiplex 990 and an HP EliteDesk 880)

Also ran the command tftp -i 10.0.0.17 get undionly.kpxe and ipxe.efi. Which appears to be successful.

Unfortunately neither of these steps have corrected the issue that when the system boots it still goes to the PXE-e53 - No boot file found.

Server

• FOG Version: 1.3.0-RC-23
• OS: Debian

Client

• Service Version: 6017
• OS: Windows 10 Pro

Description

About a week ago we updated SVN. After the update we were getting a chainloader error. In order to keep our users from having to hit esc or remove the network cable, I removed the DHCP entry on our DHCP servers. After selecting the options 066 and 067 in on our DHCP, now Fog does not even come up on our systems. It errors out PXE-e53 No Boot File Found. Our original boot image was ipxe.efi but in forums I have seen that the boot image is undionly.kpxe. Can you clarify this, also?