Test your WDS

After going through all the Syslinux steps and importing a Windows client into your WDS, you should be able to actually deploy Windows 10. Not automated of course, but it should work.

Before we continue

If you haven't done so before, it might be handy to disable the F12 Boot Policy option on your WDS-server and put it as "Always continue the PXE boot".

Here we go!

This is the time to troubleshoot:

My client is getting an IP from the DHCP. I still have to press F12 to continue.

My custom boot menu loads. Again, this screenshot is made from my finished lab. Hence why there's many more options and the image of a cake.

After selecting "Windows Deployment Services". My WDS server goes to "pxeboot.0", the original WDS-boot file and loads up my Windows 10 boot image. I advice you to complete this deployment to be absolutely sure you didn't b0rk up your WDS

If all that went well, we can move on to the Linux deployments!