Threaded Mode | Linear Mode

Wildfire3 · 2018-09-19, 09:21

Okay, I'm completely new to iPXE, but I know that this is what I'm looking for Smile

The problem is, I can't get it to work, I must be missing something but I can't fro life figure out what it is...

I've installed a new DHCP in my lab on it's own net so there is no interference from anything else.

On the DHCP I've also installed IIS.

So, what I wan't to do is to get WinPE to boot, nothing fancy at the moment but later it should connect to my MDT as well to install clients.

I have followed this guide to the letter; https://ipxe.org/howto/winpe using teh latest ADK from Microsoft.

I've added http://192.168.100.10/winpe/boot.ipxe as option 67 on my DHCP but nothing happens...

Do I need to do something else? The client gets an IP, so the DHCP responds.

Can add that everything runs in Hyper-V on Gen 2 clients with Secure Boot disabled.

***NiKiZe*** · 2018-09-19, 12:45

You need to be more specific about what works and what doesn't

My guess is that your DHCP does not give the correct info for network boot.
Hyper-V is horrible client to debug this, and windows DHCP service is horrible to configure.
If this is the state you are in then I would start doing packet capture with for example wireshark to figure out which information is in the DHCP traffic, and to see if there is any TFTP traffic.

Reading over your notes again I'm currious where you have added ipxe.efi or snponly.efi?
Please see https://2pintsoftware.com/whitepaper-usi...e-booting/ for some good pointers.

Wildfire3 · 2018-09-19, 14:49

(2018-09-19 12:45)NiKiZe Wrote: You need to be more specific about what works and what doesn't

My guess is that your DHCP does not give the correct info for network boot.
Hyper-V is horrible client to debug this, and windows DHCP service is horrible to configure.
If this is the state you are in then I would start doing packet capture with for example wireshark to figure out which information is in the DHCP traffic, and to see if there is any TFTP traffic.

Reading over your notes again I'm currious where you have added ipxe.efi or snponly.efi?
Please see https://2pintsoftware.com/whitepaper-usi...e-booting/ for some good pointers.

Hi!

I have done nothing more than following the guide I posted in the first post, created WinPE, copied wimboot to the webserver and added option 67 to my DHCP.

I have no ipxe.efi file or snponly.efi files.

Is the there a short step-by-step guide to follow on how to set it up?

***NiKiZe*** · 2018-09-19, 15:38

winpe is written with the assumption that you already have a basic environment working with iPXE as seen in https://ipxe.org/howto/chainloading
Seeing the only mention of DHCP on the winpe page I can understand that it is confusing.

You need to get a basic working iPXE environment up and running, you can also find several related posts on the forum for both windows DHCP configuration, and different wimboot issues.

Wildfire3 · 2018-09-20, 14:05

(2018-09-19 15:38)NiKiZe Wrote: winpe is written with the assumption that you already have a basic environment working with iPXE as seen in https://ipxe.org/howto/chainloading
Seeing the only mention of DHCP on the winpe page I can understand that it is confusing.

You need to get a basic working iPXE environment up and running, you can also find several related posts on the forum for both windows DHCP configuration, and different wimboot issues.

Thanks for the quick reply!

Is there a basic guide somewhere that I can follow to get started?

I've googled some but all I can find is when you have the basic environment up and running...

***NiKiZe*** · 2018-09-20, 20:23

(2018-09-20 14:05)Wildfire3 Wrote: Is there a basic guide somewhere that I can follow to get started?

What is missing from https://ipxe.org/howto/chainloading
That isn't covered by what is said in https://2pintsoftware.com/whitepaper-usi...e-booting/ ?

Windows DHCP is a mess, I'm sure there are attempts at guides out there but I don't know of any good ones.
There is also several explanations here on the forum, and you can always ask if there is any particular step that you are having issues with. There is also IRC, not very active, but as long as you stay connected you will get a reply eventually.