Post Reply 
Thread Rating:
  • 1 Vote(s) - 3 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[SOLVED] : iPXE and WDS Config
2012-11-08, 20:22 (This post was last modified: 2012-11-08 21:03 by Sha0.)
Post: #2
RE: iPXE and WDS Config
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:
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.
Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
RE: iPXE and WDS Config - Sha0 - 2012-11-08 20:22
RE: iPXE and WDS Config - Sedorox - 2012-11-09, 04:31
RE: iPXE and WDS Config - Alphakarem - 2012-11-09, 15:09
RE: iPXE and WDS Config - Alphakarem - 2012-11-11, 01:09
iPXE and WDS Config - sebus - 2016-02-04, 11:26

User(s) browsing this thread: 1 Guest(s)