Copy link to clipboard
Copied
I am trying to create a package that prevents a user from updating the version of the product contained in the package.
I also want the package to over ride the users current version installed on their machine.
Any Ideas on how this can be implemented for a enterprise enviroment.
Thank you
@Makana2615763996hy It's only an overwrite if its an update to the same year release ex. Photoshop 24.5.9 overwrites 24.1.
24.5.9 doesn't overwrite 2023 releases.
If you are installing new software versions (ex 2024 from 2023), you create two Jamf policies - one to install the new version and one to remove the older. Scope it to the users on startup or log out and they wont be able to stop it.
Copy link to clipboard
Copied
You can check the following article on how to create a managed package from the admin console: https://helpx.adobe.com/enterprise/using/create-nul-packages.html
Need more details on "Override the users current version". You can always uninstall the apps and deploy the package with the required version on the client machines. If the users are using an old version and the package has a new updated version then the apps will also update.
Copy link to clipboard
Copied
The missing details
We can not allow the user to keep a version of a product that we do not authrorize. This package needs to over ride the current version installed and install the version we approve.
Lets say are package only allows version 23.0
If the package gets deployed on to a users device and it needs to be uninstalled. We can not rely on the users word that they uninstalled it. We have to many users for us to baby sit each user and uninstall the version and launch the package.
Copy link to clipboard
Copied
@Makana2615763996hy It's only an overwrite if its an update to the same year release ex. Photoshop 24.5.9 overwrites 24.1.
24.5.9 doesn't overwrite 2023 releases.
If you are installing new software versions (ex 2024 from 2023), you create two Jamf policies - one to install the new version and one to remove the older. Scope it to the users on startup or log out and they wont be able to stop it.