[SOLVED] OS deployment: No valid IP address error
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
In fact, the BIOS itself can sometimes retrieve an IP address...
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
However, I can confirm that with the latest version of WinPE, certain types of hardware are no longer supported. To test this, I used a very old version of WinPE:
C:\Users\username\Downloads\tis-wads-requirement-minimal-x64_10.1.25398.1-36_windows_PROD\amd64\en-us
https://wapt.tranquil.it/store/fr/wapt/ ... _PROD.wapt
But I can confirm that ipconfig must display an IP address (it's mandatory).
C:\Users\username\Downloads\tis-wads-requirement-minimal-x64_10.1.25398.1-36_windows_PROD\amd64\en-us
https://wapt.tranquil.it/store/fr/wapt/ ... _PROD.wapt
But I can confirm that ipconfig must display an IP address (it's mandatory).
I'm sorry, but I'll need some explanation on how it works.
We launched an OS deployment on one machine, on a second machine we did a ping -t to the machine being deployed (sorry for the image quality).
During these phases, the ping is OK.
I suppose we're still in the PXE phase; everything is OK for the moment.
Then, at this stage, the ping fails and the ipconfig command returns nothing.
At this stage the machine attempts to download the network drivers from the WAPT server, is that correct?
We launched an OS deployment on one machine, on a second machine we did a ping -t to the machine being deployed (sorry for the image quality).
- 1.png (250.71 KB) Viewed 12138 times
- 3.jpg (85.27 KB) Viewed 12138 times
I suppose we're still in the PXE phase; everything is OK for the moment.
Then, at this stage, the ping fails and the ipconfig command returns nothing.
- 4.jpg (77.53 KB) Viewed 12138 times
Last edited by clafon on Dec 16, 2025 - 17:14, edited 1 time.
I'm adding information as I discover more...
Affected machines:
HP PROBOOK 650-G5 (hardware purchased in 2020)
LENOVO THINKPAD P16v GEN3 ( hardware purchased in December 2025)
With the package:
- tis-wads-requirement-minimal-x64 in v10.1.25398.1-36 - OS deployment: OK
- tis-wads-requirement-minimal-x64 in v10.1.26100.2454-40 - OS deployment: OK
- tis-wads-requirement-minimal-x64 in v10.1.28000.1-40 - OS deployment: NOK
The latest version of wads-requirement seems to be the source of all the problems.
Affected machines:
HP PROBOOK 650-G5 (hardware purchased in 2020)
LENOVO THINKPAD P16v GEN3 ( hardware purchased in December 2025)
With the package:
- tis-wads-requirement-minimal-x64 in v10.1.25398.1-36 - OS deployment: OK
- tis-wads-requirement-minimal-x64 in v10.1.26100.2454-40 - OS deployment: OK
- tis-wads-requirement-minimal-x64 in v10.1.28000.1-40 - OS deployment: NOK
The latest version of wads-requirement seems to be the source of all the problems.
Last edited by clafon on Dec 16, 2025 - 5:03 PM, edited 3 times.
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hi Cédric,
WinPE must have started initially because spnonly.efi is downloaded using the network driver integrated into the UEFI layer. WimBoot, which is downloaded afterward, along with the bootloader and the WIM image, must also go through this same UEFI driver.
It seems that in your case, the driver isn't recognized in the WinPE image, which is why there's no address in ipconfig even though the machine booted over the network.
The Wapt version update includes an update for IPXE and WimBoot, but it shouldn't affect the WinPE drivers. However, if you've updated wads-requirement-minimal, there was a recent update from Microsoft that we've integrated, and that might help get things working.
However, the latest version of Microsoft WinPE has dropped support for a lot of older hardware, so we'll probably have to allow both to be used simultaneously.
Regards,
Denis
WinPE must have started initially because spnonly.efi is downloaded using the network driver integrated into the UEFI layer. WimBoot, which is downloaded afterward, along with the bootloader and the WIM image, must also go through this same UEFI driver.
It seems that in your case, the driver isn't recognized in the WinPE image, which is why there's no address in ipconfig even though the machine booted over the network.
The Wapt version update includes an update for IPXE and WimBoot, but it shouldn't affect the WinPE drivers. However, if you've updated wads-requirement-minimal, there was a recent update from Microsoft that we've integrated, and that might help get things working.
However, the latest version of Microsoft WinPE has dropped support for a lot of older hardware, so we'll probably have to allow both to be used simultaneously.
Regards,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
I simply think that version 10.1.28000 no longer includes certain drivers and that they need to be added when generating WinPE.
This is the same procedure we have been using from the beginning; as mentioned, we manually added the LOS drivers from the WinPE generation.sfonteneau wrote: ↑Dec 16, 2025 - 4:52 PMI simply think that version 10.1.28000 no longer includes certain drivers and that they need to be added when generating WinPE.
@sfonteneau @dcardon
I understand your feedback, but we tested with both older equipment (purchased in 2020) and newer equipment (purchased in December 2025).
We also manually added the network drivers for the equipment when we created the WinPE installation.
The latest version of the WADS package seems to be causing the problem.
I understand your feedback, but we tested with both older equipment (purchased in 2020) and newer equipment (purchased in December 2025).
We also manually added the network drivers for the equipment when we created the WinPE installation.
The latest version of the WADS package seems to be causing the problem.
