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.
WAPT 1.5.21 to 1.7: Change in behavior?
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: 1931
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Jonattend,
Sincerely,
Denis
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?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?
Sincerely,
Denis
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
