Hello, I'm having several problems with my WAPT server.
OS: Debian 11 Bullseye
Version: 2.3.0
Discovery version (after trying an enterprise license)
Console OS: Windows Server 2019
Console version: 2.3.0.13438
I upgraded from 2.3 to 2.3.13438 (modifying the apt file).
All packages have upgraded correctly according to dpkg, although the "debian-10" in the waptsetup file leaves me with some doubt:
ii tis-waptserver 2.3.0.13438-8e580896-debian-11-amd64 amd64 WAPT Server for machines software management.
ii tis-waptsetup 2.3.0.13438-8e580896-debian-10-amd64 all WAPT setup executable for Windows.
However, when I access the web interface of the server, I'm still on version 2.3.0:
WAPT Server Version: 2.3.0
WAPT Agent
Version: 2.3.0.13438 WAPT Setup Version: 2.3.0.13438
WAPT Deploy Version: 2.3.0.13438.
I tried `apt --reinstall`, but it didn't help.
In the console, I have another problem in the "Download and send agent installers" section. I get two "Package missing" errors for waptdeploy.exe and waptsetup.exe. If I delete the waptsetup agent and rebuild it, I get the error "Windows waptupgrade not yet supported". For waptdeploy, if I delete it, it disappears from the list and I have to download it (from Tranquil IT) and manually add it back to /var/www/wapt/waptagent/.
The last problem (which I think is related) is that I can no longer deploy the agent with waptdeploy via GPO.
Manually, the client retrieves the agent correctly, but then I get an "Unable to read file version" error. I have to use the --force option to deploy the agent on the client, and this would cause a problem if I included the option in the GPO script.
That's it. I hope I haven't forgotten anything and that I've been clear enough. If anyone has encountered this problem before, I'd be very grateful for any advice.
Thanks in advance
Bug update from version 2.3 to 2.3.0.13438
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
"Tools" generates a WAPT agent which is used to generate Windows. We need to do something to make the GUI clearer. We'll remove "Windows" from the list to avoid confusion.
Actually, that's normal; it's just that the web interface wasn't displaying the full version. I've just fixed that to avoid any confusionGreg wrote: ↑Jan 24, 2023 - 3:49 PM Hello, I have several problems on my WAPT server.
OS: Debian 11 Bullseye
Version: 2.3.0
Discovery version (after trying an enterprise license)
Console OS: Windows Server 2019
Console version: 2.3.0.13438
I upgraded from 2.3 to 2.3.13438 (modified the apt file).
All packages upgraded correctly according to dpkg, although the "debian-10" in the waptsetup file leaves me with some doubt:
ii tis-waptserver 2.3.0.13438-8e580896-debian-11-amd64 amd64 WAPT Server for machines software management.
ii tis-waptsetup 2.3.0.13438-8e580896-debian-10-amd64 all WAPT setup executable for Windows
Or when I go to the web part of the server I am still on 2.3.0:
WAPT Server version: 2.3.0
WAPT Agent version: 2.3.0.13438
WAPT Setup version: 2.3.0.13438
WAPT Deploy version: 2.3.0.13438
I tried an apt --reinstall but nothing works.
Normally the "Download and send agent installers" section was not originally intended to manage Windows since you have it in the menu.Greg wrote: ↑Jan 24, 2023 - 3:49 PM In the console, I have another problem in the "Download and send agent installers" section. I get two "Package missing" errors for waptdeploy.exe and waptsetup.exe. If I delete the waptsetup agent and rebuild it, I get the error "Windows waptupgrade not yet supported". For waptdeploy, if I delete it, it disappears from the list and I have to download it (from Tranquil IT) and manually add it back to /var/www/wapt/waptagent/.
"Tools" generates a WAPT agent which is used to generate Windows. We need to do something to make the GUI clearer. We'll remove "Windows" from the list to avoid confusion.
Regarding this last issue, we do indeed have a problem in the latest version; we will release a new one soon. In the meantime, you can use the waptdeploy from an older version of wapt.Greg wrote: ↑Jan 24, 2023 - 3:49 PM Last problem (related, I think): I can no longer deploy the agent with waptdeploy via GPO.
Manually, the client retrieves the agent correctly, but then I get an "Unable to read file version" error. I have to use the --force option to deploy the agent on the client, and this would cause a problem if I included the option in the GPO script.
That's it. I hope I haven't forgotten anything and that I've been clear enough. If anyone has encountered this problem before, I'd be very grateful for any help.
Thanks in advance
