Hey folks! We're using SCCM to deploy various Adobe Creative Cloud products across our organization, but I'm curious about how everyone manages updates for them. In the past, updating required admin rights, so we've been packaging new versions for distribution. I've heard about tools like RUM and AUSST that could potentially eliminate the need for admin rights and allow for auto-updates. Any insights on this? Thanks!
2 Answers
I’ve taken a pretty laid-back approach. I just deploy the Adobe CC package from the Microsoft Store and let the users handle their own updates. If there's a specific version of Photoshop that needs to be maintained, then we go back to packaging each major version.
I had the same experience. When I managed Adobe CC, I found Adobe's distribution model to be cumbersome. I enabled updates for non-admin users when I distributed the package and never had complaints.
In education, I’ve enabled self-management and auto-updates for staff. For students, I create a managed package with a PowerShell script that uses RUM. It runs through SCCM, generates a local text file with the date it ran, and checks that against the current date. It’ll only run again if it’s a new month, and I make sure it only runs when no one’s logged in. However, RUM does have a limitation: you can only update within the same version, which works for us since we need compatibility with testing applications.
Interesting! Could you clarify how you set up that self-managed auto-update system? I worked in education for a decade, and often that seems tricky!
That sounds like a solid plan! But didn’t setting up self-management and auto-updates require admin rights? Also, regarding your RUM script, have you considered deploying it as a package? You could set a 30-day rerun time.
How do you actually deploy the app from the Store? Are you using Intune? And how do you ensure everyone is on the same version?