Artica provides an internal update endpoint and a cache for approved Microsoft files.
The service runs inside ArticaREST.
It does not require a Microsoft WSUS server or an Artica agent on Windows clients.
The native Windows Update integration is experimental.
A complete cycle from catalogue discovery to an installed update has not been qualified.
Use a pilot environment before changing the update source of managed computers.
¶ Benefits
- Reuse files already stored on Artica when several computers request the same approved content.
- Limit new content storage without stopping transfers when the cache is full.
- Measure requests, bytes sent to clients, bytes received from sources and local reuse.
- Choose direct TCP access or a Unix socket behind a reverse proxy.
- Manage several Windows profiles and Office content families from one console.
¶ How a file request is handled
- Artica checks the client network and the approved content manifest.
- An existing object is served locally.
- A missing approved object is fetched from its registered Microsoft HTTPS URL.
- The outgoing Artica proxy settings are used when configured.
- Artica checks the expected size and SHA256 before publishing a new cached copy.
- When quota or free space is insufficient, the missing object is relayed without another local copy.
An unknown or unapproved object is rejected.
Artica does not forward arbitrary client URLs to the Internet.
¶ 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, Content objects, Update catalog and Statistics.
¶ Administrator guides
- Listener and reverse proxy
Choose the client endpoint, certificate and allowed networks. - Storage and cache limits
Set the storage allowance and metric retention. - Windows profiles, Office and scheduling
Select products and describe the Windows builds used for catalogue queries. - Approved content objects
Register trusted source URLs, sizes and SHA256 values. - Catalogue and approvals
Synchronize metadata and record approval decisions. - Traffic statistics
Read request counts, transfer volumes and cache occupation. - Configure Windows clients
Set up a reversible pilot with Group Policy or PowerShell. - Deploy tool
Point a pilot computer at the endpoint from a command or a window, and put the previous policy back. - Limitations and troubleshooting
Check service errors and understand what is not yet qualified.
¶ Current limits
- 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. - Native routing between several Windows profiles is not qualified.
Use one profile for a native client pilot. - Office selection controls approved file delivery.
It does not create an Office update repository or change Office client settings. - Per-computer installation reports and trusted deployment groups are not available.
The screenshots show a test appliance with no imported catalogue and no registered content.
Its counters are real, including the zero values.