Tranquil IT Forum

Hello,

I have a question that I haven't been able to find the answer to in the 1.7 documentation...:

In WAPT version 1.5, if I remember correctly, when I added a package to a machine from the console and then clicked "save," the actions on the machine were as follows: upon shutdown: downloading of pending packages -> installation of packages -> updating of the machine package -> shutdown.

Since WAPT 1.7, it seems to be different: when I add a package to a machine and then click "save," the actions are:
- immediately : loading of the package onto the machine (the console displays "download of ...")
- upon shutdown: installation of packages -> updating of the machine package -> shutdown.

The drawback of the immediate "download of" is that it uses the user's bandwidth while they are on the machine. Is this the default behavior, or have I set an incorrect option in my wapt-get.ini file on my clients?

Is it possible to change this behavior?

Thank you.

Hello Jonattend,

Jonattend wrote: ↑May 2, 2019 - 4:10 PM On WAPT version 1.5, if I remember correctly, when I add a package to a machine from the console and then click "save," the actions on the machine are as follows: upon shutdown: downloading of pending packages -> installation of packages -> updating of the machine package -> shutdown.

Since WAPT 1.7, it seems to be different: when I add a package to a machine and then click "save," the actions are:
- immediately : loading of the package onto the machine (the console displays "download of ...")
- upon shutdown: installation of packages -> updating of the machine package -> shutdown.

The drawback of the immediate "download of" is that it uses the user's bandwidth while they are on the machine. Is this the default behavior, or have I set an incorrect option in my wapt-get.ini file on my clients?

Is it possible to change this behavior?

I haven't been able to reproduce this problem on my test infrastructure running version 1.7.4RC. I assume you're clicking the "Save" button and not "Save and Apply"? I also haven't been able to reproduce it on 1.7.3.5 in production. Does this happen on all machines? Have you set up any scheduled tasks that force the upgrade?

Sincerely,

Denis