Tranquil IT Forum

Hello,

we have just upgraded our server to version 1.7.3.5 and are preparing the agent migration. We do not use WAPTExit, and it was disabled after deploying agent version 1.6.2 with a nowaptexit package.
Unfortunately, when installing the waptugrade agent update package, created after the upgrade to 1.7, WAPTExit is re-enabled on the clients.
Is there a simple solution to disable it within the waptupgrade package?
In the case of this waptugrade package, shouldn't the activation of WAPTExit be tested to select the tasks?

I also tried the --tasks parameter of waptdeploy to select only the autorunTray and installService tasks, but without success...

Thank you

- Installed WAPT version: 1.7.3.5
- Server OS: CentOS 7.3
- Administration/package creation machine OS: Windows 7 SP1 32-bit

Hello,

With all the use cases we encounter with our clients, upgrading upon machine shutdown is the safest and cleanest method.

Perhaps not always, and we'd like to know why.

Could you explain your use case where WAPTexit would be undesirable?

Sincerely,

Vincent

Hello,

we've planned an intermediate solution.

When you launch a LibreOffice installation, for example, if your user shuts down their PC,
it needs to be possible to run waptexit to interrupt the shutdown and let the installation finish.

What you want is to prevent the upgrade from launching with waptexit when the machine shuts down.

Therefore, we've added an option to the wapt-get.ini file:

https://github.com/tranquilit/WAPT/blob ... t.pas#L397

Add the following to wapt-get.ini:

waptexit_disable_upgrade=True