Hello everyone,
following the latest version upgrade, I'm having trouble deploying the
PXE boot OS: OK
on the console:
Init installation boot 17:28:47 02/02/23
, so the machine boots correctly
. However, once WinPE starts, a brief DOS window appears and then disappears.
I had to record in slow motion to see the error/warning message: "
Trying to get hash signatures from server...
checking if JSON signer certificate is trusted..."
Then the window closes
and the deployment stops.
I should mention that I've updated ADKWinPE, etc., and installed wads-requirement-minimal-x64 and wads-requirement-minimal-x86.
The WinPE upload also went smoothly on the WAPT server.
Regards
[RESOLVED] OS deployment following update 2.3
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 :
Hello,
thank you for your reply.
Indeed, after updating WinPE on the server, the DOS window remains open in the foreground with the error, which allowed me to see that it's now the network layer that's malfunctioning. It works perfectly throughout the PXE boot process (I can ping the machine with -t), but as soon as the mini Windows boot screen starts, I lose network connectivity.
So I tested it with another machine, and it works fine. :phew (I was afraid I'd broken everything).
I'll try to investigate further why the TCP stack is no longer working (ipconfig no longer displays anything). Have
a good day everyone.
Regards
thank you for your reply.
Indeed, after updating WinPE on the server, the DOS window remains open in the foreground with the error, which allowed me to see that it's now the network layer that's malfunctioning. It works perfectly throughout the PXE boot process (I can ping the machine with -t), but as soon as the mini Windows boot screen starts, I lose network connectivity.
So I tested it with another machine, and it works fine. :phew (I was afraid I'd broken everything).
I'll try to investigate further why the TCP stack is no longer working (ipconfig no longer displays anything). Have
a good day everyone.
Regards
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Yes, indeed, IPXE has its own network layer.
WinPE also has its own network layer.
In my opinion, your WinPE is simply missing the network drivers.
WinPE also has its own network layer.
In my opinion, your WinPE is simply missing the network drivers.
