Set up the internal update server

  1. Adobe Enterprise & Teams: Administration guide
  2. Plan your deployment
    1. Basic concepts
      1. Licensing
      2. Identity
      3. User management
      4. App deployment
      5. Admin roles
    2. Deployment Guides
      1. Named User deployment guide
      2. SDL deployment guide
    3. Deploy Creative Cloud for education
      1. Deployment guide
      2. Integration with Canvas LMS
      3. Integration with Blackboard Learn
      4. Configuring SSO for District Portals and LMSs
      5. Kivuto FAQ
      6. Primary and Secondary institution eligibility guidelines
  3. Set up your organization
    1. Set up identity
      1. Identity types | overview
      2. Set up organization with Enterprise ID
      3. Set up organization with Federated ID
        1. SSO overview
        2. Setup Azure Connector and sync
          1. Set up SSO with Microsoft via Azure OIDC
          2. Add Azure Sync to your directory
          3. Azure Connector FAQ
        3. Set up Google Federation and sync
          1. Set up SSO with Google Federation
          2. Add Google Sync to your directory
          3. Google federation FAQ
        4. Generic SAML
          1. Set up SSO with other SAML providers
          2. Set up SSO with Microsoft Azure ADFS
          3. SSO Common questions
          4. SSO Troubleshooting
        5. Education SSO
          1. Configure SSO for District Portals and LMS
          2. Common questions
          3. Dovetail
      4. Verify ownership of a domain
      5. Add and manage domains
      6. Link domains to directories
      7. Use directory trust to add pre-claimed domains
      8. Migrate to new authentication provider
    2. Asset settings
    3. Authentication settings
    4. Privacy and security contacts
    5. Console settings
    6. Manage encryption
  4. Manage products and entitlements
    1. Manage users
      1. Overview
      2. Administrative roles
      3. User management techniques
        1. Manage users individually   
        2. Manage multiple users (Bulk CSV)
        3. User Sync tool (UST)
        4. User management API (UMAPI)
        5. Microsoft Azure Sync
        6. Google Federation Sync
      4. Change user's identity type
      5. Manage user groups
      6. Manage directory users
      7. Manage developers
      8. Migrate existing users to the Adobe Admin Console
      9. Migrate user management to the Adobe Admin Console
    2. Manage products and product profiles
      1. Manage products
      2. Manage product profiles for enterprise users
      3. Manage self-service policies
      4. Manage app integrations
      5. Manage product permissions in the Admin Console  
      6. Enable/disable services for a product profile
      7. Single App | Creative Cloud for enterprise
      8. Optional services
    3. Manage Shared Device licenses
      1. What's new
      2. Deployment guide
      3. Create packages
      4. Recover licenses
      5. Migrate from Device Licensing
      6. Manage profiles
      7. Licensing toolkit
      8. Shared Device Licensing FAQ
  5. Manage storage and assets
    1. Storage
      1. Manage enterprise storage
      2. Adobe Creative Cloud: Update to storage
      3. Manage Adobe storage
    2. Asset migration
      1. Automated Asset Migration
      2. Automated Asset Migration FAQ  
      3. Manage transferred assets
    3. Reclaim assets from a user
    4. Student asset migration | EDU only
      1. Automatic student asset migration
      2. Migrate your assets
  6. Manage services
    1. Adobe Stock
      1. Adobe Stock credit packs for teams
      2. Adobe Stock for enterprise
      3. Use Adobe Stock for enterprise
      4. Adobe Stock License Approval
    2. Custom fonts
    3. Adobe Asset Link
      1. Overview
      2. Create user group
      3. Configure Adobe Experience Manager 6.x Assets
      4. Configure and install Adobe Asset Link
      5. Manage assets
      6. Adobe Asset Link for XD
    4. Adobe Sign
      1. Set up Adobe Sign for enterprise or Teams
      2. Adobe Sign - Team feature Administrator
      3. Manage Adobe Sign on the Admin Console
    5. Creative Cloud for enterprise - free membership
      1. Overview
      2. Getting started
  7. Deploy apps and updates
    1. Overview
      1. Deploy and deliver apps and updates
      2. Plan to deploy
      3. Prepare to deploy
    2. Create packages
      1. Package apps via the Admin Console
      2. Create Named User Licensing Packages
      3. Adobe templates for packages
      4. Manage packages
      5. Manage device licenses
      6. Serial number licensing
    3. Customize packages
      1. Customize the Creative Cloud desktop app
      2. Include extensions in your package
    4. Deploy Packages 
      1. Deploy packages
      2. Deploy Adobe packages with SCCM
      3. Deploy Adobe packages with ARD
      4. Install products in the Exceptions folder
      5. Uninstall Creative Cloud products
      6. Use Adobe provisioning toolkit enterprise edition
      7. Adobe Creative Cloud licensing identifiers
    5. Manage updates
      1. Change management for Adobe enterprise and teams customers
      2. Deploy updates
    6. Adobe Update Server Setup Tool (AUSST)
      1. AUSST Overview
      2. Set up the internal update server
      3. Maintain the internal update server
      4. Common use cases of AUSST   
      5. Troubleshoot the internal update server
    7. Adobe Remote Update Manager (RUM)
      1. Use Adobe Remote Update Manager
      2. Channel IDs for use with Adobe Remote Update Manager
      3. Resolve RUM errors
    8. Troubleshoot
      1. Troubleshoot Creative Cloud apps installation and uninstallation errors
      2. Query client machines to check if a package is deployed
      3. Creative Cloud package "Installation Failed" error message
    9. Create packages using Creative Cloud Packager (CC 2018 or earlier apps)
      1. About Creative Cloud Packager
      2. Creative Cloud Packager release notes
      3. Application packaging
      4. Create packages using Creative Cloud Packager
      5. Create named license packages
      6. Create packages with device licenses
      7. Create a license package
      8. Create packages with serial number licenses
      9. Packager automation
      10. Package non-Creative Cloud products
      11. Edit and save configurations
      12. Set locale at system level
  8. Manage your account
    1. Manage your Teams account
      1. Overview
      2. Update payment details
      3. Manage invoices
      4. Change contract owner
    2. Assign licenses to a Teams user
    3. Add products and licenses
    4. Renewals
      1. Teams membership: Renewals
      2. Enterprise in VIP: Renewals and compliance
    5. Purchase Request compliance
    6. Value Incentive Plan (VIP) in China
    7. VIP Select help
  9. Reports & logs
    1. Audit Log
    2. Assignment reports
    3. Content Logs
  10. Get help
    1. Contact Adobe Customer Care
    2. Support options for teams accounts
    3. Support options for enterprise accounts
    4. Support options for Experience Cloud

Set up the internal update server and then set up clients to use the server.

Adobe Update Server Setup Tool (AUSST) enables you to centralize the download of Adobe apps and updates to a single server location. 

AUSST tool

Maintain server

setup server

2. Set up the internal update server 

Common use cases

You can set up an internal update server, with AUSST. Before setting up an internal update server you need an already up and running HTTP server (such as Apache or IIS). An HTTP server can host and serve static file content.  

You can download the Adobe apps and updates from the Adobe Update server to your internal update server. You need to set up your clients or end users computers to get their apps and updates from your internal update server.

To check the system requirements, see AUSST web server system requirements.

Set up an HTTP server for use with AUSST

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

Set up an Apache HTTP server

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

  1. Download and install an HTTP server. 

  2. 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.”
  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.

    Apache Server

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

Set up IIS

Before you begin: You need a platform such as Windows Server 2008 R2 and above.

Ping the server from another computer to see if it is reachable.

Ping <server ip or hostname>

Ping

Note:

The AUSST tool and the update mechanism used by CCD and RUM support IIS 7.5 and above, when an overrides file is in place on the client workstations. The screenshots and instructions below demonstrate IIS 8.5; the same settings should be applied to other versions of IIS.

  1. 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. 
    Roles

    •  Click Install on the Confirmation screen. 
    Confirm_Install

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

  2. 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.
    Directory Browsing

    •  Enable the Directory Browsing service.
    Enable Drirectory Browsing

  3. Select the server displayed in the left pane. 

  4. Click the Handler Mappings of the required website. 

    Handler Mappings

    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.

  5. Select the Add Module Mapping option. 

    Add Module Mapping

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

    Add Module Mapping

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

    Extenstion added

  8. Similarly add Module Mapping for the given extensions:

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

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

  9. 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 Mime Type

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

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

    Mime Types

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

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

    Local Host

Set up the internal update server with AUSST tool

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.

See Set up IIS for a step-by-step guide to setting up IIS for use with AUSST.

Download 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 computer.

 In the  Admin Console navigate to Packages > Tools.
 

Tools

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

Ausst tool

Set up the internal update server

Ensure that you've downloaded the latest version of the  Adobe Update Server Setup Tool from the admin console, to set up your internal update server.  

Note:

To ensure that the Update server runs without interruption confirm that you have allowed access to the endpoints in Adobe Creative Cloud Network Endpoints.

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

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

    Updates folder

    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/

    server root

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

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

Note:

A full fresh sync needs approximately 300 GB(which may vary depending on the size of Adobe apps). Refer to the Common use cases for a selective sync.

After the synchronization of apps and updates with the Adobe Update server is complete, the AUSST tool creates an updated 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 internal update server setup

  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.

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

    Server Host

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

    ausst_producticon

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

    Note:

    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.

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

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:

Note:

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. Or, to quickly get started, see the commonly used AUSST commands in the Common use cases.

Windows:

AdobeUpdateServerSetupTool.exe --root="C:\inetpub\wwwroot\updates" --incremental

macOS:

AdobeUpdateServerSetupTool --root="/Library/WebServer/Documents/ausst/" --incremental

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

Note:

A full fresh sync needs approximately 300 GB(which may vary depending on the size of Adobe apps). Refer to the Common use cases section for a selective sync.

Set up clients to use the internal update 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.

Note:

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.

Generate client configuration (.override) files

Client configuration(.override files) are required to create product groups.  Later you can deploy the generated client configuration(.override files) to the different groups of users. To generate the configuration files, enter the following command in a command shell or terminal (using your own server information):

Note:

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

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

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

     

    Note:

    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.

    In this example, the new files are:

    • ·Windows:
      \serverroot\config\AdobeUpdaterClient\win\AdobeUpdater.Overrides
    • ·macOS:
      /serverroot/config/AdobeUpdaterClient/mac/AdobeUpdater.Overrides
    Config

Windows

<Overrides>

<Application appID="webfeed">

<Domain>http://ausstserver.example.com</Domain>

<URL>/updates/webfeed/oobe/aam10/win/</URL>

</Application>

<Application appID="updates">

<Domain>http://ausstserver.example.com</Domain>

<URL>/updates/updates/oobe/aam10/win/</URL>

</Application>

<Application appID="webfeed20">

<Domain>http://ausstserver.example.com</Domain>

<URL>/updates/webfeed/oobe/aam20/win/</URL>

</Application>

...

</Overrides>

macOS

<Overrides>

<Application appID="webfeed">

<Domain>http://ausstserver.example.com</Domain>

<URL>/updates/webfeed/oobe/aam10/mac/</URL>

</Application>

<Application appID="updates">

<Domain>http://ausstserver.example.com</Domain>

<URL>/updates/updates/oobe/aam10/mac/</URL>

</Application>

<Application appID="webfeed20">

<Domain>http://ausstserver.example.com</Domain>

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

</Application>

...

</Overrides>

Deploying client configuration files

There are two ways of deploying the client configuration files(.overrides).

1. By including .overrides in the package itself

When you create packages to deploy apps and updates to your end users, follow the given 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.  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. 

    Internal update server preference

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

    NUL Managed Package
    Named user language Managed Package

    NUL Self service Package
    Named user language Self-Service Package

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.

2. Manually placing .overrides at desired path

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 (Intel) & macOS (ARM):
    /Library/Application Support/Adobe/AAMUpdater/1.0/
  • Windows 10:
    %SYSTEMDRIVE%\ProgramData\Adobe\AAMUpdater\1.0\
    %SYSTEMDRIVE%\Program Files (x86)\Common Files\Adobe\UpdaterResources
  • Windows ARM:
    %SYSTEMDRIVE%\ProgramData\Adobe\AAMUpdater\1.0\
    %SYSTEMDRIVE%\Program Files\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

Additional videos to setup the internal update server

Note:

The content and voice-over for this video is currently available in English only.

Set up the internal update server on Windows

Created by: Nikhil Gupta

Set up the internal update server on Mac

Created by: Nikhil Gupta
Adobe logo

Sign in to your account