Post Reply 
Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
architecture getting confused - wds chainloading
2013-05-01, 15:15
Post: #3
RE: architecture getting confused - wds chainloading
(2013-04-26 17:49)robinsmidsrod Wrote:  It could be a possibility that iPXE or PXELinux does something that confuses WDS, but it seems unlikely. Maybe some of the more technical people on IRC might be able to help you figure out what's going on.

I would recommend using instead of the stock TFTP WDS setup for booting Windows PE, it is much faster.

Hi There,

Thanks for taking a look at this. Yeah it is a bit odd that wds only returns x86 boot images. I can post up the tftp logs if there is any interest on the forums, but quite happy to have a chat on irc.

I had conetmplated a bit of a cumbersome workaround. do an initial pxelinux with chooser for wds or everything-else. this will allow wds to carry on as usual. everything-else can then chain undionly.kpxe and based on the dhcp user class, return another pxelinux with the non-wds boot images.

Thanks for the winpe link - to be fair wds is not doing an awful lot (pretty much only tftp and booting up wim images) so this may be just the ticket!

Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
RE: architecture getting confused - wds chainloading - muzz - 2013-05-01 15:15

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