Page 1 of 1
Automatic update
Published: March 24, 2026 - 11:39
by mathieu081092
Hello,
I am currently testing the solution and would like to deploy the latest version of Chrome to several workstations.
I downloaded the package from the private repository and installed it on the machines in question.
When a new version is available, will the agent installed on the workstations automatically retrieve the update from the private repository to update Chrome without any intervention on my part?
Or will manual action be required for each new version?
Installation details:
WAPT version: Enterprise version 2.6.1.17765
Server OS: Windows 2022
Console machine OS: Windows 11
Sincerely,
Re: Automatic update
Published: March 25, 2026 - 09:36
by sfonteneau
Good morning
mathieu081092 wrote: ↑March 24, 2026 - 11:39
When a new version is available, will the agent installed on the machines automatically retrieve the update from the private repository to update Chrome without any intervention on my part?
Or will manual action be required for each new version?
The only thing you need to do on your end is to import the new version into your private repository to validate it
Re: Automatic update
Published: April 7, 2026 - 1:39 PM
by mathieu081092
Hello,
Thank you for your feedback.
Once the new version is deployed to the repository, the VMs correctly detect its availability and change to a "Need to upgrade" status. However, manual action is still required to trigger the update on the VMs.
Can you confirm if this is the expected behavior?
Thank you,
Best regards
Re: Automatic update
Published: April 7, 2026 - 2:53 PM
by dcardon
Hi Mathieu,
by default, a machine will install its updates upon shutdown using waptexit. If these are VMs that are never restarted, you need to determine the strategy you want to implement.
Updates can be forced from the server (you select the machine in the console and force the update).
You can also create a scheduled task that launches waptexit or runs the command `wapt-get -U upgrade`.
You'll need to consider the software already running and see the expected behavior (forced application shutdown for updates, waiting for shutdown, etc.).
If it's for Windows updates, you can also run a scheduled task like `wapt-get waptwua-install`.
Or simply restart the machine; this will force the default behavior.
In short, there's no perfect time to perform updates; you just need to choose the most suitable time for you.
Best regards,
Denis
Re: Automatic update
Published: April 14, 2026 - 3:23 PM
by mathieu081092
Hello Denis,
Thank you for your feedback.
Despite restarting the VM to perform an automatic upgrade test of KeePass from version 2.59 to 2.61, it is not working.
Sincerely,
Mathieu
Re: Automatic update
Published: April 14, 2026 - 4:50 PM
by dcardon
Hi Mathieu,
images hosted on third-party temporary sites are not recommended for a forum (the goal is to have content that can be viewed over time), so please upload them directly to the post (see the attachments tab). Could you add them directly?
Regards,
Denis
Re: Automatic update
Published: April 14, 2026 - 6:13 PM
by mathieu081092
Hello Denis,
Please excuse me, I wasn't aware.
It's done now.
Have a good rest of the day,
Mathieu
Re: Automatic update
Published: April 15, 2026 - 11:40 AM
by sfonteneau
Hi Mathieu,
package wapt assigned to it and installed?
Simon