Requirement
Last updated on
Nov 4, 2026
Install an HTTP server, then configure it to serve the files synchronized by AUSST.
AUSST is a command-line tool that downloads Adobe apps and updates to a folder on your internal server. Your web server then serves that folder to client computers on your network.
Confirm the following before you start.
|
|
Detail |
|---|---|
|
Admin Console access |
You can open Packages > Tools in the Admin Console to download AUSST. |
|
Web server |
A running HTTP server that can serve static files, such as IIS on Windows or Apache on macOS. |
|
Operating system |
|
|
Storage |
The required space depends on which apps you synchronize. To reduce it, filter the apps AUSST synchronizes. |
|
Memory |
8 GB RAM or more |
|
Network access |
The server can reach the endpoints listed in Adobe Creative Cloud network endpoints. If your network uses a proxy, see Set up proxy support for Creative Cloud apps. |
|
Permissions |
The account that runs AUSST has write permission to the root folder you create in step 3. |
|
Client access |
Client computers can reach the server on the port you choose. Open that port in the server's firewall. |
For the full list of what AUSST synchronizes and what it doesn't, see the AUSST overview.
Choose HTTP or HTTPS
You can configure your AUSST server to support connections over HTTP or HTTPS. If you use HTTPS, ensure the certificate is recognized as valid by the client computers.
Download AUSST
AUSST is a command-line tool and needs no separate installation. You can place it anywhere on the computer.
In the Admin Console, go to Packages > Tools.
On the Adobe update server setup tool card, select Download for your operating system.
Always download AUSST from the Admin Console so that you get the current release. Don't reuse a copy from an earlier setup. To see what changed between releases, read the AUSST release notes.
Configure the web server
Follow the steps for your operating system:
Use absolute paths everywhere in this article. AUSST doesn't support relative paths.
Configure IIS on Windows
The directory browsing, module mappings, and MIME types you configure in this section apply to the website you select in IIS Manager, and they affect all content that website serves. To avoid changing how other sites on the server behave, create a new website for the AUSST files and apply these settings to it rather than to the default website.
Prepare the server
Install IIS using Server Manager. See Microsoft's documentation for installing IIS on your version of Windows Server.
While adding role services, also select ISAPI Extensions and ISAPI Filters.
Select Install, then restart the server after the installation completes.
Confirm the server is reachable from another computer. For example, run ping <server IP or host name>. If your network blocks ping, open the server's address in a browser instead.
Enable directory browsing
Go to Server Manager > Tools > IIS Manager.
Select the website you use for AUSST in the Connections pane, then open the Directory Browsing service.
In the Actions pane, select Enable to turn on the service.
Add module mappings
In IIS Manager, select the website, then open Handler Mappings.
Select Add Module Mapping.
Enter the parameter values for .xml, then select OK. Select Yes when IIS asks you to confirm the ISAPI extension.
Repeat the steps for each of these extensions: .crl, .zip, .dmg, .sig, .json, .arm.
Add MIME types (Acrobat and Reader)
If you synchronize Acrobat and Acrobat Reader, add the application/octet-stream MIME type for .msp, .pkg, and .arm.
Select the website you use for AUSST in the left pane, then open MIME Types.
Select Add.
For File name extension, enter the extension (for example, .msp). For MIME type, enter application/octet-stream.
Repeat for .pkg and .arm.
Confirm that the web server works by opening a web browser on the server itself.
Apache on macOS
Download and install an HTTP server, such as XAMPP, on macOS.
Start the web server. In XAMPP, open the Manage Servers tab, select Apache Web Server, then select Start.
Create a folder named updates inside the web server's document root. In XAMPP, the document root is the htdocs folder.
Confirm the folder is reachable in a browser. For example: http://<server name>/updates/.
If you already synchronized AUSST files on another computer, copy them into the updates folder and set permissions on the folder so the web server can read all files inside it.
Create the root folder and confirm it's reachable
The root folder is the location where AUSST stores the synchronized files. It must be inside your web server's document root so that it maps to a valid HTTP URL.
Create the folder. For example:
- Windows: C:\inetpub\wwwroot\updates
- macOS: <web server document root>/updates
Confirm the AUSST account has write permission to the folder.
In a browser, open the folder's URL. For example: http://ausstserver.example.com/updates/.
Run the first synchronization
The first synchronization downloads all available apps and updates from Adobe, so it takes time. Make sure the server has the free disk space listed under Before you begin.
Open Command Prompt (Windows) or Terminal (macOS), and go to the folder that contains AUSST. For example: cd C:\AUSST.
Run the fresh synchronization command using the absolute path of the root folder from step 3:
For example: AdobeUpdateServerSetupTool.exe --root="C:\inetpub\wwwroot\updates" --fresh
- Windows: AdobeUpdateServerSetupTool.exe --root="<absolute path of root folder>" --fresh
- macOS: AdobeUpdateServerSetupTool --root="<absolute path of root folder>" --fresh
Don't put spaces around the = sign. Precede every option with two hyphens (--).
AUSST creates a directory structure under the root folder that matches the structure of the Adobe update server and downloads the apps and updates into it.
If the synchronization fails, download the remaining products with the incremental command:
- Windows: AdobeUpdateServerSetupTool.exe --root="<root folder>" --incremental
- macOS: AdobeUpdateServerSetupTool --root="<root folder>" --incremental
If errors persist, see Fix AUSST sync and configuration errors.
Verify the server
After the synchronization completes, verify the server from a client computer. Replace <server name> with your server's name. If your server uses a port other than the default or uses HTTPS, include the protocol and port in each URL.
Open the web server's home page in a browser. Confirm that you can browse the directories by selecting the directory links.
Confirm the server serves files without an extension. Open http://<server name>/updates/ACC/services/ffc/icons/producticon. You should see a string of letters. Do this check before the next one.
Confirm that the server serves files with an extension. Open the following file:
- If you haven't 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
To check from the command line instead, use a standard HTTP request, such as curl or Invoke-WebRequest, against ffc.xml and specify the expected response.
If a check fails on a client but works on the server, check the server's firewall settings. Next, configure clients to use the internal update server by generating the .override files.
Keep the server current
Use --fresh only once, when you first set up the server. After that, run an incremental synchronization to download new app versions and updates:
- Windows: AdobeUpdateServerSetupTool.exe --root="C:\inetpub\wwwroot\updates" --incremental
- macOS: AdobeUpdateServerSetupTool --root="<root folder>" --incremental
To run the command at regular intervals, schedule a recurring job with Task Scheduler (Windows) or cron (macOS). For more, see Maintain the internal update server.
