Copy link to clipboard
Copied
Hello,
I'm looking for a way to allow our Mac non-admin Adobe CC 2015.2 users to upgrade to the new 6/2016 versions of apps such as Illustrator CC 2015.3 and Photoshop CC 2015.5 without using the Adobe Creative Cloud desktop application.
We've always facilitated Adobe updates for these non-admin users by paring AUSST+RUM along with JAMF's Casper Suite to offer updates via a Self Service application. However, even after upgrading to the latest releases of RUM and AUSST, performing a Fresh AUSST Sync and generating new .override files for clients, I can still not seem to get these new applications to be offered.
It appears that CC users outside our organization are upgrading via the Creative Cloud desktop application, however we had disabled the Apps panel during deployment within the Creative Cloud Packager, per Adobe's recommendation for organizations where end users are not administrators...
Does anyone have any recommendations for our situation to allow our end users to upgrade themselves without admin privileges?
These updates required full binaries and so were not offered via RUM/AUSST.
You can use the Creative Cloud Packager tool to build a package with these applications and push that out to your end users.
Copy link to clipboard
Copied
These updates required full binaries and so were not offered via RUM/AUSST.
You can use the Creative Cloud Packager tool to build a package with these applications and push that out to your end users.
Copy link to clipboard
Copied
So does that mean that AUSST is basically redundant in terms of the newer applications such as PS CC 2015.5?
Copy link to clipboard
Copied
For the applications you mentioned, there have been upgrades to the earlier version and not update so here RUM would not be able to install those. For example the latest version of Photoshop CC 2015.5 is version 17 as opposed to Photoshop CC 2015.4 which was version 16.x.x . The Creative Cloud Desktop application though, can install these upgrades but your users would need the Apps tab to install them and admin rights.
In the latest build of the Creative Cloud Packager though, we have come up with the concept of elevated privileges ( More information about it can be found here. Using this option, users without admin rights can install applications from the Creative Cloud desktop app without the need of having admin rights.
Also, the newer versions of most applications have the complete application installers hosted on AUSST and not just update patches. The list of the applications which can be installed from AUSST completely can be found here
Copy link to clipboard
Copied
Thanks for that info, very helpful! One thing I am confused about though is the last paragraph. I can see from my fresh installation of AUSST 4.0 that drilling down into the ACC folder there are the full updaters for the applications in that link. So when you say they can be "installed from" AUSST do you mean taking the package and using whatever delivery method you have at your disposal to install it on clients?
Also, is the fact they are "full" installers and not "updaters" the reason they cannot be installed using RUM? I usually package up applications using CCP and don't deploy CCDA to our clients as it causes too many help desk tickets as users sign in using their personal Adobe ID's and want to install non supported apps etc.
Slightly off track but do you know if there is a way to prevent a user form signing into CCDA with anything other than an Enterprise ID?
Thanks
Copy link to clipboard
Copied
The only workflow you can follow to install complete applications from AUSST is by using the Creative Cloud Desktop application which can check and see if it sees a newer application available from download from AUSST, it can install it.
Again, because it is an upgrade, RUM is incapable of handling it because it can only install update patches to a specific version.
Now, in order to perform any actions using CCDA it is required for a user to sign into it. Unfortunately we currently do not have a provision in place that can prevent a user from logging on to the application using anything else other than their Enterprise IDs.
Find more inspiration, events, and resources on the new Adobe Community
Explore Now