How to install and configure Adobe Update Server Setup Tool to set up an internal update server environment.

What is AUSST

In an enterprise environment, you usually have a large number of end users who require a number of Adobe apps and, subsequently, updates. Each user is required to download and install the apps individually. Allowing all your end users to individually download and install apps from the Adobe servers will consume a sizeable amount of network bandwidth in your organization.

To address the issue of network bandwidth consumption, Adobe provides Adobe Update Server Setup Tool (AUSST). AUSST enables you to centralize the download of Adobe apps and updates to a single server location. After this, you redirect your end users to download the Adobe apps from this internal server location. This ensures that, a single download from the Adobe servers is required for each app or update.

Notă:

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)

AUSST also hosts apps that can be deployed without their base versions, which can be installed using Adobe Creative Cloud desktop app.  

AUSST web server System requirements

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

Disk Space
  • Minimum space requirements for a full synchronization: 250 GB

Operating System

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

Deployment options

The following table lists the support of apps and updates for AUSST, RUM, and Creative Cloud desktop app: 

Type of product/product update Sync via 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

Why use AUSST

In an enterprise environment, you provide apps and updates to your end users via packages created in the Admin Console in different setups. In all the available setups, AUSST ensures that all apps and updates are downloaded once from the Adobe update servers and then served to your end users across the organization.

Install the Creative Cloud Desktop App and allow end users to install apps and updates

If you create Self-service or managed packages with elevated privileges, your users will have access to the Creative Cloud Desktop App. This allows the users to download install apps and updates (based on the package configuration options).

When you set up an internal update server, the apps and updates are downloaded once from the Adobe update servers. After this, when you set up your end user computers to use your internal update server, the apps and updates are downloaded from this server.

Creative Cloud Desktop Application

Also, if you create product configuration groups when setting up your end user computers, only the specified products are available (for install and update) from the Creative Cloud Desktop Application. For details about product configuration groups, see the Maintaining AUSST section below.

Install apps and allow end users to install updates

If you create managed packages and enable the apps panel, your users can update apps via the Help > Updates menu from with the installed apps.

When you set up an internal update server, the apps and updates are downloaded once from the Adobe update servers. After this, the end user updates are downloaded from your internal update server.

Help > Updates menu

Install apps via packages and updates via Remote update manager

In a managed environment, you want to disallow your end users from installing apps or updates individually. In this case, you do not enable the Apps panel.

When you set up an internal update server the apps and updates are downloaded once from the Adobe update servers. To install updates, you use Adobe's Remote Update Manager that gets the updates from your internal update server.

Set up AUSST server

The steps to set up an internal update server are described in the following sections. However, before proceeding you need an already up and running HTTP server (such as Apache or IIS) that can host and serve static file content.

Download AUSST

  1. In the Admin Console, navigate to Packages > Tools.

  2. On the Adobe Update Server Setup Tool card, click to download AUSST for your operating system.

    choose-ausst

Notă:

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

Atenție:

The paths provided to all the command-line options in the following section must be absolute paths. AUSST does not support relative paths.

Set up Internal Update Server

To set up your internal update server, ensure that you've downloaded the Adobe Update Server Setup Tool. Also, ensure that you have an up-and-running HTTP server (such as Apache or IIS) that can host and serve static file content.

See the section below for a step-by-step guide to setting up IIS or Apache for use with AUSST.

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

    Notă:

    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.

  2. Navigate to the folder in which you have downloaded the Adobe Update Server Setup Tool and enter the following command:

    Notă:

    The following commands show only the mandatory options to set up your server.
    For details of all the available command options, see the section Maintaining AUSST in this document. Or, to quickly get started, see the commonly used AUSST commands in the Common use cases section below.

    • 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:

    • The root update folder on your web server is at the file-system location:
      • macOS: /serverroot/updates/
      • Windows: c:\inetpub\wwwroot\updates
    • The web server's URL is http://serverabc.example.com:80
    • Within your web server, you set up the internal update server at
      http://serverabc.example.com:80/Adobe/CC

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

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

    Atenție:

    Ensure that there are no spaces around the = sign.

After the synchronization of apps and updates with the Adobe Update server is complete, the Adobe Update Server Setup tool creates an update directory structure at the root folder location. The folder structure 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 internal update server.

Verify your AUSST server setup

After you've set up the server, check the following:

  1. 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.
  2. Using a browser on a client computer, ensure that you can view Adobe products and updates in the root location that you specified in the --root option in the update server setup described above. If not, check that the root location has the correct write permissions and run the update server setup again.
  3. Confirm that you can view/download the products and updates from the client computers through a browser.
  4. When you're setting up your clients, you need to generate client configuration (.override) files. Generated the client configuration files (for Windows and macOS), have the following entries:

Windows

<Overrides>
    <Application appID="webfeed20">
        <Domain>http://10.41.35.164</Domain>
        <URL>/ausst/webfeed/oobe/aam20/win/</URL>
        <Port>8089</Port>
    </Application>
        ....
</Overrides>

macOS

<Overrides>

    <Application appID="webfeed20">

        <Domain>http://10.41.35.164</Domain>

        <URL>/ausst/webfeed/oobe/aam20/mac/</URL>

        <Port>8089</Port>

    </Application>

        ....

</Overrides>

From an end-user computer, use the Ping command (on both Windows and macOS), to test the following URLs:

  • To verify that your server supports extension-less files:

http://<server path>:<port number>/Adobe/ACC/services/ffc/icons/producticon

  • To verify that your server supports files with extensions:

If you have not set up product configuration groups:

http://<server path>:<port number>/Adobe/ACC/services/ffc/products/ffc.xml 

If you have set up product configuration groups:

http://<server path>:<port number>/Adobe/ACC/services/ffc/products/<groupName>ffc.xml 

Incremental sync

To set up your internal update server, you use the --fresh option that downloads all Adobe apps and updates from the Adobe Update server. However, this is usually a one-time operation that you perform when you first set up your update server. After this you want to get only new apps versions and updates.

To get an incremental update from the Adobe Update server, use the following command:

Notă:

The following commands show only the mandatory options to set up your server.
For details of all the available command options, see the section Maintaining AUSST in this document. Or, to quickly get started, see the commonly used AUSST commands in the Common use cases section below.

Windows:

AdobeUpdateServerSetupTool.exe --root="/serverroot/updates/Adobe/" --incremental

macOS:

AdobeUpdateServerSetupTool --root="/serverroot/updates/Adobe/" --incremental

To run this command at regular intervals, schedule a recurring job  - Using Task Scheduler for Windows or Crontab for macOS.

Set up clients to use AUSST server

After you have set up an internal update server to download Adobe apps and updates from the Adobe Update server, you still need to set up your end users to get their apps and updates from your internal update server.

For example, if end users use the Creative Cloud Desktop App to get the latest version of an app, the app should not be downloaded and installed from the Adobe Update server. The app should be installed from your internal update server. If you are creating and deploying packages on your end user computers, the installation of the apps in the packages should come from your internal update server.

Notă:

When you migrate from one version of AUSST to another, run the following commands to re-generate the client configuration files and update these on the client computers.

Generating client configuration (.override) files

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

Notă:

The following commands show only the mandatory options to sync your server. For a complete list of all the options, see the Syntax section, above.

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

Atenție:

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

This command creates two client configuration files (one for Windows platform, and one for Mac OS 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

Deploying client configuration files

If you are creating packages to deploy apps and updates to your end users

If you create packages to deploy apps and updates to your end users, follow these steps to include the client configuration files in the package:

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

  2. Open the AdobeUpdater.Overrides file in any text editor.

  3. Copy and paste the entire contents of the file into the Internal Update Server box and click Save.

Now your packages are created, with the client configuration files. When you deploy these packages on the end user computers, the files are included as part of the deployment. Your end users computers are subsequently redirected to your internal update server for app and updates.

If your end users are using Creative Cloud Desktop App

If your end user uses the Creative Cloud Desktop app to install apps and updates in your enterprise, then you need to deploy client configuration files on each client computer (based on the end user operating system)

  • macOS:
    /Library/Application Support/Adobe/AAMUpdater/1.0/AdobeUpdater.Overrides
  • Windows 10:
    %SYSTEMDRIVE%\ProgramData\Adobe\AAMUpdater\1.0\
    %SYSTEMDRIVE%\Program Files (x86)\Common Files\Adobe\UpdaterResources
  • Windows XP:
  • %SYSTEMDRIVE%\Documents and Settings\All Users\Application Data\Adobe\AAMUpdater\1.0\
  • Windows 7/Vista:
    %SYSTEMDRIVE%\ProgramData\Adobe\AAMUpdater\1.0\
    %SYSTEMDRIVE%\Program Files (x86)\Common Files\Adobe\UpdaterResources

Notă:

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

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.

Common use cases

The following use cases will help you further understand how to use AUSST in different commonly encountered scenarios.

For a detailed description of the functionality of AUSST, see the Maintaining AUSST section below. 

Use cases

Use case

Command

Sync all products and updates

(Not including legacy products)

AdobeUpdateServerSetupTool.exe --root="<root folder>" --incremental

Sync latest update of specific product. Example: Photoshop.

AdobeUpdateServerSetupTool.exe --root="<root folder>" --incremental --filterProducts="PHSP"

Sync specific version of a product for a specific group only. And generate client configuration files for this group.

Example: Group name: g1. Photoshop v18.1.3.

AdobeUpdateServerSetupTool.exe --root="<root folder>" --incremental --filterProducts="g1(PHSP#18.0#18.1.3)"

AdobeUpdateServerSetupTool.exe --root="<root folder>" --genclientconf="<output folder>" --url="<URL Path to root folder>" --groupName=g1

Sync a specific version for one group and latest version for another group.

Example: PHSP 18.3.1 for group g1. Latest version of Dreamweaver for g2 group.

AdobeUpdateServerSetupTool.exe --root="<root folder>" --incremental --filterProducts="g1(PHSP#18.0#18.1.3)|g2(DRWV)"

AdobeUpdateServerSetupTool.exe --root="<root folder>" --genclientconf="<output folder>" --url="<URL Path to root folder>" -- groupName=g1

 

AdobeUpdateServerSetupTool.exe --root="<root folder>" --genclientconf="<output folder>" --url="<URL Path to root folder>" -- groupName=g2

Sync all products of the groups that you have previously created

Note: Required if you have previously run the incremental option and defined groups.

AdobeUpdateServerSetupTool.exe --root="<root folder>" --incremental

Sync all products and updates that are not part of any group.

Note: Required if you have previously run the incremental option and defined groups.

AdobeUpdateServerSetupTool.exe --root="<root folder>" --incremental filterProducts="()"

Get all groups with products.

A file, groups.xml, is created at the filterFilePath location.

AdobeUpdateServerSetupTool.exe --root="<root folder>" --gengroupconfig --filterFilePath="<output folder>\groups.xml"

Remove obsolete products that are not required

Downloads of all products except for those specified in filter are removed.

AdobeUpdateServerSetupTool.exe --root="<root folder>" --incremental --cleanup --filterProducts="<sap codes you want to retain after cleanup>"

Admin wants to get updates on legacy products/version (See this document for list of legacy products)

AdobeUpdateServerSetupTool.exe --root="<root folder>" --incremental --legacyUpdates

Maintaining AUSST

Besides setting up an internal update server, AUSST also allows you to:

  • Generate client configuration files that are used to set up clients that will use your internal update server.
  • Get incremental updates from the Adobe Update server.
  • Create product configuration groups that enables different groups of users to download products and updates from their respective product groups.
  • Free up disk space on your internal update server by removing obsolete updates.

This section describes the AUSST command options.

Notă:

The fresh (setup) and incremental (maintenance) commands are mutually exclusive. However, all other commands described below are used in conjunction with these two commands.

For a quick understanding of using these commands, see the commonly used AUSST commands in the Common use cases section.

Synchronizing with the Adobe Update Server

After you initial setup, you will need to regularly synchronize your internal 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/CC" {--incremental | --fresh}

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 end user computers, 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 computer are first removed. Then, all the apps and updates available on the Adobe Update Server are downloaded to the computer.

In either case, the result is that your internal update server is up-to-date, and ready to update end user computers.

Acrobat-only Synchronization

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

Download products and updates based on a filter

When you use AUSST for fresh or incremental synchronization, you can choose the products and updates that you want to download.

Using the --filterProducts option

AdobeUpdateServerSetupTool.exe --root="<absolute location of the download folder>" --incremental --filterProducts="<Comma-separated list of Product Sap Codes>"

Replace --incremental with --fresh if you use this option during setup.

Using After Effects CC (Sap Code: AEFT) as an example:

  • To download all versions and updates:
    AdobeUpdateServerSetupTool.exe --root="<absolute location of the download folder>" --incremental --filterProducts="AEFT"
  • To download all updates of version 16.0:
    AdobeUpdateServerSetupTool.exe --root="<absolute location of the download folder>" --incremental --filterProducts="AEFT#16.0"
  • To download update 16.01 version 16.0:
    AdobeUpdateServerSetupTool.exe --root="<absolute location of the download folder>" --incremental --filterProducts="AEFT#16.0#16.01"
  • To download update 16.01 version 16.0 of After Effects along with all version of Photoshop (Sap Code: PHSP):
    AdobeUpdateServerSetupTool.exe --root="<absolute location of the download folder>" --incremental --filterProducts="AEFT#16.0#16.01,PHSP"
    (Note that different products are comma-separated)

Using the --filterFilePath option

If you have a number of products and updates that you want to include in a product filter, then using the --filterProducts option can get cumbersome and difficult to maintain. Instead, you can define you product filters in a filterConfig.xml file and use the --filterFilePath. Then include the details in a filterConfig.xml file.

AdobeUpdateServerSetupTool.exe --root="<absolute location of the download folder>" --incremental --filterFilePath="<absolute location of filterConfig.xml>"

Sample of Structure of filterConfig.xml

Similar to the examle given above (--filterProducts), to create a filter to download update 16.01 of After Effects CC 16.0 and all versions of Photoshop:

<Filters>
      <Filter>
             <FilterValue>AEFT#16.0#16.01</FilterValue>
      <Filter>
      <Filter>
              <FilterValue>AEFT#16.0#16.01</FilterValue>
      <Filter>
</Filters>

Create product groups

Product groups help you to group products and versions based on the users who need to be provided with specific products and updates.
  1. Define your product groups based on the products and updates that required by different groups of users.
  2. Create .override files based on the different product groups.
  3. Deploy the .override files to the different groups of users.
Each group of user will then have access to their own respective product group.

Define product groups

Using the --filterProducts option

AdobeUpdateServerSetupTool.exe --root="<absolute location of the download folder>" --incremental --filterProducts="<group name>(<Comma-separated list of Product Sap Codes>)|<group name>(<Comma-separated list of Product Sap Codes>)"

Replace --incremental with --fresh if you use this option during setup.

Using After Effects CC (Sap Code: AEFT) and Photoshop CC (Sap Code: PHSP) as an example. Create two groups, named g1 and g2.

  • g1 filters the following products and updates: All versions of After Effects CC (Sap Code: AEFT) and Photoshop CC (Sap Code: PHSP) update 19.1.2.
  • g2 filters the following products and updates: All updates of After Effects CC 16.0 and all versions of Photoshop.

AdobeUpdateServerSetupTool.exe --root="C:\inetpub\wwwroot\DynamicViews" --incremental --filterProducts="g1(AEFT,PHSP#19.0#19.1.2)|g2(AEFT#16.0,PHSP)"

Note that groups are separated by the pipe (|) character.

Using the ----filterFilePath option

If you have a number of groups, products, and updates that you want to include in a product filter, then using the --filterProducts option can get cumbersome and difficult to maintain. Instead, you can define you product filters in a filterConfig.xml file and use the --filterFilePath.

AdobeUpdateServerSetupTool.exe --root="<absolute location of the download folder>" --incremental --filterFilePath="<absolute location of filterConfig.xml>"

Sample of Structure of filterConfig.xml

Similar to the examle given above (--filterProducts), to create a filter to download update 16.01 of After Effects CC 16.0 and all versions of Photoshop:

<Filters>
      <Filter>
            <ConfigName>g1</ConfigName>
            <FilterValue>AEFT,PHSP19.0#19.1.2</FilterValue>
      <Filter>
      <Filter>
            <ConfigName>g1</ConfigName>
             <FilterValue>AEFT#16.0,PHSP</FilterValue>
      <Filter>
</Filters>

Create override files for product groups

After you create the product groups, you need to generate client configuration files for these groups.

Run AUSST for each of the groups that you defined above:

AdobeUpdateServerSetupTool.exe --root="<rootpath>" --genclientconf="<out folder path>" --url="<server url>" --groupName=g1

AdobeUpdateServerSetupTool.exe --root="<rootpath>" --genclientconf="<out folder path>" --url="<server url>" --groupName=g2

Deploy product group-based client configuration

After you've defined the product groups and generated the client configuration files, deploy these files to the clients based on the product groups that you created. See Setting up clients to use the internal update server for details about generating and deploying client configuration files.

Cleanup obsolete products and updates

As Adobe releases a new product update, previous updates that you download using AUSST become obsolete and, as a result, take up unnecessary disk space on your internal update server.

For example, if you downloaded Photoshop update 19.1.0 and then later downloaded 19.1.1, you no longer require 19.1.0.

Use the --cleanup option along with --fresh or --incremental options to simultaneously clean up your server of all obsolete updates.

AdobeUpdateServerSetupTool.exe --root="<absolute location of the download folder>" --incremental --cleanup --filterProducts="<sap codes you want to retain after cleanup>"

AUSST CLI Menu

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.

Set 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.

Set up HTTP server

You can use any HTTP server. For this example, XAMPP for macOS 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 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.”
  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

Set 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:

    Notă:

    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.

    Notă:

    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 dialog box.

    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:

    • C:\inetpub\wwwroot[AUSST root folder]\ACC\services\ffc\icons\
    • C:\inetpub\wwwroot[AUSST root folder]\ACC\services\ffc\validation\

     

    Descărcare

  12. Select the location:

    C:\inetpub\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.

Troubleshooting

Follow these troubleshooting steps if you face problems in deploying apps and updates through Adobe Update Server Setup Tool:

Error logs

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/

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

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

To test that the web server is running correctly, see Verify your AUSST server setup in the Set up AUSST server section above.

Check network connectivity

Ensure that there are not problems related to network connectivity and that the internal update server can connect to the Adobe update server. For example, check that you can access the default welcome page of the internal update 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
Unwanted space
  • Anywhere in a path.

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

Unwanted space anywhere in path

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:

Specify URL

<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 internal update server. The server setup process is not complete unless all apps and updates are synced/downloaded on the internal update server.

Ensure that the client configuration files are generated correctly on the internal update 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 internal update server.

Ensure that the client configuration files are deployed correctly on the end user computers

After the client configuration files are generated on the internal update server, they are deployed on each end user computer. The files are different for the Windows and the Mac-OS platforms.

The location for the file on each end0user computer is platform-specific. Ensure that the configuration files are deployed on the end user computers 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 computers

In exceptional cases, multiple apps/updates of the same package might get stored on the internal update server if the option of incremental update sync is specified. These will then be deployed to the end user computers, and the users will see multiple copies of the packages on their computers. 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 internal update server, from where they are deployed to the end user computers.

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 internal update server.

Această lucrare este oferită sub licență Atribuire-Necomercial-FărăModificări 3.0 Ne-adaptată Creative Commons  Postările pe Twitter™ şi Facebook nu sunt acoperite de condiţiile de licenţiere Creative Commons.

Prevederi legale   |   Politică de confidențialitate online