Using AUSST and RUM to manage updates/installs with Linux web server?

Hey ​@Greg32395104qhgx , just wanted to add a bit more detail to what Bani shared above as there's a useful nuance worth unpacking for your specific setup.

About the AUSST binary

The AUSST binary itself — the part that actually syncs content down from Adobe's update servers — is only available for Windows and macOS, so that piece does need to run on one of those two platforms. This part Bani covered correctly.

About the web server side — this is where it gets interesting for your setup

The web serving layer is a completely separate concern. Adobe's own documentation states that before setting up AUSST you simply need an already up and running HTTP server such as Apache or IIS, and all it requires from the web server side is a folder root that maps to a valid HTTP URL. It just needs to serve static files over HTTP or HTTPS — it does not mandate what OS that web server runs on.

A split architecture approach that works for your environment

Here's how you can make this work without needing a dedicated Windows server:

Step 1 — Run the AUSST sync binary on a minimal Windows or macOS instance This doesn't need to be anything heavy. A lightweight VM, a spare endpoint, or even a minimal macOS instance is enough. AUSST runs as a scheduled task rather than a persistent always-on service, so it doesn't need dedicated server-grade hardware — just something that runs the sync job on a schedule and pushes the content to a shared location.

Step 2 — Point the AUSST output to a path served by your Linux Apache server Once the sync runs, the downloaded content just sits in a folder. As long as that folder is accessible via a valid HTTP URL, client machines will pull their updates from it without any issues. Your Linux Apache server handles all the actual file delivery to end user machines — and it does this job extremely well.

Step 3 — Configure your client machines to point to your Linux Apache server Once your Apache server is serving the AUSST content folder over HTTP or HTTPS, you simply configure your client machines to use that internal URL as their update source. This is standard AUSST client configuration and works the same regardless of what OS is running the web server.

On your distro choices All three of your options — Debian, openSUSE LEAP, and AlmaLinux — are well suited for the Apache file serving role here. Any of them would handle this cleanly. If reliability and long-term support are priorities in your environment, AlmaLinux is a particularly solid choice given its RHEL compatibility.

Quick summary

Yes, your Linux Apache server can absolutely handle the delivery side of this. You just need a minimal Windows or macOS touchpoint purely for running the sync binary itself, which can be as lightweight as a scheduled VM.