waptupgrade - Clients not updated

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

May 22, 2017 - 1:36 PM

As with every update of the WAPT client, some PCs in my network are not updating. My server has been on version 1.3.12 for a few days, but I still have 250 PCs on an older version (3.9.3, 1.3.8.2, or 1.3.5.0)

The status of the dst-waptupgrade package is "OK" on these machines, but here is an example log:

Code: Select all

Your current wapt version (1.3.8.2) is too old to be upgraded, a full waptagent.exe install will be planned for Fri May 05 17:20:38 2017
waptexit is running, scheduling a one time task at system startup with command c:\windows\temp\waptdeploy.exe --hash=88556f5b8da1ad523b12cb0fa613cff8afe06ac7025b672079c9357fbca4ff41 --waptsetupurl=c:\windows\temp\waptagent.exe --wait=15 --temporary --force --minversion=1.3.12.13
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.
The PCs have been restarted several times since, but apparently the agent installation is not working...
High
Locked

Return to “WAPT Packages”


  • To go further with WAPT