Adobe Update Server Setup Tool overview

When many users need Adobe apps and updates, individual downloads from Adobe servers can strain your network. AUSST is a server-side, command-line tool that downloads content from Adobe to one internal server. After setup, end-user computers get apps and updates from that server instead of from Adobe.

AUSST scope

AUSST handles the following:

• Sync Adobe apps and updates from Adobe to your internal server.
• Serve that content to client computers through the Creative Cloud desktop app, in-app updates, or Remote Update Manager (RUM).
• Let you limit what is synced. See Filter Adobe apps with AUSST.

AUSST doesn’t:

• Install apps. Installation occurs via packages you create in the Admin Console or in the Creative Cloud desktop app.
• Run silent or unattended installations. These are part of package deployment. See Packaging overview and tools and Deploy packages manually. To point packaged apps at your server, see Configure an internal update server for packages.
• Update the Creative Cloud desktop app. Users must update it regularly, or you must deploy an updated package. See Update and rebuild outdated packages and Deploy updates overview.
• Sync Substance apps, or updates for apps that are no longer sold.

Supported apps and updates

• AUSST syncs the current Adobe desktop apps and the latest previous major version of each. For Acrobat, it syncs only the current version. See the apps available to download.
• Apps and updates synced through AUSST can be installed through the Creative Cloud desktop app. Updates can also be installed through Remote Update Manager (RUM).
• AUSST also hosts apps that can be deployed without their base versions. Users install these through the Creative Cloud desktop app.

AUSST web server requirements

• Disk space: 1.2 TB or more for full synchronization. See Filter Adobe apps with AUSST.
• Operating system: Windows Server 2008 R2 or later, or macOS High Sierra (10.13) or later
• RAM: 8 GB or more

Deployment options

AUSST works with the following installation methods:

Deployment scenarios

You provide apps and updates to end users through packages created in the Admin Console. In every scenario, AUSST downloads content from Adobe’s servers once and serves it to users across your organization.

Users install from the Creative Cloud desktop app

If you create self-service or managed packages with elevated privileges, users can open the Creative Cloud desktop app to download and install apps and updates, based on the package configuration. With an internal update server, content is retrieved from Adobe each time you synchronize. Once client configuration files are in place, users download from your server.

If you create product configuration groups, only the specified products are available for installation and update in the desktop app.

Install by package, update in the app

If you create managed packages and enable the apps panel, users can update apps from Help > Updates inside the installed apps. Apps are installed from your package. Updates are retrieved from your internal server.

Install by package, update with Remote Update Manager (RUM)

Deploy apps to users through packages. Then use RUM, a command-line tool that runs on client computers, to install updates from your internal server. This scenario also suits Acrobat updates, which can’t be installed through the Creative Cloud desktop app. For setup and syntax, see Deploy and manage updates with RUM.

If your internal update server is unavailable, end-user computers won't receive Adobe updates until it's back online. Administrators can allow client machines to bypass the internal server and retrieve updates directly from Adobe servers when required, helping your team feel prepared for unexpected server issues.