Tranquil IT Forum

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

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.

Good morning,

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)

Guillaume