Maintain 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

How to maintain the internal update server environment setup with AUSST.

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

AUSST tool

Maintain server

3. Maintain internal update server

setup server

Common use cases

Once you have set up your internal update server, you perform some synchronization activities to maintain it for regular updates. 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. Client configuration files are required to create product groups.  
  • Get incremental updates from the Adobe Update server.
  • Create product configuration groups that enable 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.
 
Note:

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

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

Synchronize with the Adobe Update Server

After the initial setup, you must regularly synchronize your internal update server with the Adobe Update Server. It ensures that you have all the latest apps and updates. Run the following command:

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

Incremental Synchronization

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

  • New apps and updates posted on the Adobe update server since your last synchronization

   --incremental parameter pulls only the new apps

  • No new apps and updates posted on the Adobe update server

   --incremental parameter pulls nothing

In normal course, you should use --incremental option. However, 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.

This parameter cleans the root folder and any apps and updates present on the internal update server are first removed. Then, all the latest apps and updates available on the Adobe Update Server are downloaded to the server machine.

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.

Note:

The filterProducts option does not support Acrobat. The following scenarios cannot be used to filter Acrobat. Also, if you use the following filter options, Acrobat is always downloaded or updated, even if you don't include it in the filter. If you only want to download and update Acrobat, synchronize your server using the acrobatonly parameter.

AUSST syncs current Adobe desktop apps and the latest previous major versions of each. AUSST does not sync updates for apps we no longer sell. Find links to the apps that are available to download.​​ It implies that, when creating filters, you must specify only the versions of apps supported for download and installation.

The use cases below contain SAP Codes. If required, get the Complete list of SAP Codes.

Using the --filterProductsoption

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 (Sap Code: AEFT) as an example to download the given versions and updates:

  • All versions and updates:
    AdobeUpdateServerSetupTool.exe --root="<absolute location of the download folder>" --incremental --filterProducts="AEFT"
  • All updates of version 16.0:
    AdobeUpdateServerSetupTool.exe --root="<absolute location of the download folder>" --incremental --filterProducts="AEFT#16.0"
  • Update 16.1.3 of version 16:
    AdobeUpdateServerSetupTool.exe --root="<absolute location of the download folder>" --incremental --filterProducts="AEFT#16.0#16.1.3"
  • Update 16.0.1 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.0.1,PHSP"
    (Note: Different products are comma-separated.)

Using the --filterFilePathoption

If you have multiple products and updates that you want to include in a product filter, using the --filterProducts option can be cumbersome.

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>"

filterConfig.xml: Sample Structure

Similar to the example given above (--filterProducts), to create a filter to download update 16.0.1 of After Effects 16.0 and the latest version of Photoshop:

<Filters>     

  <Filter>

      <GroupName/>

             <FilterValue>AEFT#16.0#16.0.1,PHSP</FilterValue>

  </Filter>  

</Filters>

Complete list of SAP Codes.

Note:

If you are not creating product groups (described below),  you must create an empty GroupName node. If the GroupName node is not included, the .xml format will be incorrect and lead to errors why syncing.

By default a wild-card group is created for the generic filter commands.

Create product groups

Product groups help you to group products and versions based on the users who must 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 can access to their own respective product group.

1. Define product groups

You can create product groups by using one of the two options:

1.   --FILTERPRODUCTS option

2.   --FILTERFILEPATH option

1. Using the --filterProductsoption

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 (Sap Code: AEFT) and Photoshop (Sap Code: PHSP) as an example. Create two groups, named g1 and g2 which filter the following products and updates.

 group g1

group g2

All versions of After Effects and Photoshop update 19.1.2.

All updates of After Effects 16.0 and all latest 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.

Complete list of SAP Codes.

2. Using the --filterFilePathoption

If you want to include multiple groups, products, and updates in a product filter, using the --filterProducts option can be 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>"

filterConfig.xml: Sample Structure

Similar to the example given above (--filterProducts), to create a filter containing two groups: g1 and g2.

group g1

group g2

Latest version of After Effects and the 19.1.2 update of Photoshop version 19.0

Version 16.0 
of After Effects and all latest versions of Photoshop

<Filters>

      <Filter>

            <GroupName>g1</GroupName>

            <FilterValue>AEFT,PHSP#19.0#19.1.2</FilterValue>

      </Filter>

      <Filter>

            <GroupName>g2</GroupName>

             <FilterValue>AEFT#16.0,PHSP</FilterValue>

      </Filter>

</Filters>

Complete list of SAP Codes.

The Sap Code list shows the latest version of each application, which can be used together to construct the XML file for filtering.

2. Create client configuration (override) files

After you define product files and, optionally, product groups, you must generate client configuration files for these filters and 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

Note:

The groupName options is required if you have defined product groups.

3. Deploy client configuration (override) files

Next, deploy the generated client configuration(.overrides) files to the clients based on the product groups that you created. See Set 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. As a result, they occupy 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 the --incremental option 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>"

You cannot use the cleanup option without the filterProducts option to clean your server of the obsolete updates. 

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. You can select one of the options to proceed further. 

CLI Menu

Adobe logo

Sign in to your account