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).
[SOLVED] OS - WADS Deployment Issue
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 :
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
Code: Select all
<nom du PC dépôt>:80/api/v3/get_wads_exe/<ip du PC à déployer>/wads64.exeCode: Select all
<nom du PC dépôt>Code: Select all
<srvwapt>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)
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)
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
I can confirm that there is indeed an issue since the last version.
We are fixing it quickly.
Thank you for your feedback.
We are fixing it quickly.
Thank you for your feedback.
