WAPT Version: 2.6.1.17567
Server OS: Debian 12
Administration Machine OS: Windows Server 2019
Target Machine OS: Windows 11
Hello,
We just received new laptops (Lenovo ThinkPad P16v Gen3 model) and are trying to deploy a Windows 11 OS via WAPT.
We have successfully retrieved the network card drivers and put them in WinPE.
We can boot from PXE but get the following error:
VerifyCert: X:\SSL\server\server.crt
No Valid IP address found.
When we search the forum or the internet, this error message often comes from missing drivers, but that's not the case because they have been successfully retrieved. Do you have any ideas?
Thank you.
[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 :
Once WinPE is running, you can check with ipconfig in a command prompt.
If no interface appears, it's a driver issue.
If no interface appears, it's a driver issue.
Thanks for your feedback Simon,
we just realized that we can no longer deploy OS at all, even on "old" machines that were working...
On the DHCP server we can see the machines and an IP address is correctly assigned to them.
we just realized that we can no longer deploy OS at all, even on "old" machines that were working...
On the DHCP server we can see the machines and an IP address is correctly assigned to them.
Last edited by clafon on Dec 16, 2025 - 11:52, edited 1 time.
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
We updated the tis-wads-requirement-minimal-x64 package to version 10.1.28000.1.
Perhaps the new version of WinPE doesn't work as well with older PCs:
https://learn.microsoft.com/fr-fr/windo ... ember-2025
Perhaps the new version of WinPE doesn't work as well with older PCs:
https://learn.microsoft.com/fr-fr/windo ... ember-2025
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
sfonteneau wrote: ↑Dec 16, 2025 - 11:03 Once winpe is started, in a cmd you can check with ipconfig.
You did not answer me on this subject.
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
On a working machine, WinPE will always return an IP address (it's impossible for it to return nothing on a working machine). I just tried it.
I upgraded the Wapt server to version 2.6.1.17576 (just in case).
The workstations are correctly assigned IP addresses (reservations are present in the DHCP server)... but at the beginning of the PXE boot process... I get the error "No Valid IP Address found."
I'm completely baffled.
The workstations are correctly assigned IP addresses (reservations are present in the DHCP server)... but at the beginning of the PXE boot process... I get the error "No Valid IP Address found."
I'm completely baffled.
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
If you're starting an IPXE server, it's quite possible that the IPXE server itself will get an IP address, but WinPE won't.
Are you starting with an IPXE server?
Are you starting with an IPXE server?
