[SOLVED] : iPXE and WDS Config

[Sha0]

You might be interested in omitting the WDS interaction and simply booting the Windows PE environment using wimboot, using this article.

However, if you are really interested in a hand-off to WDS...

Microsoft's Windows NBP cares about the DHCP packets that have been stored according to the PXE specification. In a WDS scenario, it is usually the case that there is a stored packet of the DHCP server's offer as well as a stored packet of the proxyDHCP server's offer.

You need to modify the proxyDHCP packet before handing control to the Windows NBP. You can do this from the iPXE CLI or a script:

Code:

set proxydhcp/next-server AAA.BBB.CCC.DDD
set proxydhcp/filename startrom.n12
set proxydhcp/dhcp-server AAA.BBB.CCC.DDD

Note #1: A proxyDHCP offer must have been sent in order for you to be able to access the proxydhcp/ scope shown above. That usually means having the proxyDHCP service running.

Note #2: The Windows NBP most likely uses its own internal TFTP client, so it won't fetch files using iPXE's HTTP support.

But since you are doing iPXE -> PXELINUX, you can also use Gene Cumm's pxechn.c32 module. It has a variety of options that are documented in Syslinux' doc/pxechn.txt file. Gene's considerations included the WDS use-case.