Windows HTTP iPXE Setup

[gmcl]

Hi all,

I am new to this forum and I am having trouble setting up WinPE via HTTP using IIS.

So far I have added roles IIS and DHCP to my VM Win Server. I have followed http://ipxe.org/howto/winpe by extracting the wimboot file into my http folder 'C:\inetpub\wwwroot\ipxe'. I have ensured that this directory is shared and directory browsing is enabled within IIS Manager. I can browse the files within IE.

I have the iPXE file iPXE.KRN extracted from iPXE.iso and placed in the same inetpub\wwwroot\ipxe directory too. BCD, boot.sdi and the boot.wim files are all there also. As stated in the documentation I have created a boot.ipxe file. The contents of this reads:
#!ipxe

cpuid --ext 29 && set arch amd64 || set arch x86
kernel http://192.168.0.2/ipxe/wimboot
initrd http://192.168.0.2/ipxe/BCD BCD
initrd http://192.168.0.2/ipxe/boot.sdi boot.sdi
initrd http://192.168.0.2/ipxe/boot.wim boot.wim
boot

I have configured option 67 to http://192.168.0.2/ipxe/boot.ipxe in DHCP server config options.

Documentation states,
'Boot using iPXE from the URI of your boot.ipxe script, e.g. http://my.web.server/winpe/boot.ipxe. You should see iPXE download and boot Windows PE via HTTP'
But unfortunately I can not for the life of me get this to start iPXE. DHCP offer is received but nothing else and results in a timeout. I am testing this through Hyper-V VMs and both UEFI and BIOS generations have been tested just in case...

Any help or advice on how to setup this WinPE via HTTP (using iPXE) is greatly appreciated. Thanks in advance

[MultimediaMan]

It is probable that you are having problems with the PXE part of all of this.

Where is your TFTP server and what is in the root of the TFTP directory? (You need TFTP to load undionly.kpxe or something similar...)

[NiKiZe]

(2016-09-15 17:13)gmcl Wrote:  I have the iPXE file iPXE.KRN extracted from iPXE.iso and placed in the same inetpub\wwwroot\ipxe directory too.

It is not possible to run a "linux kernel" (the ipxe.lkrn) from a standard PXE environment.
For Legacy bios you probably want undionly.kpxe
And for efi you want ipxe.efi

Let's start with doing one of those and see that it works so far, before going into the autodetection of which files to send. But you can find the basic stuff about this at http://ipxe.org/howto/chainloading

(we need to have ipxe working before worrying about the wimboot step)