Hello,
a new WaptServer user who will eventually be managing a fleet of workstations.
I have a few questions about managing client package updates:
1) Are client packages deployed via WaptServer updated automatically and autonomously? (If Firefox version 18 is installed, will it automatically update to version 19 without operator intervention?)
2) For certain workstations, can a version be frozen? For example, an old Java application that only works with version 17.7 and not 18. Can the update of this package be prevented once the correct version is deployed?
Thank you.
Waptserver and package updates
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
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Good morning
When a new version is available in your private repository, there are then several ways to launch the installation.
- The client can automatically install the version when the workstation is shut down via waptexit (other installation methods are available):
- Update notifications available via the WaptTray, and updates can be launched by the user (convenient for users who never have time)
- Force the installation from the console using "Launch package installation"
Example:
"tis-java6-6.0.0.wapt"
Thus, the "tis-java6" version can be installed on a specific machine, and a tis-java package can be installed on other PCs. And so on...
Welcomemarkham wrote:
New waptserver user who will eventually manage a fleet of workstations,
I have some questions about managing client package updates.
When you install, for example, "tis-firefox_39.0-15_all.wapt", you are actually installing "tis-firefox".markham wrote: 1) Does the updating of client packages deployed via waptserver happen automatically and autonomously (if we install version 18 of Firefox, will it automatically update to version 19 without operator intervention)?
When a new version is available in your private repository, there are then several ways to launch the installation.
- The client can automatically install the version when the workstation is shut down via waptexit (other installation methods are available):
- Update notifications available via the WaptTray, and updates can be launched by the user (convenient for users who never have time)
- Force the installation from the console using "Launch package installation"
In this case, it's best to create a package with the version number in the package name:markham wrote: 2) For certain applications, can we freeze a version, e.g., an old Java application that only works with version 17.7 and not 18? Can we prevent the update of this package once the correct version is deployed?
Example:
"tis-java6-6.0.0.wapt"
Thus, the "tis-java6" version can be installed on a specific machine, and a tis-java package can be installed on other PCs. And so on...
