Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Applications CC 2017 show as up to date, but they are not current versions

Engaged ,
Feb 08, 2017 Feb 08, 2017

Hi Enterprise/deployment team,

ISSUE: We have so trouble here on the updates using Adobe AUSST for a deployment of CC 2017 CCT for 60 machines.

We did package CC 2017 (bases versions around December 2016) and updated or AUSST 3.0 to AUSST 4.x. But the apps don't update (they did before with AUSST 3.0 and CC 2015.x)

At the moment LR does update but the other CC 2017 app's don't (CC 2017, for example Premiere, Photoshop)

After a pull of the updates to our internal update server we also don't see the CC 2017 folders (for example PR 11.x) is this normal?

AUSST_4.png

Capture_CCD_shows_updated.PNG

Example: PR CC 2017 still @ 11.0.0

Capture_PR_CC_2017.PNG

I am aware of the KB: Adobe Creative Cloud desktop application lists uninstalled Adobe apps as up to date

This was tested but could not resolve the issue. How does the update check work? Does it check what is on the machine and check what is on the internal server to determine what is missing / can be updated?

What can I check to find the root cause? Are there any log I can check?

Thanks for the help, Daniel

379
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Feb 08, 2017 Feb 08, 2017

What version of RUM are you using? Because of changes to the way some of our installers work it may be necessary to ensure that the current version of RUM is deployed to each machine. To do this you can simply build an 'empty' package for deployment making sure to tick the option to include RUM.

Translate
Adobe Employee ,
Feb 08, 2017 Feb 08, 2017

What version of RUM are you using? Because of changes to the way some of our installers work it may be necessary to ensure that the current version of RUM is deployed to each machine. To do this you can simply build an 'empty' package for deployment making sure to tick the option to include RUM.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Engaged ,
Mar 13, 2017 Mar 13, 2017
LATEST

Thanks Alister, we did deploy the new RUM, also we did re-generate the .override files. This solved the issue. There were entries missing due to the fact the old .override was generated by the old AUSST.

Daniel

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines