- Adobe Enterprise & Teams: Administration guide
- Plan your deployment
- Basic concepts
- Deployment Guides
- Deploy Creative Cloud for education
- Deployment home
- K-12 Onboarding Wizard
- Simple setup
- Syncing Users
- Roster Sync K-12 (US)
- Key licensing concepts
- Deployment options
- Quick tips
- Approve Adobe apps in Google Admin Console
- Enable Adobe Express in Google Classroom
- Integration with Canvas LMS
- Integration with Blackboard Learn
- Configuring SSO for District Portals and LMSs
- Add users through Roster Sync
- Kivuto FAQ
- Primary and Secondary institution eligibility guidelines
- Set up your organization
- Identity types | Overview
- Set up identity | Overview
- Set up organization with Enterprise ID
- Setup Azure AD federation and sync
- Set up Google Federation and sync
- Set up organization with Microsoft ADFS
- Set up organization for District Portals and LMS
- Set up organization with other Identity providers
- SSO common questions and troubleshooting
- Manage your organization setup
- Manage users
- Overview
- Administrative roles
- User management strategies
- Assign licenses to a Teams user
- Add users with matching email domains
- Change user's identity type
- Manage user groups
- Manage directory users
- Manage developers
- Migrate existing users to the Adobe Admin Console
- Migrate user management to the Adobe Admin Console
- Overview
- Manage products and entitlements
- Manage products and product profiles
- Manage products
- Buy products and licenses
- Manage product profiles for enterprise users
- Manage automatic assignment rules
- Entitle users to train Firefly custom models
- Review product requests
- Manage self-service policies
- Manage app integrations
- Manage product permissions in the Admin Console
- Enable/disable services for a product profile
- Single App | Creative Cloud for enterprise
- Optional services
- Manage Shared Device licenses
- Manage products and product profiles
- Get started with Global Admin Console
- Adopt global administration
- Select your organization
- Manage organization hierarchy
- Manage product profiles
- Manage administrators
- Manage user groups
- Update organization policies
- Manage policy templates
- Allocate products to child organizations
- Execute pending jobs
- Explore insights
- Export or import organization structure
- Manage storage and assets
- Storage
- Asset migration
- Reclaim assets from a user
- Student asset migration | EDU only
- Manage services
- Adobe Stock
- Custom fonts
- Adobe Asset Link
- Adobe Acrobat Sign
- Creative Cloud for enterprise - free membership
- Deploy apps and updates
- Overview
- Create packages
- Customize packages
- Deploy Packages
- Manage updates
- Adobe Update Server Setup Tool (AUSST)
- Adobe Remote Update Manager (RUM)
- Troubleshoot
- Manage your Teams account
- Renewals
- Manage contracts
- Reports & logs
- Get help
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.
3. Maintain internal update server
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.
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.
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>
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.
- Define your product groups based on the products and updates that required by different groups of users.
- Create .override files based on the different product groups.
- 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.
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 |
<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>
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
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.
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 after the --incremental option to clean up your server of all obsolete updates.
AdobeUpdateServerSetupTool.exe --root="<absolute location of the download folder>" --incremental --filterProducts="<sap codes you want to retain after cleanup>"
Followed by:
AdobeUpdateServerSetupTool.exe --root="<absolute location of the download folder>" --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. You can select one of the options to proceed further.