Discussion:
[ipxe-devel] Problem with first steps in IPXE using wimboot
Vancek, Sascha (MSC)
2018-09-20 12:54:32 UTC
Permalink
Hello,

is it possible to get help on that issue ?
I set up a system with Win Server 2016 and running DHCP, IIS and WDS on it.
I build the undionly.kpxe by with an embedded script to chainload to this server and run a boot.ipxe script where wimboot should be run ( all 2 files in my Webroot)
If I perform a PXE boot with the client the undionly.kpxe is loaded and I get also the message:
http://192.168.1.1/boot.ipxe....OK
wimboot ... No such File or Directory ...

I added the mime type on my ISS ( * ; application/octet-stream ) but this did not help.


I didn found the solution in the forum for that.



Regards
Sascha Vancek

We continuously commit to comply with the applicable data protection laws and ensure fair and transparent processing of your personal data.
Please read our privacy statement including an information notice and data protection policy for detailed information on our website.
shouldbe q931
2018-09-27 15:32:29 UTC
Permalink
On Wed, Sep 26, 2018 at 6:44 PM Vancek, Sascha (MSC)
Post by Vancek, Sascha (MSC)
Hello,
is it possible to get help on that issue ?
I set up a system with Win Server 2016 and running DHCP, IIS and WDS on it.
I build the undionly.kpxe by with an embedded script to chainload to this server and run a boot.ipxe script where wimboot should be run ( all 2 files in my Webroot)
http://192.168.1.1/boot.ipxe....OK
wimboot … No such File or Directory …
I added the mime type on my ISS ( * ; application/octet-stream ) but this did not help.
I didn found the solution in the forum for that.
Have you checked the IIS logs ?

from bitter experience, I tend to use Apache or nginx (even on
Windows, unless the application requires IIS

Cheers

Loading...