[RESOLVED] WAD Deployment - No more network devices

[Vercingetorix]

Hello,
we are trying to deploy Windows 11 on our PCs using WADs.
Our setup consists of a primary server on one LAN
and a secondary repository on another LAN.
We have a DHCP server on each LAN.

When we try to upload the image to the primary server via IPXE from a PC on the secondary repository's LAN, we get the following results:
The IP address assigned by DHCP is indeed on the secondary repository's LAN.
The ipxe.efi file is successfully downloaded from the primary server, and this happens twice!

We get a message:
IPXE initializing devices ok.

Then it goes wrong:
FEATURES: DNS HTTP ISCSI TFTP VLAN SRP AoE EFI Menu

No more network devices
could not boot image: Error 0x7f048207 (https://ipxe.org/0x7f048207)
No more network devices.

Can you help us with this problem?
As a follow-up question, do we need to point the "Boot Server Hostname" to the main server in DHCP?

Thank you in advance for your help.
Have a good day.

[dcardon]

Hi Marc,

could you try replacing the ipxe.efi file with snponly.efi [1]?

snponly.efi is based on the EFI BIOS network drivers and works better. Now, ipxe.efi should only be used on machines that don't support snponly.efi.

Regards,

Denis

[1] https://www.wapt.fr/fr/doc/wapt-wads.ht ... ftp-server

[Vercingetorix]

Hello,
where can I find the snponly.efi file?
I only have undionly.kpxe and ipxe.efi in /var/www/wads/pxe.
Do we need to download the tis-compile-ipxe package for this?
Thank you in advance for your help.
Have a good day.

[sfonteneau]

I only have undionly.kpxe and ipxe.efi under /var/www/wads/pxe.

Normally, if you are up to date, you should find the file in /opt/wapt/wads/pxe/snponly.efi

Latest version of wapt: 2.5.5.15697 (20422a0b)

[Vercingetorix]

Hello,
I should have started with this: we're on version 2.4...
So can we use SnOnly with this version?
Thank you.

[sfonteneau]

Hello,

the best solution would be to upgrade. Otherwise, you can download the server's .deb file (version 2.5) and extract the file from it.

Simon

[Vercingetorix]

Hello,
we upgraded to version 2.5.
The result is:
a DHCP IP address,
NBP filename is spnonly.efi
...
NBP file downloaded successfully.
IPXE initializing devices... OK.


Then,


Nothing to boot: No such file or directory (https://ipxe.org).

At the DHCP level, we have rules 067 with:
EFI/Boot/bootmgfw.efi
http://xx.xx.xx.xx./api/v3/baseipxe?keymap=fr
http://xx.xx.xx.xx./api/v3/baseipxe?uef ... &keymap=fr.

Thank you in advance for your help.

[sfonteneau]

At the DHCP level, we do have rule 067 with:
EFI/Boot/bootmgfw.efi

I didn't understand that part of your message

If you are in spnonly.efi, you are normally not in "EFI/Boot/bootmgfw.efi".

Can you specify which DHCP server to use?

Alternatively, could you also send a screenshot of your DHCP configuration?

[Vercingetorix]

Hello,
this is a bit confusing for us.
Attached is our Windows 2019 DHCP configuration.

[Vercingetorix]

extended options