[RESOLVED] Workstations that don't update in 2.0

Share your tips or issues concerning the WAPT Console or WAPT Agent here
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
mviale
Messages: 25
Registration: Apr 4, 2019 - 11:03

July 6, 2021 - 4:03 PM

Hello,

I migrated from Wapt Community 1.8 to Wapt Enterprise 2.0 last Thursday.
I have a few workstations that aren't updating despite running the waptupgrade package.
The logs don't show anything unusual:
Setting up upgrade from wapt version 1.8.2.7267 to 2.0.0.9428. waptagent install planned for Mon Jul 5 19:57:54 2021
Information: The scheduled task "fullwaptupgrade" will be created under the username
("NT AUTHORITY\SYSTEM").
Operation successful: The scheduled task "fullwaptupgrade" has been created.


Similarly, after rebooting the machine, I have about 20 workstations like this, while 1450 have successfully migrated to 2.0.

Has anyone else encountered this problem?

Mathieu
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

July 7, 2021 - 10:30

Hi Mathieu,

For the WAPT update, the agent creates a scheduled task that launches the upgrade one or two minutes after the package is installed. Therefore, the task scheduler needs to be working correctly. There are cases where the Windows task scheduler is malfunctioning on the machine.

Could you call support to share your screen and see the problem?

It makes me think we might need to add a check that the scheduled task service is running properly on the machine before creating the task.

Thanks, :-)

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
mviale
Messages: 25
Registration: Apr 4, 2019 - 11:03

July 7, 2021 - 11:34

Hi Denis,

I checked with support and noticed that it only affected laptops, and the scheduled task is configured to run only when the machine is plugged into the mains.
By forcing a reinstall and plugging it into the mains, it works. :)

- Mathieu
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

July 7, 2021 - 4:40 PM

Hi Mathieu,

Thanks for your feedback!

The fix has been implemented and will be available in the next version, 2.1. We'll try to release it soon. :-)

See you soon,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Locked