Hello,
I'm currently testing WAPT Enterprise.
I've noticed some behavior that seems strange to me, given my understanding of how WAPT works: when I add a package to my test PC (which is powered on at the time), the package installs immediately. The system doesn't wait for WAPTExit to execute (i.e., for the PC to shut down) before making the changes. The same behavior occurs when uninstalling packages that conflict with each other (this happens with several different packages).
Is this behavior normal (I haven't found any information in the documentation or on this forum)? If so, is there a way to force installations/uninstalls to only occur when the machine is shut down?
Thank you in advance.
Guillaume
[RESOLVED] Immediate package installation
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
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello GF68,
there are two options in the console: saving a workstation configuration or applying a configuration. If you apply it, it saves the configuration and then tells the workstation to perform its update/upgrade.
If you simply save the configuration, you can run an update on the workstation so that it downloads the new package and applies it when the workstation shuts down.
By default, the WAPT agent checks every 1.5 hours for updates on the server and caches them locally. Then it installs the updates when the workstation shuts down.
there are two options in the console: saving a workstation configuration or applying a configuration. If you apply it, it saves the configuration and then tells the workstation to perform its update/upgrade.
If you simply save the configuration, you can run an update on the workstation so that it downloads the new package and applies it when the workstation shuts down.
By default, the WAPT agent checks every 1.5 hours for updates on the server and caches them locally. Then it installs the updates when the workstation shuts down.
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
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
Good morning,
Thank you for your reply!
To summarize, if anyone else has this problem, from what I understand:
Thank you for your reply!
To summarize, if anyone else has this problem, from what I understand:
- Checking for updates = caching available packages and installing them on shutdown
- Launch the installations = launch the installation of available packages as soon as possible (immediately if the target machine is powered on and available)
Server: WAPT Enterprise 2.4.0.14143 on Debian
Console: Windows 10
Infrastructure: Windows
Console: Windows 10
Infrastructure: Windows
