bypass "trigger_action.sh"

[Floflobel]

Good morning,

Very happy that this new version is available in a stable release. I immediately updated a test machine and upon reaching the end of the documentation, I saw a small message:

Installing WaptUpgrade on Clients:

In version 1.5, it is no longer possible to contact clients prior to version 1.5 from the WAPT console.

To allow you to install the WaptUpgrade package on version 1.3, we have created a small script.

My workstations are not on the same network; I operate as follows:
- The client workstation contacts the server when it shuts down
- The client workstation restarts every night at 2 AM and updates at that time

How can I enable the update of my workstations to version 1.5?

[dcardon]

Good evening Floflobel,

Very happy that this new version is available in a stable release. I immediately updated a test machine and upon reaching the end of the documentation, I saw a small message:

Installing WaptUpgrade on Clients:
In version 1.5, it is no longer possible to contact clients prior to version 1.5 from the WAPT console.
To allow you to install the WaptUpgrade package on version 1.3, we have created a small script.

My workstations are not on the same network; I operate as follows:
- The client workstation contacts the server when it shuts down
- The client workstation restarts every night at 2 AM and updates at that time

How can I enable the update of my workstations to version 1.5?

The trigger_action.sh script will prompt the workstations to update immediately by connecting to port 8088, which was opened by the WAPT agent on workstations running version 1.3. If the workstations are unreachable (e.g., behind a NAT), they will update naturally with the normal WAPT update cycle if the waptupgrade package has been successfully assigned to all of these workstations.

Sincerely,

Denis

[Floflobel]

Yes, I had regenerated a certificate, so the wapt-upgrade package wouldn't install. Everything is working now, thank you.