I have a questions about deploying and managing versions of Adobe apps using just the clean Creative Cloud app.
We're currently undergoing a merging of companies, where we also get merged into a shared JAMF instance, where we will have little to no control over packages, scripts etc. So our old method of creating and download custom Adobe packages from Adobes admin panel will be out of the question for now (this is also a tiresome method anyway). The clean Adobe Creative Cloud app is what we are left with.
So, I've heard that we might be able to install and version manage Adobe apps using scripts and commands, but I can't find much information on this online (Adobes support documents are rather lackluster).
Does any of you JAMF gurus here have any experience with deploying Adobe apps this way? I tried to search the forum, but didn't find what I was looking for.
It's worth mentioning that we are a post-production company, so always updating to the newest version is a big no here. We usually stick to one version for each release (eg. 2022.3, 2023.3 etc.).
Any help appreciated!
Take a look at Adobe RUM: https://helpx.adobe.com/enterprise/using/using-remote-update-manager.html
Adobe Caching server: https://helpx.adobe.com/enterprise/using/update-server-setup-tool.html
If you need to manage updates so users can't update the version, then I would deploy a "managed" Adobe Creative Cloud package.
So far, RUM is the best option. To deploy updates, you'd need to build a managed package through the Adobe console and trigger RUM with a script. However, this only works for minor releases and won't upgrade Adobe from version 22 to version 23.
this is the script I use to trigger RUM
#kills all adobe processes
pkill -f Adobe
pkill -f adobe
# Run the RemoteUpdateManager command with the install action
Starting to look at options for deploying Adobe. I'm going to test out using the Creative Cloud license and the apps from Jamf App Installers.
I noticed that the packages created in the Adobe console expire after a time. Does this expiration only effect when they can be downloaded. Or would that effect the ability to deploy it from a Profile?
Expanding on obi-k's comment:
We do the same. Here's a high level view of our workflow:
* I wrote a single script that takes attributes for the app, version and actions. I then reference it in the policies. Also I've added an Extension Attribute that checks the version of RUM so I can update that too if needed.
Thanks for all the replies! It seems there isn't a quick-and-easy way to have as much control as we require, using just the clean Creative Cloud. Alas!
@obi-k Thanks for the links! Guess I have to dig deeper into this. Not having admin-level control of our JAMF environment will be challenging! :)
@marksf Thank you for your suggestion. We won't be able to upload packages for the applications themselves, but it would be interesting to check out the basis of your script as an alternative, if that would be possible?
@mnordbye : Sure! This script will work if you've enabled Adobe Remote Update Manager in the admin console when you build the packages.
#!/bin/bash # # Runs Adobe RUM to manage Adobe Application updates # Parameters available in Policies # $4 = --action Options: list, download, install # $5 = --productVersions see: # <https://helpx.adobe.com/enterprise/package/help/apps-deployed-without-their-base-versions.html> if [[ -f /usr/local/bin/RemoteUpdateManager ]]; then echo "Starting Adobe RemoteUpdateManger..." /usr/local/bin/RemoteUpdateManager --action=$4 --productVersions=$5 else echo "Adobe RemoteUpdateManager not found." fi
Options: list, download, install
Specifies the action to be performed: list, download, or install.
I should note that this script is specifically for use with Jamf policies.
We can use this one script to install and / or update the base version of most Adobe apps.
This seems like a very clean way to deal with Adobe in JAMF @marksf . Thanks for sharing!
To understand you correctly, you still need a base package WITH Photoshop included for this to work, right? Not just a Managed package with RUM?
Thanks for all the great help so far, this forum is a lifesaver!
Posted this on another thread but perhaps this is a better place for this question. If I deploy Acrobat with Jamf Apps and it also installs the CC app, do I still need to deploy via a Profile the "blank" CC only pkg downloaded from Adobe? Is that just to manage some of the settings?