[SOLVED]PXE error: Nothing to boot: no such file or directory

Questions about WAPT Server / Requests and help related to the WAPT server
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
Locked
Erman
Messages: 3
Registration: June 9, 2022 - 1:58 PM

June 9, 2022 - 2:41 PM

Hello,

I'm trying to set up a deployment using WAPT 2.2. However, I'm encountering an error when my client PCs boot via PXE in BIOS:
Picture

And here's the error message when the clients are in EFI mode:
Picture

I'm using Windows Server for my DHCP (for DHCP settings, EFI: ipxe.efi / BIOS: undionly.kpxe).

I consulted the 2.2 documentation and this answer: viewtopic.php?p=9879#p9879

Thank you.
Last edited by Erman on June 15, 2022 - 08:36, edited 1 time.
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

June 13, 2022 - 11:31

For me, it's a DHCP configuration issue.

I've published the PowerShell commands directly if you'd like them:

https://www.wapt.fr/fr/doc/wapt-wads-tf ... hcp-server

You can delete the manually created configurations and then run the PowerShell commands on your DHCP server.
Erman
Messages: 3
Registration: June 9, 2022 - 1:58 PM

June 14, 2022 - 11:07

Hello,

Version: WAPT 2.2.1.11957
Server OS: Windows 2012 server
ISO distributed: Windows 10

You were right, it was a DHCP server issue. Now I'm facing another problem. I correctly register my PC with the WAPT server, the deployment starts, the CMD window displays this command, and then does absolutely nothing afterward. Do you have any suggestions?

Picture

I found this forum post viewtopic.php?t=2989 which corresponds to my problem, but I still haven't found a solution.

Regards,
Erman
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

June 14, 2022 - 11:15

You can rerun the last command that appeared (without the start button).

The start button actually allows you to use the French keyboard layout, but it also hides errors.
Erman
Messages: 3
Registration: June 9, 2022 - 1:58 PM

June 14, 2022 - 11:22

Hello,

I've encountered yet another error message. I think it's a problem with the ISO image...

Picture (open the image in a new tab to see it more clearly)


Regards,
Erman
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

June 14, 2022 - 12:31

Yes, indeed.

The hash of the downloaded ISO doesn't match the advertised hash.

Your Windows 10 ISO is only 3.1 GB? There might have been a problem during the ISO upload?

The filename, and therefore the URL, corresponds to the SHA256 hash, so clearly the file's hash doesn't match.

Therefore, either there was a problem during the upload, or there was a problem during the download via WADs.
Attachments
Capture.PNG
Capture.PNG (36.35 KB) Viewed 3847 times
Locked