Skip to main content
Participant
May 28, 2019
Question

How update Creative Cloud app to latest version without signing in?

  • May 28, 2019
  • 1 reply
  • 4746 views

Using the Admin Console site today, I generated a new Named license package that is supposed to contain both CCDA, Acrobat 19, and allow the ability for my users (who do not have admin rights), to install whatever other Adobe applications they want. In the sidebar, I have the following options:

  • Show apps panel
  • Allow non-admin to update and install apps
  • Enable file syncing
  • Enable Remote Update Manager
  • Exclude extensions folder & Extension Manager command line tool
  • Exclude Adobe Asset Link
  • AUSST override XML not included
  • Install at default directory

After installing, the application sits at January 22, 2019's version 4.8.0.421, when the current version of the app is 4.8.2.476.

What I want to know is, how can I force the CCDA to update itself immediately after it finishes installing? Our workflow is that systems get imaged in my I.T. office and might sit for 2-3 days before getting sent out to the users' offices. Yet it seems that until my endusers sign in with their Enterprise ID, they're just going to have an outdated 4.8.0.421 version of the CCDA on their machine, and it's going to waste time for them on first CCDA launch for the application to update itself.

Is there a flag or parameter I can set during install, via GPO, or some other method (we use SCCM) that will force the CCDA to update itself to the most recent version on Adobe's servers without the user signing in first?

...For that matter, why does the Admin Console keep pushing out a version of the CCDA from January 2019? It's not like this is a locally hosted Adobe mirror my company isn't keeping up to date; I'm getting these packages directly from Adobe's servers. Why is the pushed out version so out of date?

This topic has been closed for replies.

1 reply

Participant
May 12, 2022

Did you ever figure out how to keep the CCDA up to date without a logged-in user? I have a few machines deployed to users that don't get logged into very often, and I'm tired of getting dinged by my vulnerability scan for these devices. Creating a new package in the console just to update the CC app is beyond inefficient. It would be great if the AdobeUpdateService could be kicked off, or just run automatically, without a logged-in user.