Windows Updates
Cache the Microsoft updates your Windows computers download, or run the experimental update source.
Artica keeps a local copy of the Microsoft updates that your Windows computers download.
The service runs inside ArticaREST.
It needs no Microsoft WSUS server and no Artica agent on the computers.
Two ways to use it
| Mode | What it does | Status |
|---|---|---|
| Microsoft super-cache | Computers keep their usual update source. Artica serves the downloaded files from its cache through Delivery Optimization. |
Tested on Windows 10, Windows 11 and Windows Server 2022. Recommended. |
| Decision-source mode | Artica answers the Windows Update protocol itself. The administrator chooses the catalogue and approves updates. |
Experimental. A full cycle up to an installed update has not been qualified. |
The two modes are independent.
The super-cache works without a catalogue, a profile or an approval.
Start with the super-cache unless you need to control which updates computers see.
Benefits
- A cumulative update crosses the Internet link once per site.
The next computers get it from the local network. - Windows, Office, Intune and Xbox content share one cache.
- The least requested files make room for new ones when the disk allowance is reached.
- The console shows how much was served from the cache and how much came from the Internet.
- One command on each computer,
artica-wuclient.exe, sets the client policy and can put the previous one back.
Open the console
Sign in with a system administrator account.
Open Windows Update from the updates menu, or open /system-wsus in the console.
The tabs are Status, Cached files, Super-cache statistics, Content objects, Update catalog, Statistics and Access log.
On Status, the Microsoft super-cache card comes first.
The cards below Decision-source mode (laboratory) belong to the experimental mode.
Microsoft super-cache
- Microsoft super-cache
How the cache works, how to enable it and how to check that computers use it. - Cached files
The files in the cache and how often computers ask for them. - Storage, quota and rotation
The disk allowance, the rotation of old files and the metric retention. - Statistics
Traffic counters, the part served from the cache and the cache occupation. - Deploy tool
Point a computer at the cache, or at the update source, and put the previous policy back. - Configure Windows clients
The same settings by Group Policy or PowerShell.
Decision-source mode (experimental)
- Listener and reverse proxy
The endpoint of the update source, its certificate and the allowed networks. - Windows profiles, Office and scheduling
The products and Windows builds used for catalogue queries. - Catalogue and approvals
Synchronize metadata and record approval decisions. - Approved content objects
Register trusted source URLs, sizes and SHA256 values.
Both modes
- Limitations and troubleshooting
Error messages, client checks and what is not qualified yet.
Current limits
- The super-cache does not decide which updates are installed.
The update source of each computer keeps that role. - In decision-source mode, a successful empty scan does not prove that a computer is fully patched.
- An approval records a local decision and its reason.
It does not prove native distribution or installation. - Per-computer installation reports are not available.