Problem with WAPT executables after updating from 1.5.1.26 to 1.6

[Gaelds]

Hello,
I just updated my WAPT server from version 1.5.1.26 (Debian) to version 1.6. This latest version is correctly indicated on the server's web page, but the executable I download there, waptserver-tis.exe, is still version 1.5.1.26, and perhaps wapt-deploy as well?

[Gaelds]

I just managed to fix it by manually downloading the executables here: https://wapt.tranquil.it/wapt/
But where could this update problem be coming from?

[Gaelds]

I'm still missing waptagent.exe on my server. Even though the waptupgrade package installs version 1.6 correctly, I'd like to be able to install it manually.

[dcardon]

Hello Gaelds,

I'm still missing waptagent.exe on my server. Even though the waptupgrade package installs version 1.6 correctly, I'd like to be able to install it manually.

The waptagent.exe file is recreated along with the xyz-waptupgrade package. It should be up to date.

There was an old bug a long time ago with symbolic links in the WAPT directory. Could you check in the /var/www/wapt or /var/www/html/wapt directory to see if there's a symbolic link between waptagent.exe and tis-waptsetup.exe, or something similar?.

Sincerely,

Denis

[Gaelds]

If I'm using the correct command under Linux, there shouldn't be any symbolic links in these directories:

root@srv-wapt:/var/www/wapt# find /var/www/wapt -type l
root@srv-wapt:/var/www/wapt# find /var/www/html/wapt -type l
root@srv-wapt:/var/www/wapt# find . -type l
root@srv-wapt:/var/www/wapt#

[Gaelds]

I don't know if the waptdeploy.exe file I downloaded from https://wapt.tranquil.it/wapt/ is the correct one? Two-thirds of our domain workstations have been updated to 1.6.2.7, but about twenty remain on 1.5.1, even though the scheduled task was correctly created by the waptupgrade package and the GPO runs at each startup.

[sfonteneau]

If waptdeploy is run manually, is there an error?

[Gaelds]

On a Windows 10 PC stuck on version 1.5.1.26, I tried the following command:

Code: Select all

waptdeploy.exe --hash=2be31296ac8520884705df44d1caaee97532e617b6c913baa699f3fabf7c4da1 --minversion=1.6.2.7 --wait=15

who gave this back to me:

WAPT version: 1.6.2.7
WAPT required version: 1.6.2.7
Nothing to do
Update host status on the server

From the console, package 1.6.2.7 appears to be installed on the machine, with the following log:
Setting up upgrade from wapt version 1.5.1.26 to 1.6.2.7. waptagent install planned for Mon Nov 05 19:05:55 2018
waptexit is running, scheduling a one time task at system startup with command c:\windows\temp\waptdeploy.exe --hash=870171eb0428a1fd14fcf7bde530f416f05c2bdb7cd178ef4c495afa3643ca98 --waptsetupurl=c:\windows\temp\waptagent.exe --wait=15 --temporary --force --minversion=1.6.2.7
Information: The scheduled task "fullwaptupgrade" will be created under the username
("NT AUTHORITY\SYSTEM").
Operation successful: the scheduled task "fullwaptupgrade" has been created.

And there's no trace of the task in the planner.


On two Windows 7 64-bit laptops, I found the task in the task scheduler, but it had run unsuccessfully. The error message was "Constraint error in task definition." Based on the task constraints, I assume the PC wasn't plugged in when it started? And then it never ran again?


I also saw a Trend Micro message when a PC started up, during the automatic execution of waptdeploy. Officescan had blocked the installation from a temporary directory. I've never found the right way to exclude waptagent on the Trend server; when I manually install the agent, I have to unload Officescan before starting.

[sfonteneau]

"Constraint error in task definition"

We need to check the task parameters (it might not install if the device is running on battery)

[Gaelds]

Yes, that was one of the constraints that was checked, but is the task supposed to restart on the next power cycle?