Unable to update Creative Cloud apps 2016

[robert_humphreys]

Not sure how to word this one.

Previously, i would create the packages using Adobe CC Packager and uncheck the Creative Cloud app. because i did not want user to be able to update the apps or be confused as to how to sign in.

We have a Enterprise License and i would Distribute it and Local Admin accounts could update it as needed.

Always worked fine before. but this year with the 2015.5 (or 2016?) versions they no longer update.

AAM keeps saying that Creative Cloud is damaged, or not installed, which is what I want. I don't want users being able to sign into Creative Cloud or update the apps.

I'm signed in, and it recognizes my ID, but Updates is always grayed out.

Am i missing something in the creation of Packages? or is a old version that was not uninstalled causing a glitch in the AAM not being able to function? the Serial number nor my account has changed in years, so it should be fine..

[alisterblack]

Is it possible that you chose to block updates when building your package?

Disable auto-updates in Adobe Creative Cloud and Adobe Creative Suite 6 apps

[robert_humphreys]

Nope, there's no way to do that in the CCP Packager...

[alisterblack · Accepted solution]

There is, in fact the default option is to turn off updates when building a package.

Create packages for Adobe Creative Cloud

• To prevent the user’s Application Manager from doing automatic update checking for the deployed products, choose the default option, "Adobe Update Manager is disabled (IT manages update distribution)”. In addition to suppressing the automatic update behavior, it disables the Update option from the Help menu in the applications; users can no longer actively look for updates on their own. If you choose this option, the IT admin must download and deploy updates for their users.
• The option “Admin users update via Adobe Update Manager” enables automatic update checking through the Adobe Application Manager, which is the default for products installed individually. If the user’s system was previously set to suppress updates, deploying a package with this option set re-enables automatic update checking.
• You can choose to redirect the automatic update process to check for updates with your own update server, rather than the Adobe update server. Select the option “Use internal update server”. For this option, it's necessary to host updates on an internal server, and redirect the Adobe Application Manager to look there for updates. You do this by providing the path to an XML configuration file that contains information about the hosted server. For more information about hosting an internal server, see Using Adobe Update Server Setup Tool.

[robert_humphreys]

Ohhhhh, man, I apologize, you are right!!!!!!

i can't believe i missed that one...

I will re-create my package....

Hmmm.. I wonder if there is a way to change it after-the-fact to allow Admins to do the updates?

I see from the link on how to disable it, if i change the "1" to a "0" would that change it back to allow?

Thank you so much for the info, I totally missed it....

[alisterblack]

Yes, or just remove the AdobeUpdaterAdminPrefs.dat  file entirely.

[robert_humphreys]

Wait, i think if i just remove the file located here:

Mac OS

<Startup Disk>/Library/Application Support/Adobe/AAMUpdaterInventory/1.0/AdobeUpdaterAdminPrefs.dat

Then it will allow local admins to do updates? I think i have that right......

[robert_humphreys]

Ahh, you are too fast!! 🙂   I was thinking the same thing.. ok. i got it, and thank you so much for you help on this!!!

Gold Star for you !!!!