Set up the internal update server

Download and install an HTTP server. 

Copy the update and installation files synchronized by AUSST, to a sub-directory accessible through the web-server.

• If you haven’t already downloaded the AUSST files, pass the command to copy the AUSST files to a folder under the HTTP server folder (here htdocs) folder. For more information, see Use the fresh sync option if multiple apps/updates are visible on  end-user computers.
• If you have already downloaded the AUSST files, copy AUSST files to a folder inside the HTTP server folder. (here <xamppserver>\htdocs\<create a folder called AUSSTFiles>). For the new folder you have created in this step (here AUSSTFiles), change permissions to select to “Apply to enclosed items.”

 Launch the HTTP server (here Xamppserver).  

Start the HTTP web server. For example, in the xampp server, go to the Manage Servers tab and start the Apache web server.

Generate the .override files. For steps on generating the .override files, see Generating Client Configuration Files. 

Set up IIS 8.5 on any platform, such as Windows Server 2019.  For steps on configuring IIS 8.5, see: http://www.iis.net/learn/install/installing-iis-85/installing-iis-85-on-windows-server-2012-r2. 

•  Add two additional Role Services manually: ISAPI Extensions and ISAPI Filters while configuring IIS 8.5. 

•  Click Install on the Confirmation screen. 

Ensure to restart the server after you have installed the above given additional roles. 

Ensure that Directory Browsing on IIS is enabled.

• In Server Manager, select Tools > IIS Manager.
• In IIS Manager, select the server displayed in the left pane. 
• Double click the Directory Browsing to enable the directory service.

•  Enable the Directory Browsing service.

Select the server displayed in the left pane. 

Click the Handler Mappings of the required website. 

Select the Add Module Mapping option. 

Add Module Mapping for .xml extension. You may use the details as shown in the sample dialog box.

After the extension is added, the system displays the Add Module Mapping dialog box. Click Yes.

Similarly add Module Mapping for the given extensions:

• ·crl
• .zip
• .dmg
• .sig
• .json
• .arm 

Check that you have added Module Mapping for all the above listed extensions.

For Acrobat and Adobe Reader, you will need to add the application/octet-stream MIME Types for the .msp, .pkg, and .arm extensions.

• Select the Server displayed in the left pane. 
• Add the MIME Type.

• Add the details as shown in the sample dialog box.

Similarly add MIME types for the .pkg, and .arm extensions.

Check you have added the MIME type for all three mentioned extensions. 

Confirm that the web server works by opening a web browser on the server itself. Verify that the following default web page is displayed when you use the http://localhost address.

Within your web folder, create a folder (root) that you will use to download the Adobe apps and updates from the Adobe Update server.

For example: C:\inetpub\wwwroot\updates

The root folder location must map to a valid HTTP URL on your web server. To validate this, go to a browser and ensure that the folder root is accessible via an http request.

For example: http://ausstserver.example.com/updates/

Navigate to the folder in which you have downloaded the Adobe Update Server Setup Tool.

• cd <Absolute location of the folder which contains the Adobe Update Server Setup Tool>

       For example: cd C:\AUSST 

The  root update folder (which we will use as an example throughout this document) on your web server is at the file-system location:

For example:

• macOS: /serverroot/updates/
• Windows: C:\inetpub\wwwroot\updates

Check that the root location has the correct Write permissions. 

Enter the following command to do a fresh installation of the internal update server:

• Windows:
  AdobeUpdateServerSetupTool.exe --root="<absolute location of the folder from Step 1 above>" --fresh
• macOS:
  AdobeUpdateServerSetupTool --root="<absolute location of the folder from Step 1 above>" --fresh

For example:

AdobeUpdateServerSetupTool --root="c:\inetpub\wwwroot\updates" --fresh

Ensure that there are no spaces around the = sign. Also, ensure that all options are preceded by a                   --(double minus) sign.

Ensure that the web server is running correctly — confirm that the home page of the web server can be accessed by a browser from a client computer.

Verify that you can browse through the directories by clicking the directory links.

To verify that your server supports extension-less files open this URL in your web browser - you should see a string of letters:

http://<server name>/updates/ACC/services/ffc/icons/producticon

For example:

http://ausstserver.example.com/updates/ACC/services/ffc/icons/producticon

To verify that your server supports files with extensions, test that you can open the following XML file in a web browser from your server:

• If you have not set up product configuration groups:

http://<server name>/updates/ACC/services/ffc/products/ffc.xml

• If you have set up product configuration groups:

http://<server name>/updates/ACC/services/ffc/products/<groupName>ffc.xml   

Check the firewall settings for the server if your verification on the client computer is not successful. 

Navigate to the folder in which you have downloaded the Adobe Update Server Setup Tool.

Enter the following command in a command shell or terminal (using your own server information):

• AdobeUpdateServerSetupTool --genclientconf="/serverroot/AdobeUpdaterClient" --root="/serverroot/updates/Adobe/CC" --url="http://<server name>"

For example:

AdobeUpdateServerSetupTool.exe --genclientconf="C:\inetpub\wwwroot\updates\config" --root="C:\inetpub\wwwroot\updates" --url="http://ausstserver.example.com/updates"

• server root is path of the root folder
• config is the folder for AUSST tool to generate the AdobeUpdaterClient configuration files
• url is the valid http path of the root folder

This command creates two client configuration files (one for Windows platform, and one for macOS platform), and in the following platform-specific folders under the path given in the --genclientconf option.

In this example, the new files are:

• ·Windows:
  \serverroot\config\AdobeUpdaterClient\win\AdobeUpdater.Overrides

• ·macOS:
  /serverroot/config/AdobeUpdaterClient/mac/AdobeUpdater.Overrides

Log in to the Admin Console and navigate to Packages > Preferences.

Open the AdobeUpdater.Overrides file in any text editor.  Copy and paste the entire contents of the file into the Internal Update Server box and click Save.

AUSST allows redirection of all kinds of packages. 

AUSST allows redirection of all kinds of packages. To include overrides in your package, enable “Redirect to internal Adobe update server”. It will be deployed with package.