Patch Management for Adobe Creative Cloud

New Contributor III

With there now being separate packages for Intel and Apple Silicon Macs for Creative Cloud products, how are you all handling patch management in Jamf? As far as I can tell, you can only tie a single package to a product version in the Definition tab, and for patch management purposes Jamf seems to treat both architectures the same. I have some ideas on how to do this, but I don't really like either of them. They are:

1. Make one package that has both installers and a script. The script will determine the architecture and thus run the right package
2. Make each of my existing installer policies also have a trigger. Use a payload-free package that has a script that calls the appropriate trigger
Is there some other way I am missing?



You’re right that it’s too difficult to manage with patch management. Use Adobe’s RUM. That’s the preferred update solution for enterprise.

Script it to run regularly via policy. There are several flags for the command, but running it without any flags updates all Adobe CC apps. 

Honored Contributor

@JasonAtCSUMB - not using AUSST - what script would update all Adobe products?  Thank you!

It works with/without AUSST server. 

New Contributor III

I was looking at RUM a while back and definitely want to go down that road. The issue I had when looking at this before was testing. I tried to do the following:

1. Install an old CC app
2. Run RUM to update
3. verify it updated

Between steps 1 and 2, the product always auto-upgraded before I had a chance to run RUM. Do you happen to know what option in what file turns off auto-updates? If I can turn them off I can then test RUM. This post - - gives a location that I thought was correct but upon further reading it looks like that controls just the Creative Cloud Desktop app itself, not the other apps.


I believe this explains how to disable CC updates system-wide in the package (Admin Console).


I would try this to preview what will be updated by RUM. 

/usr/local/bin/RemoteUpdateManager --action=list
/usr/local/bin/RemoteUpdateManager --help
RemoteUpdateManager version is :

Commandline Usage :

      RemoteUpdateManager [--proxyUserName=<username> [--proxyPassword=<password>]] [--channelIds=<',' separated channelIds>] [--productVersions=<',' separated productVersions>] [--action=<case-insensitive action verb from {list, download, install}, default is 'install'>] [{-h, -help, --help}]

RemoteUpdateManager must be launched with elevated privileges.