@Wayne-Workman@Sebastian-Roth I figured it out. The issue was with another DHCP server at another campus. For some reason it was see that server and not communicating since I did not have the server options stored. After adding the options its pxe booting fine.

While I’m not the sharpest tool in the shed, but wouldn’t this imply that the OP has the right settings for dhcp?

When I try to pxe boot, I am getting the message “Could not start download: Operation not supported (http://ipxe.org/3c092003)”

If the OP is getting a warning message that indicates “ipxe.org”, it would seem that the ipxe boot file [udnionly.kpxe] made it to the target computer, since the PXE boot loader doesn’t know anything about ipxe? and ipxe is generating the error.

OP are you getting any bits of the boot menu? Maybe a screen (mobile phone) shot of the boot screen might give an indication of the root of the error. The error basically says you tried to use a protocol that isn’t supported by this ipx kernel. This is not something that is in the OPs control.

Have you tried searching the forums? This error is being reported many times. Are you sure your windows DHCP server is handing out the correct information (take a look using wireshark for example). Is tftp on your FOG server running and listening (netstat -antup | grep ":69")?

@monasmith529 is the fog server virtualized too? is the client’s NIC type set to bridged? What’s doing DHCP ? Are you behind a home router device? Normally those do DHCP too, and they usually don’t support the needed options.

MOST people would use dnsmasq at home if they didn’t want to turn DHCP off for their home routing device.