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

Installing AUSST 4.0 on Windows Server 2012 R2

New Here ,
Aug 05, 2016 Aug 05, 2016

Hi,

I'm trying to install AUSST on Windows Server 2012 R2 with IIS 8.5, though I can't get the thing to work!!!

I've followed the instructions from Using the Adobe Update Server Setup Tool (AUSST) though I'm doing something wrong.

All the updates have been downloaded to the directory 'c:\AdobeCloudUpdate' (just over 80GB). I've created a new web site in IIS to point to this directory as the root and set the permissions for the local 'IIS_USERS' group to read, list, etc.

I've followed the instructions to add the file types to the 'Handler Mappings' at the server level, changed the AppPool to classic and updated the 'C:\Windows\Microsoft.NET\Framework\v2.0.50727\config\web.config' file with the add path veriables for the 5 file types.

When trying to browse to the 'updaterfeed.xml' from a client computer using the full URL of 'http://co-au-01.contoso.msft/webfeed/oobe/aam20/win/updaterfeed.xml' I get an XML page cannot be displayed error.

Capture1.PNG

I have created a 'AdobeUpdater.xml' override file and added this to a new package created in the CC Packager and just deployed Photoshop and the CC Desktop app. When I load the CC app I get a Download Error when trying to display the apps.

Capture2.PNG

I've tried editing the other web.config files found on the IIS server ('C:\Windows\Microsoft.NET\Framework\v4.0.30319\config'), and also the .Net v2 & .Net v4 in the 'C:\Windows\Microsoft.NET\Framework64', though no joy.

Hopefully this is a really simple fix and I'm simply missing a step but some help would be very much appreciated.

Thanks in advance,


Tom

5.1K
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

Community Beginner , Aug 08, 2016 Aug 08, 2016

Something that I discovered here is that you need to add a wildcard MIME type on the ACC/services/fcc folder (more specifically the validation folder) because the validation files don't have an extension so it was throwing back a 404.

Screen Shot 2016-08-08 at 1.40.07 PM.png

Hopefully this fixes it for you!

Translate
Community Beginner ,
Aug 08, 2016 Aug 08, 2016

Something that I discovered here is that you need to add a wildcard MIME type on the ACC/services/fcc folder (more specifically the validation folder) because the validation files don't have an extension so it was throwing back a 404.

Screen Shot 2016-08-08 at 1.40.07 PM.png

Hopefully this fixes it for you!

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
New Here ,
Aug 18, 2016 Aug 18, 2016

Fantastic - that did the trick!

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
New Here ,
Dec 19, 2017 Dec 19, 2017
LATEST

Did you use the 64bit version or the 32bit version web.config and the aspnet_isapi.dll files?

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