Page 1 of 1

waptupgrade - Clients not updated

Published: May 22, 2017 - 1:36 PM
by gaelds
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...