Hello there,
is there a way to upgrade a Photoshop 2021 to 2022 the old fashioned way with the continuous versions in the now legacy Titles?
In total we have 3 Sites with 24 Adobe CC Installation Policies + 24 testing policies to test new versions. Every product has a patch title in every site, so in total we have 144 Policies for Adobe and 42 Patch titles (Intel and Apple Silicon use the same titles).
General:
- Each software has an policy scoped to a static computer group or all computers
- It contains the latest approved productive package version for a software
- This policy contains a custom trigger named after the software
- For testing purposes we have a second testing policy
- Updates are done by change the package installers in the productive policy and rerunning the same policy.
- Each patch management title definition package for a version we deploy in the installation policy has a package set, which will execute the corresponding custom trigger set in the main policy to rerun the installation policy.
Steps for a regular update using continuous patch definitions:
- Prepare the package and upload it to the distribution point
- Change the package in the testpolicy and wait for approval
- If the approval is given change the package in the productive policy
- Add the corresponding “Trigger package” for the version in the patch title definitions
- Done
Steps for a regular update using new patch definitions for softwares without a continuous track when a new major version is released (some Adobe products):
- Prepare the package and upload it to the distribution point
- Change the package in the testpolicy and wait for approval
- If the approval is given change the package in the productive policy
- Inform the user about a new version and that they need to install it manually
- Add the new patch title for further updates for that Photoshop release. 42 times
- Remove the old patch title. 42 times
Patchmanagement with the new kind of patch definitions cannot be used to trigger an a major update ( Photoshop 2021 to 2022 ). There is no way to deploy an update without creating a smart computer group and a second policy for the installation or create a custom patch definition in our case. It defeats the whole purpose of the patch management and it creates a lot of unnecessary work in the backend and for the user.
