@brakcounty To get some more information, can you please schedule a debug deploy task (same as you would do a normal deploy task but just before you hit the last button in the web UI there is a check box for debug). Boot up the client as usual and let it boot up. Then you need to hit ENTER twice to get to the shell. Now type fog and ENTER again to start and step through all the process till you hit the error. It will throw you back to the shell. Now type: sgdisk -gl /images/Win10Standard_GPT_EFI/d1.mbr /dev/sda It surely will fail. Take a picture of the screen and post that here.

@KevFlwrs Just to confirm what Tom said, check out this thread that discusses the same issue and the commands needed to disable it: https://forums.fogproject.org/post/102522 Review the posts by @THEMCV they are enlightening to what may be causing this issue.

dhcp general settings on LAN: dhcp settings on other VLAN:

@jjsplitter Since you still had firewalld enabled, did you remember to set selinux to permissive? If not you will have a sad time when you try to capture an image.

Just cross-linking this here: https://forums.fogproject.org/topic/10615/ipxe-booting-possibly-broken-on-os-x-sierra-update

@Tom-Elliott this fixed the issue! Thank you very much!

@craigcoulson said in Debian + svn = error: nevermind all - i rebuilt the server with only minimal packages and re-ran the svn install of Fog and it worked fine - go figure. Glad to hear you got it working ;)

@Tom-Elliott And you can’t calculate all the hours you’ve saved for other admins.

@fdrouard wol/wol.php path no longer exists.

@Sebastian-Roth said in Impossible to boot on PXE......: Wireshark filter bootp && tftp is great for this This has been in the wiki for some time, here: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_TFTP

Ok thanks so i will write a expect script to install fog automaticly

I have solved this thread because as @Junkhacker stated, this is fixed in the dev builds as I am not using gzip compression on the page at all any more. If you are worried about the display, please update to Dev.

@Omanimous said: Changed Option 67 in DHCP to undionly.kkpxe and it seems to be working fine. lol glad you got it working. I’m sure it will be fine. In the future, when you have network booting issues, the boot file should always be your first thing to inspect and think about :-)