Wapt client update

Questions about WAPT Packaging / Requests and help regarding Wapt packages.
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
Gaelds
Messages: 254
Registration: Nov 22, 2015 - 08:37

November 28, 2016 - 11:10

Good morning,

I'm having a problem deploying the latest wapt client (3 weeks ago). Several hundred of my PCs successfully updated the wapt-upgrade package to version 1.3.8, but with the following message:

Code: Select all

Your current wapt version (1.3.5.0) is too old to be upgraded, a full waptagent.exe install will be planned for Mon Nov 07 17:11:43 2016
waptexit is running, scheduling a one time task at system startup with command c:\windows\temp\waptdeploy.exe --hash=e9920bc1e5502f846a90715457e281b009d77aa2a79c2eda1180e296006206ac --waptsetupurl=c:\windows\temp\waptagent.exe --wait=15 --temporary --force --minversion=1.3.8.2
Information?: la t?che planifi?e "fullwaptupgrade" sera cr??e sous le nom d'utilisateur
("AUTORITE NT\SYSTEM").
Op?ration r?ussie : la t?che planifi?e "fullwaptupgrade" a ?t? cr??e.
When I look at the scheduled tasks, the "fullwaptupgrade" task is running, but the 1.3.8 client isn't installing. For example, in a room with 11 identical PCs, 3 have successfully upgraded to 1.3.8, but the rest are stuck on 1.3.5.

And on approximately 90 PCs, I still have client 1.2.3.2 active with the following message after installing the latest wapt-ugrapde package:

Code: Select all

Your current wapt version (1.2.3.2) is too old to be upgraded, a full waptagent.exe install will be planned for Tue Jul 05 10:16:31 2016
waptexit is running, scheduling a one time task at system startup with command c:\windows\temp\waptdeploy.exe --hash=e7deadf35ba854c8a25f47c49fa7f5dbd93dcbc927db64abc18ada354ffb526c --waptsetupurl=c:\windows\temp\waptagent.exe --wait=15 --temporary --force --minversion=1.3.5.0
Information?: la t?che planifi?e "fullwaptupgrade" sera cr??e sous le nom d'utilisateur
("AUTORITE NT\SYSTEM").
Erreur?: Impossible de cr?er un fichier d?j? existant.

Erreur?: la t?che "fullwaptupgrade" ne fonctionnera peut-?tre pas car les informations de compte ne peuvent pas ?tre d?finies.
INFO?: le fichier de t?ches v1 est en cours de suppression.
For now, the only workaround I've found is to manually reinstall the Waptagent on these machines or right-click on the WaptTray and launch the client update.
High
Locked

Return to “WAPT Packages”


  • To go further with WAPT