This article describes how to install and configure Adobe Update Server Setup Tool (AUSST), which is a utility to help you set up your own update server to manage the deployment of Adobe products and product updates in your enterprise. AUSST also hosts apps that can be deployed without their base versions, which can be installed using Adobe Creative Cloud desktop app.  

Apps and updates are downloaded for both the Windows and the Mac OS platforms. Apps and updates synced through AUSST can be installed through Adobe Creative Cloud desktop app. While updates synced through AUSST can be installed through Remote Update Manager (RUM). 

Note:

AUSST is intended for the enterprise IT administrator who sets up and maintains the in-house update server.

Overview

Adobe Creative Cloud desktop app can be used to install products synced through AUSST. To install updates, you can use one of the following:

  • Remote Update Manager
  • Help > Update menu command in the applications 
  • Adobe Creative Cloud desktop app 
  • Adobe Updater tool

For more information on ways to deploy products and updates, see Deployment options.

Update server overview

Note:

If you have suppressed the updates while deploying a package, updates through the Help menu (Help > Update) are disabled. However, you can still install updates through RUM or deploy an updated package created through Creative Cloud Packager.

What’s new in AUSST 4.1

  • Support for syncing Acrobat and Reader updates (Windows and MAC)
  • Applications synced through AUSST can now be installed through Creative Cloud desktop app. For a list of applications that can be installed through Creative Cloud desktop app, see Applications that can be deployed without their base versions.

Deployment options

For the latest versions of some products, along with updates, applications are also synced through AUSST. For a list of applications hosted on AUSST, see Applications that can be deployed without their base versions.

You can use Remote Update Manager (RUM) or the Adobe Creative Cloud desktop app to install products and product updates. The following table lists the support of apps and updates for AUSST, RUM, and Creative Cloud desktop app: 

Type of product/product update Sync throu AUSST Install through Adobe Creative Cloud desktop app Install through RUM
Latest products for which applications are hosted on AUSST (list) Yes Yes No
Product updates Yes Yes Yes
Acrobat updates Yes No Yes

Apps and updates synced through AUSST can be installed through Adobe Creative Cloud desktop app. While updates synced through AUSST can be installed through Remote Update Manager (RUM). 

Note:

Updates for version CS5 and above are synced through AUSST.

Apps and updates installed through Adobe Creative Cloud desktop app
Apps and updates installed through Adobe Creative Cloud desktop app

Using AUSST to set up your own update server

In an enterprise environment, you might prefer to host your own update server (AUSST) to download and store products and updates from the Adobe Update server.

The Adobe Update Server Setup Tool (AUSST) helps you to configure your own update server and download products and updates from the Adobe Update Server to it. Once you have set up your own update server, you can redirect the client machine where Adobe apps are installed to AUSST server, rather than the Adobe Update Server. When you do this, the client machines check for products and updates on your server, and when instructed, downloads the products and updates from your server.

Using AUSST

Note:

The purpose of AUSST is to help you host an in-house update server so that the client machines check for products and updates on the in-house server instead of the Adobe update server. AUSST is not currently intended for remotely deploying products and updates on machines in your network.

System requirements

The server hosting AUSST is recommended to have the following configuration:

Disk Space
  • Initial minimum space requirements - 200 GB

Operating System

  • Windows: Microsoft Windows 7 or later
            -OR-
  • Mac: OS X Mavericks (version 10.9) or later

Setting up an update server: at a glance

Here are the main steps for setting up your in-house update server using AUSST. You need an already up and running http server to use as the update server.

Note:

AUSST is available in the utilities folder of Adobe® Creative Cloud™ Packager installation. You can also download AUSST from the Deployment snap in the Admin Console.

  1. Ensure that a web server is available
  2. Perform one-time setup using AUSST:
    As part of the one-time setup, AUSST does the following:
    • Performs the initial configuration
    • Sets up a directory structure similar to the one on the Adobe update server
    • Copies apps and updates from Adobe update server to the web server. Both Windows and Mac OS apps and updates are synced.
  3. Periodically, synchronize the latest apps and updates from the Adobe update server to the web server. Perform this step regularly to ensure that your in-house server hosts the latest apps and updates.

These steps are described in the next sections. The following diagram illustrates the process and provides links to the sections in this document where the corresponding steps are explained.

Note:

The paths provided to all the command-line options should be absolute paths. AUSST does not support relative paths.

Setting up an update server

Location of the Adobe Update Server Setup Tool

AUSST is available as AdobeUpdateServerSetupTool.exe on Windows and a UNIX executable named AdobeUpdateServerSetupTool on Mac OS. You can also download AUSST from the Deployment Dashboard.

If you use Creative Cloud Packager to deploy Adobe products, AUSST is made available as part of the Creative Cloud Packager installation. Here are the locations:

In Windows 32-bit <system drive>:\Program Files\Common Files\Adobe\OOBE\PDApp\CCP\utilities\AUSST
In Windows 64-bit <system drive>:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\CCP\utilities\AUSST
In Mac OS /Library/Application Support/Adobe/OOBE/PDApp /CCP/utilities/AUSST

AUSST is a command line tool and needs no separate installation steps. There are no restrictions on where AUSST should be located on the machine.

Preparing a web server to use as the update server

You can set up your in-house update server on any HTTP server (such as Apache or IIS) that can host and serve static file content. An already up and running http server is a pre-requisite for setting up AUSST.

To use a specific port, configure the port number while setting up the client machines. You will only need to provide the port number in the client configuration file (overrides file).

If you use Internet Information Services (IIS) Server as your web server, refer to the following section for configuring the IIS server for use as the update server.

Performing One-Time Setup

To set up your in-house update server for the first time, you use the Adobe Update Server Setup tool to create an update directory structure at the root folder location you created. If any files or folders exist at that location, the tool removes them. It then creates the folder structure that matches that of the Adobe update server, and performs the initial synchronization that downloads all available apps and updates from the Adobe update server to your in-house server.

Here are the steps to run the tool for first-time configuration:

  1. Run the tool in a command shell or terminal, specifying your root update folder. For example:

Note:

Ensure that there are no spaces around the = sign.

Fresh synchronization AdobeUpdateServerSetupTool.exe
--root="/serverroot/updates/Adobe/" --fresh
[--proxyusername=proxy_username --proxypassword=proxy_password] [--silent]
Incremental syncronization AdobeUpdateServerSetupTool.exe
--root="/serverroot/updates/Adobe/" --incremental
[--proxyusername=proxy_username --proxypassword=proxy_password] 
Generate
Client Configuration XML
AdobeUpdateServerSetupTool.exe
--root="/serverroot/updates/Adobe/" 
--genclientconf="/serverroot/config/AdobeUpdaterClient" 
--url="http://serverabc.example.com:1234/Adobe/"      
  • The [--proxyusername=<proxy_username> --proxypassword=<proxy_password>]parameter is optional and specifies the proxy username and password if a proxy server is required to connect to the network.
  • The --fresh parameter removes any existing files from the root location (if it exists) and then downloads all the apps and updates present on the Adobe Update Server.
  • The --silent parameter suppresses the warning that is displayed by default in case the root folder specified already exists.
  • The --acrobatonly parameter syncs only Acrobat and Reader updates.

The root folder is the file-system location on your in-house update server where apps and updates from the Adobe update server are stored. The root folder location must map to a valid HTTP URL.

Note:

Ensure that the root folder lies within the access of the server root location so that update content can be served by the web server.

As an example, suppose:

  • The root update folder on your web server is at the file-system location /serverroot/updates/
  • The web server's URL is http://serverabc.example.com:80
  • Within your web server, you set up the in-house update server at
    http://serverabc.example.com:80/Adobe/CS

In this case (which we will use as an example throughout this document), the root folder location is
--root="/serverroot/updates/Adobe/CS"


For this example, the command to run the apps and updates will be:
AdobeUpdateServerSetupTool --root="/serverroot/updates/Adobe/CS" --fresh

AUSST creates a directory structure for the apps and updates in the root folder and then copies the apps and updates from the Adobe update server to your in-house update server.

Note:

Both Windows and Mac OS apps and updates are downloaded. Currently, you cannot selectively download updates for only one platform.

When you have completed this initial setup, your in-house update server is ready to update client machines.

Errors, warnings, and troubleshooting information are recorded in the log files.

The following log files are located in the %temp%  folder in Windows and in the ~/Library/Logs  in Mac OS:

  • AdobeUpdateServerSetupTool.log
  • AdobeAcrobatUpdateServerSetupTool.log

DLM.log is located in the following locations:

  • Windows: 
    • %Temp%\CreativeCloud\ACC\AdobeDownload
    • %Temp%\AdobeDownload\
  • Mac: 
    • ~/Library/Logs/CreativeCloud/ACC/AdobeDownload
    • ~/Library/Logs/AdobeDownload/

Verifying the setup

To confirm that the first-time configuration is successful, check the following:

  1. Ensure that the web server is running correctly — confirm that the home page of the web server can be accessed from a client machine.
  2. Confirm that the root location has the Adobe products and updates available on it. If not, check that the root location has the correct write permissions.
  3. Confirm that you can view/download the products and updates from the client machines through a browser.
  4. Check that the updaterfeed.xml files on the update server can be accessed from browsers on the client machines.

The updaterfeed.xml files are located at the following path, determined by the parameters in the overrides file:
http://[domain]:[port]/[URL]/updaterfeed.xml


For example, let us assume that the override file has the following entries:

<Overrides>
	<Application appID="webfeed20">
        <Domain>http://10.41.35.164</Domain>
        <URL>/ausst/webfeed/oobe/aam20/win/</URL>
        <Port>8089</Port>
    </Application>
    <Application appID="updates20">
        <Domain>http://serverabc.example.com</Domain>
        <URL>/ausst/updates/oobe/aam20/win/</URL>
        <Port>8089</Port>
    </Application>
    <Application appID="FFCProducts">
        <Domain>http://serverabc.example.com</Domain>
        <URL>/ausst/ACC/services/ffc/products/ffc.xml</URL>
        <Port>8089</Port>
    </Application>
    <Application appID="FFCIcons">
        <Domain>http://serverabc.example.com</Domain>
        <URL>/ausst/ACC/services/ffc/icons/productIcon</URL>
        <Port>8089</Port>
    </Application>
    <Application appID="FFCValidation">
        <Domain>http://serverabc.example.com</Domain>
        <URL>/ausst/ACC/services/ffc/validation/</URL>
        <Port>8089</Port>
    </Application>
    <Application appID="FFCPackages">
        <Domain>http://serverabc.example.com</Domain>
        <URL>/ausst/ACC/services/ffc/packages/</URL>
        <Port>8089</Port>
    </Application>
</Overrides>

In this case, the location of the updaterfeed.xml file is as follows:
http://serverabc.example.com:1234/Adobe/CS/webfeed/oobe/aam20/win/updaterfeed.xml

The location on Mac OS is:
http://serverabc.example.com:1234/Adobe/CS/webfeed/oobe/aam20/mac/updaterfeed.xml

Note:

When you view the updaterfeed.xml file in a browser, you will not be able to view the content in the file. This is OK; you only need to ensure that the file is accessible through the http:// path. You can view the content of the updaterfeed.xml file by right-clicking and viewing the source.

Setting up Client Machines

Apps and updates, by default, are fetched from the Adobe update server. To host and configure your own update server to fetch apps and updates from the AUSST server, deploy the override file.

To do this, you must create an XML configuration file (AdobeUpdater.overrides) and deploy it on the users' machines. You can use the AUSST tool to generate the override files automatically, as explained in the next section. The configuration file provides the domain, URL and port information for your in-house update server; the URL is different for Windows and Mac OS platforms. The following shows the format of the AdobeUpdater.Overrides file, using our example server information (see Performing One-Time Setup for the example server information):

Note:

If you migrated from one version of AUSST to another, you must update the XML configuration files on the client machines.

Generating client configuration files

You can generate the client configuration files automatically with AUSST. You can only do this after you have set up your server and synchronized it with the Adobe update server.

To generate the configuration files, enter this command in a command shell or terminal (using your own server information):

AdobeUpdateServerSetupTool--genclientconf="/serverroot/config/AdobeUpdaterClient"
--root="/serverroot/updates/Adobe/CS"
--url="http://serverabc.example.com:1234/Adobe/CS"

 

 

 

This command creates two client configuration files (one for Windows platform, and one for Mac OS platform), and writes them into platform-specific folders under the path given in 

--genclientconf.

In this example, the new files are:
/serverroot/config/AdobeUpdaterClient/win/AdobeUpdater.Overrides
/serverroot/config/AdobeUpdaterClient/mac/AdobeUpdater.Overrides

Deploying client configuration files

To deploy the client configuration file for the Adobe Application Manager Updater on each client machine, you must write the correct platform version of the file to the following platform-specific location:

In Windows XP:

\Documents and Settings\All Users\Application Data\Adobe\AAMUpdater\1.0\AdobeUpdater.Overrides

In Windows 7/Vista:

\ProgramData\Adobe\AAMUpdater\1.0\AdobeUpdater.Overrides

\Program Files (x86)\Common Files\Adobe\UpdaterResources

In Mac OS X:

/Library/Application Support/Adobe/AAMUpdater/1.0/AdobeUpdater.Overrides

Note:

In case only Acrobat or Reader is installed on the user machine and no other Creative Cloud product or Creative Cloud desktop application is present, the above folder structure will not be available. In this case, you will need to create the folders manually with administrative privileges.

 

Note:

You are recommended not the deploy these configuration files on an admin computer on which you are running Creative Cloud Packager else you might experience issues during package creation.

Synchronizing with the Adobe Update Server

After you initial setup, you will need to regularly synchronize your in-house update server with the Adobe Update Server, to make sure you have all the latest apps and updates. You do this with the following command:


AdobeUpdateServerSetupTool --root="/serverroot/updates/Adobe/CS" {--incremental | --fresh | --acrobatonly}

Incremental Synchronization

Although the --incremental parameter validates all the downloaded apps and updates, but it downloads only those apps and updates for which a more recent version is available. 

If there are new apps and updates posted on the Adobe update server since your last synchronization, specifying the --incremental parameter pulls only the new apps and updates to the local server. If there are no new apps or updates available, the command does nothing.

In normal course, this is the option that you should use. However, if you find that if for some reason the latest apps and updates are not being reflected on the client machines, you can perform a fresh synchronization as explained next.

Fresh Synchronization

The --fresh parameter downloads all apps and updates present on the Adobe Update Server.

Any apps and updates present on the machine are first removed. Then, all the apps and updates available on the Adobe Update Server are downloaded to the machine.

In either case, the result is that your in-house update server is up-to-date, and ready to update client machines.

Acrobat-only Synchronization

The --acrobatonly parameter downloads only Acrobat and Reader app or updates present on the Adobe Update Server.

Setting Up IIS\Apache Server for Use with AUSST

This section describes how to set up an HTTP server on Mac and Internet Information Services (IIS) Server on Windows for use with AUSST.

Setting up HTTP server

You can use any HTTP server. For this example, XAMPP for OS X is used.

  1. Download and install an HTTP server. 

  2. Copy the AUSST files.

    • If you haven’t already downloaded the AUSST files, pass the command to copy the AUSST files to a folder under HTTP server folder (here htdocs) folder. For more information, see Use the fresh sync option if multiple apps/updates are visible on client machines.
    • 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.”
  3.  Launch the HTTP server (here Xamppserver).  

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

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

Setting up IIS 8.5

  1. Set up IIS 8.5 on any platform, such as Windows Server 2012 R2, and add two additional features manually: ISAPI Extensions and ISAPI Filters while configuring IIS 8.5.

    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

    IIS 8.5 setup
  2. Run AUSST and synchronize the apps and updates available on the Adobe update server at default website root.

  3. In Server Manager, select Tools > IIS Manager.

  4. In IIS Manager, select the Server displayed in the left pane. 

  5. Click the handler Mapping of the required website as shown here:

    Note:

    The configuration changes are applied to all data referring to this (default in this example) website. You should, therefore, create a separate website for updater- related data and apply these configuration-related changes to this separate website, so that the other sites are not affected.

    Click the handler Mapping of the required website
  6. Select the Add Module Mapping option as shown here:

    Select the Add Module Mapping option
  7. Add Module mapping for xml, crl, zip, dmg, sig, json, and arm extensions. A sample dialog box for .xml is shown here.

    Note:

    The mapping for crl, zip, dmg, sig, json, and arm extensions can be performed similar to as shown here for the .xml extension.

    Add Module Mapping options
  8. After each extension is added, the system displays the Add Module Mapping popup. Click Yes.

    Add Module Mapping popup, click Yes
  9. In the Application pool section change the App Pool Manager Pipeline mode to Classic as shown here:

    Application pool section
  10.  Add the http Handles for the xml, crl, zip, dmg, sig, json, and arm extension in the web.config file as shown here:

    httpHandles
  11. Copy the attached web.config file to the following two locations:

    • <initpub\wwwroot>\[AUSST root folder]\ACC\services\ffc\icons\
    • <initpub\wwwroot>\ [AUSST root folder]\ACC\services\ ffc\validation\

     

    Download

  12. Select the location:

    <initpub\wwwroot>\ [AUSST root folder]\ACC\services\ ffc\validation\

  13. Double-click MIME Types.

    Screenshot_3
  14. Click Add to add a MIME Type as shown below, and click OK.

    Screenshot_4

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

  15. Restart the website and run AUSST.

Running AUSST command without specific parameters

You can run AUSST from the command line by specifying only the --root parameter. In this case, a menu is displayed from which you can make your choice:


AdobeUpdateServerSetupTool.exe --root=<root location>

  1. Fresh Synchronization.
  2. Incremental Synchronization.
  3. Generate Client Configuration XML.
  4. Exit.

Your choice:

You can select one of the options to proceed further. The details of these options are available earlier in the article.

Error codes

The following error codes may be reported if update server is unsuccessful.

Error Code Error Message
2 Internal error occurred
3 Could not access specified path
4 Network failure
5 Server unresponsive
6 Proxy authentication failed
7 Output disk full
8 Write permission denied
9 File not found on server

Troubleshooting

Here are some common troubleshooting steps to follow if you face problems in deploying apps and updates through Adobe Update Server Setup Tool.

Ensure that the web server is set up correctly

If the web server that is used to distribute the apps and updates is not set up correctly, apps and updates might get downloaded from the Adobe update server (Adobe Update Server Setup Tool does that automatically), but will not be distributed to the clients.

Web server setup

 

As a simple test to check that the web server is running correctly, check that the updaterfeed.xml files on the update server can be accessed from browsers on the client machines. Essentially, you need to ensure that the web server is working, independent of the Adobe Update Server Setup Tool.
The updaterfeed.xml files are located at the following path, determined by the parameters in the overrides file:
http://<Domain>:<Port>/<URL>/updaterfeed.xml

For example, let us assume that the override file has the following entries:

<Overrides>
	<Application appID="webfeed">
        <Domain>http://serverabc.example.com</Domain>
        <URL>/ausst/webfeed/oobe/aam20/win/</URL>
        <Port>8089</Port>
    </Application>
    <Application appID="updates">
        <Domain>http://serverabc.example.com</Domain>
        <URL>/ausst/updates/oobe/aam20/win/</URL>
        <Port>8089</Port>
    </Application>
    <Application appID="webfeed20">
        <Domain>http://serverabc.example.com</Domain>
        <URL>/ausst/webfeed/oobe/aam20/win/</URL>
        <Port>8089</Port>
    </Application>
    <Application appID="updates20">
        <Domain>http://serverabc.example.com </Domain>
        <URL>/ausst/updates/oobe/aam20/win/</URL>
        <Port>8089</Port>
    </Application>
</Overrides>

In this case, the location of the updaterfeed.xml files are as follows:

http://serverabc.example.com:1234/Adobe/CS/webfeed/oobe/aam20/win/updaterfeed.xml

Check network connectivity

Ensure that there are not problems related to network connectivity and that the in-house server can connect to the Adobe update server. For example, check that you can access the default welcome page of the in-house server.

Ensure that there are no unwanted spaces in commands

When you run the AdobeUpdateServerSetupTool command, ensure that there are no spaces in the following cases:

  • Between parameters and the = sign
  • Between the = sign and arguments
    For example, the following command has an incorrect extra space between --root and the = sign
Unwantedspace
  • Anywhere in a path.

For example, the following command has an extra space between the quotation mark (") and the forward slash (/)

UnwantedspaceAnywhere

Specify full URLs with protocol and port number

The URLs for the server should include the protocol (such as http://). If the port number is different from the default value of 80, the port number should also be specified.

For example, the following section in the AdobeUpdater.Overrides file is incorrect because it does not specify the http:// protocol:

specifyURL

 

<URL>/Adobe/CS/webfeed/oobe/aam20/win/</URL>
<Port>1234</Port>

Note that in this example, the port number (1234) has been specified, which is required if the port number does not have the default value of 80.

Ensure that the location for storing the apps and updates has write permission

Ensure that the location on the server where the apps and updates are to be stored has the correct write permission. Otherwise, apps and updates might not be synced/downloaded on the in-house server. The server setup process is not complete unless all apps and updates are synced/downloaded on the in-house server

Ensure that the client configuration files are generated correctly on the in-house server

The client configuration files are generated at a location determined by the -genclientconf parameter of the AdobeUpdateServerSetupTool command as explained in the section Generating client configuration files of this document. Two files are generated, one each for Windows and Mac-OS clients. Check that the files are available in the respective locations on the in-house server.

Ensure that the client configuration files are deployed correctly on the client machines

After the client configuration files are generated on the in-house server, they are deployed on each client machine. The files are different for the Windows and the Mac-OS platforms.

The location for the file on each client machine is platform-specific. Ensure that the configuration files are deployed on the client machines at the locations as explained in the section Deploying client configuration files of this document.

Ensure that paths specified are absolute paths

Check that the paths provided to all the command-line options are absolute paths. AUSST does not support relative paths.

Use the fresh sync option if multiple apps and updates are visible on client machines

In exceptional cases, multiple apps/updates of the same package might get stored on the in-house server if the option of incremental update sync is specified. These will then be deployed to the client machines, and the users will see multiple copies of the packages on their machines. If this happens, perform the fresh update sync (one time) by running the following command:
AdobeUpdateServerSetupTool --root="/<update folder>" --fresh

This ensures that the correct single copy of the packages get downloaded to your in-house server, from where they are deployed to the client machines.

Use the fresh sync option if other troubleshooting steps fail

If you are using the incremental sync option and continue to get errors even after trying all the previous steps, perform fresh update sync (one time) by running the following command:
AdobeUpdateServerSetupTool --root="/<update folder>" --fresh

This will ensure that all updates from the Adobe update server are downloaded to your in-house server.

Perform a fresh install as a last resort

If all other troubleshooting steps fail, as a last resort perform a fresh install by running the following command:
AdobeUpdateServerSetupTool --root="/<update folder>" --fresh

Note:

When you perform a fresh install, the update folder and all its subfolders on your in-house server will be first deleted and then recreated with the updates from the Adobe update server. If you had created any additional files or folders in the update folder, they will be deleted. You should, therefore, back up any such files or folders before performing a fresh install.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy