Skip to main content
Question

Patch Management for Adobe Creative Cloud

  • August 9, 2021
  • 5 replies
  • 32 views
I
Forum|alt.badge.img+7

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?


    5 replies

    JasonAtCSUMB
    Forum|alt.badge.img+6
    • JasonAtCSUMB
    • Contributor
    • August 10, 2021

    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. 
    https://helpx.adobe.com/enterprise/using/using-remote-update-manager.html

    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. 

    scottb
    Forum|alt.badge.img+18
    • scottb
    • Valued Contributor
    • August 10, 2021

    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. 
    https://helpx.adobe.com/enterprise/using/using-remote-update-manager.html

    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. 


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

    I
    Forum|alt.badge.img+7
    • imy
    • Author
    • Contributor
    • August 10, 2021

    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. 
    https://helpx.adobe.com/enterprise/using/using-remote-update-manager.html

    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. 


    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 - https://community.jamf.com/t5/jamf-pro/not-able-to-suppress-automatic-updates-in-adobe-creative-cloud/td-p/166649 - 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.

    JasonAtCSUMB
    Forum|alt.badge.img+6
    • JasonAtCSUMB
    • Contributor
    • August 10, 2021

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


    It works with/without AUSST server. 

    JasonAtCSUMB
    Forum|alt.badge.img+6
    • JasonAtCSUMB
    • Contributor
    • August 10, 2021

    I believe this explains how to disable CC updates system-wide in the package (Admin Console). https://helpx.adobe.com/creative-suite/kb/disable-auto-updates-application-manager.html#main_machine_wide

     

    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 : 2.6.0.3 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.

     

      Terms & ConditionsCookie settingsAccessibility statement