I just use the Creative Cloud packager and build an installer of the Core Compnents:

I then use the directions here to deploy: https://jamfnation.jamfsoftware.com/article.html?id=161

Additionally, you will want to either deploy this via self service or by scoping a policy to a smart group based on a dummy receipt or whatever else makes the most sense in your environment.

@emilykausalik - have you found this method more managed than deploying the individual apps to end users and maintaining the updates, etc

@randy we don't install the other components for them. We use the named license version of the Creative Cloud team so the user logs in with an Adobe ID generated from an invite email sent and logs in, then downloads what they need. We found that users that have the software pre-installed via Self Service/Casper distribution have trouble getting updates, uninstalling, and/or reinstalling through the CC portal. I think it has to do with the receipts saved on the machine, though I'm not 100% sure why that happens as I haven't had a chance to really vet it out on a user having problems.

@emilykausalik - thanks Emily, our method has been to disable the CC desktop app and just put all the apps in self service (done with both team accounts and enterprise license) and just use the adobe package tool to update each app with updates and also create a updates package - seems to work well, but since all apps can be delegated through the cloud app, I'm curious if this would be the better method and more practical for users and less interaction on our part to manage it.

@randy I'm guessing it would be easier on your team, but then you'd have to make sure users are actually updating stuff. We all know how that goes…

@emilykausalik, but seeing how good Adobe are at highlighting the shiny new feature available in each CC update.. Perhaps that's the carrot?

@bentoms true!

Though to at least encourage updating, you could always have smart groups based on version and have a pop-up script that appears if an update is available or something. *shrug*

Piggybacking on this post with a related issue.

I've got AUSST working and a policy that executes RemoteUpdateManager. I'm also successfully disabling update notifications. However the Creative Cloud app itself seems to fall outside what AUSST and RemoteUpdateManager dish out.

In most installs I am converting existing installs of Creative Cloud updates from user-managed to IT-managed. In the process I'm going to just uninstall the Creative Cloud app. But a few boxes will need to keep the Creative Cloud app and I will need to keep that app updated.

So I tried to update the Creative Cloud app via a package created with CC Packager (Core Components only). However when I apply it to test boxes the Creative Cloud app still thinks it needs updating. Get Info in the Finder shows the correct version. But when launched it still begs to be updated.

Has anyone had any success with keeping the Creative Cloud app updated via a policy?