Is there a way to to create a policy to have our current macs update all of the applications via the create cloud desktop tool? Or is there another way to do it? We are currently running cc2019 Device license and they are asking for the machines to be updated to 2020.
@stephaniemm77 Following. We just rolled up one of our labs to Adobe CC 2020, that being said it was during a re-image. I split the installers into 3 separate PKGs, wrapped in them in a DMG, and used a script to install PKG from DMG. <-- If I did not do it that way the install would fail.
To the point, the installer from the Adobe Admin Console comes with an uninstaller. I am wondering if you deploy that prior to deploying CC 2020 if that would work? You would need to have the 2019 installer to get the correct un-installer.
The CC update tool will update 2019 versions to the Max available version of 2019, they will not be updated to the 2020 version. This will be true for all of the apps that put 2019 as a part of the app name. So Lightroom classic does not put 2019 in its name, it will update to the latest version. I have just repackaged all of the Adobe Apps, and will be rolling them out.
And when I last spoke to Adobe about the updater, it will not update the Creative Cloud Desktop Application. That has to be done manually from within its self. They may have changed this behaviour, as it was a couple of years ago that I asked about it.
There is no way to leverage the functionality of the CCDA via command line, cloud console or otherwise. Most shops who manage versions and updates use packages from the adobe admin console to uninstall the old and install the new.
@stephaniemm77 Did you install RUM when you rolled out the desktop app? If you could probably run a script to kick start RUM and update any installed apps. That's currently what I am trying out now and figuring it will work. What I need figure out is how to get the old version to uninstall when the latest gets installed via RUM. Work in progress for sure.
This is the script I will be testing with https://github.com/jmahlman/uarts-scripts/blob/master/Adobe-RUMWithProgress-jamfhelper.sh
Always good to know there's a universal pinch point for such challenges. We had a combination of of old versions of Adobe from 2015... The uninstaller is great however it fails to remove some incremental version of any CC. So you will have some apps left behind after running the uninstaller. The way we did it was make use of both the uninstaller an and a script using the adobe sapcodes where available. in fact the sapcode is quite reliable in a script
If you run the script as a before script in a policy for 2020 it removes old versions before installing 2020.
We also do not place the package downloaded from admin console into a dmg as JAMF Admin zips it up and it has never failed. We also created a policy for cashing and another one for installing cashed.