Tranquil IT Forum

WAPT version: 2.2.1.11957
Server OS: Linux Debian 11
Administration machine OS: Windows Server 2012R2


Hello,

I'm encountering a problem deploying an OS via WADS. I want to deploy an OS from a remote site (a remote repository PC running Windows 10).

The WADS option is enabled on the repository rule for the site in question. The tftpd server is also installed on the remote PC (running Windows 10). The remote repository is up to date and has the wads folder in its directory structure. It is configured for HTTP.

However, when I try to deploy the OS, I get the following error when running the command: "start x:\dlls\wgetwads64.exe --verify-cert=0 --server-url=https://

Error getting wads executable from server: THttpClientSocket.WGet:

Indeed, this directory structure doesn't seem to be present on the remote repository.

Note that the deployment works correctly if I uncheck the WADS option on the remote repository (and therefore the downloads are done directly from the WAPT server).

Good morning
This is not but Indeed, the WAPT server will redirect to the secondary repository address

Did you reinstall WinPE after the update?
There have been some changes

Yes, but it's the secondary repository rule that determines this variable.

When the "WADS" option is unchecked in the repository rule, it points directly to the WAPT server and the deployment works (but it's not optimized because downloads are slow).

However, when I check the "WADS" option in the repository rule, it applies the name of the secondary repository to the variable during deployment (and therefore the failure mentioned in my first message).

How can I make the ISO download from the remote repository?

(WinPE is up to date)

I can confirm that there is indeed an issue since the last version.

We are fixing it quickly.

Thank you for your feedback.

Fixed with the latest release 2.4.0.14143; Tested OK