AUSST - some versions of products will install, but not all

[jeremyh94224552]

I setup an AUSST server, had the CC desktop app packaged with update Overrides files, and everything was working OK - internal only deployment from my AUSST server worked for all CC software, including client privileges escalation for local admin rights for any of our users to be able to install any program from the CC desktop launcher.

Then the CC desktop launcher updated, a few times now it seems.  The client privileges escalation allows the new version to download and install just fine.

However - my customers unable to install the newest versions of CC products.  I can install older versions, but not newer.

This is the error when attempting to install Photoshop CC (both 2018 and 2017 versions)

FATAL: Fatal Error '113' occurred while download

FATAL: Error occurred in download of package (Name: CameraRawRIBSCoExistPackage Version: 9.6.0.126). Error code: '113'

The installation files for that product are on my server.

The installation of Photoshop CC 2015 went perfectly.  IE: my server, my configuration files, and my network are not the problem with these older versions.

What has Adobe changed in newer versions of the CC desktop launcher application so that it is ignoring the files on my AUSST server?

[kglad]

[moved from Adobe Creative Cloud to Deployment for Creative Cloud for Team, Enterprise, & CS]

[Francouz · Accepted solution]

Hi,

Now you can set up your AUSST update server in two different mode:

-Incremental mode: only update for the current version

-Fresh mode: Update and upgrade

However be careful with the fresh mode as it will not delete the old version on the end user computer.

i assume you AUSST is in the incremental mode as your end user can't install newer version.

Have a nice day

[jeremyh94224552]

I have tried both fresh and incremental downloads via AUSST, with no difference between the 2.

I found today using a compare tool that 2 file types are not downloading from Adobe:

“Application.JSON” files which seem to start as Application.json.aamdownload.

“Validation.XML” files which seem to start as validation.xml.aamdownload.

I am investigating with my network team as these file type may be blocked by our malware prevention systems.

It's strange though, as I have tried at home also, with similar results.  I will give it another go tonight.