Page 1 of 1

Waptserver and package updates

Published: July 13, 2015 - 11:59 PM
by markham
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.

Re: Waptserver and package updates

Published: July 15, 2015 - 7:27 PM
by sfonteneau
Good morning
markham wrote:
New waptserver user who will eventually manage a fleet of workstations,
I have some questions about managing client package updates.
Welcome ;)
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 you install, for example, "tis-firefox_39.0-15_all.wapt", you are actually installing "tis-firefox".
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"
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?
In this case, it's best to create a package with the version number in the package name:

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...

Re: Waptserver and package updates

Published: July 16, 2015 - 4:58 PM
by markham
Thank you for your reply