Using Fog Adv Menu to chainload WDS?
Just wondering if anyone has tried chainbooting Windows WDS?
Would be nice to get FOG and WDS sitting next to each other with iPXE lording over the netboot process.
I’ve tried to boot the Windows file from the Windows TFTP server tftp://10.0.0.100/boot/x64/pxeboot.com
but it just reports with the default iPXE message cannot boot.
Would this be possible at all?
I figured it would go into a loop trying to boot iPXE as DNS masq was turned on which was configured to pxeboot iPXE.
Autoboot seems to ignore iPXE and boot WDS even with dnsmasq turned on.
I didn’t think it would be as simple as that. Thanks :)
So if you run autoboot all works to the WDS? You could just add that as the call for the WDS menu entry.
Also as a follow up, when going into the iPXE shell and running Autoboot for the WDS it works correctly.
Just when trying to run the commands imgfetch, imgload or imgexec.
So I’m not sure where I’m going wrong?
I’m wondering if it has got to do with mixed mode? I honestly don’t know enough about Windows DHCP servers as I have never had to manage them before.
I found this that might be related?
I have been finding that I can attempt to download the files manually from a tftpclient on my computer but reports that it couldn’t write the file and reports a random port number from the windows server.
I have tested downloading from my Linux TFTP server with no problems at all.
@Tom Elliott - Firewall on the server? I don’t think that is an issue as I can boot to the WDS correctly when not using dnsmasq/ipxe
@Junkhacker - I’ve read that but from what I understand that is just installing winpe onto my own server and not chain loading an existing one? I don’t have access to any of the Windows files on the existing WDS server or the default Windows Images that it creates.
Is the windows firewall process running?