Page 1 of 1
Prevent a package from updating on a single machine
Published: February 5, 2020 - 5:11 PM
by realynot
Hello everyone,
I need a quick refresher.
I have package groups that apply to OUs, and within these OUs, I have 2-3 computers where I need to lock the version of Java or Firefox, for example.
What's the best approach?
Thanks in advance.
Re: Preventing a package from updating on a single machine
Published: February 6, 2020 - 6:23 PM
by dcardon
Hello Realynot,
realynot wrote: ↑Feb 5, 2020 - 5:11 PM
I need a refresher.
I have package groups that apply to OUs, and within these OUs, I have 2-3 computers where I need to freeze the version of Java or Firefox, for example.
What's the best approach?
To keep a package fixed to an older version, the best approach is to include the version number in the package name itself, e.g., tis-java8.189-1.wapt. However, due to how Organizational Units (OUs) work, the list of packages to install is generated by combining everything inherited by the OUs and everything directly assigned to the machine. This presents a problem if you want to create an exception for two or three machines and disable inheritance. It's possible to exclude certain packages. However, I'm not entirely sure how the dependency management engine will interpret this (does the deny take precedence over the accept? This needs to be verified)...
The simplest solution would be to put them in a separate OU that does not inherit from the package that needs to be frozen.
Sincerely,
Denis
Re: Preventing a package from updating on a single machine
Published: February 6, 2020 - 8:02 PM
by vcardon
dcardon wrote: ↑Feb 6, 2020 - 6:23 PM
The simplest solution would be to put them in a separate OU that does not inherit from the package that needs to be frozen.
I think this is your best option because this method will allow you to keep an eye on these machines which are potentially vulnerable due to this dependency on "old" utilities.
In the case of Firefox, you can configure it to only access the specified website, thus discouraging your users from using this older version of Firefox for their daily activities. As an added bonus, you can deploy a custom icon on their desktop for direct access to the application, without using Firefox shortcuts.
We are familiar with your situation because we have worked extensively with local authorities for whom this situation is unfortunately very common.
Long live the promise of the web!!! Now we have practically as many browsers as business applications, isn't that great? I'm so glad you chose WAPT
Sincerely.
Vincent