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
WaptUpgrade and WaptExit Reactivation
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
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
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
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
Vincent CARDON
Tranquil IT
Tranquil IT
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
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
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
