WSUS alternative

Control Windows updates without running a WSUS

fliix Ops rolls out Windows updates in maintenance windows, staggered after Patch Tuesday, and shows per device what was installed and what is missing. Devices download straight from Microsoft, so you need no update server in your own network.

No update server, no database Reaches devices outside the company network Update history per device, kept for 25 months

The short answer

What can replace WSUS?

Microsoft deprecated WSUS in September 2024 and has not developed the service further since. It is still included in Windows Server 2025. Anyone who wants to replace it needs three things: a schedule for updates, a stagger between test devices and all others, and proof per device.

fliix Ops does this without a server of your own. An agent on every Windows device installs the quality and security updates in the maintenance window you define, for example pilot devices one day and all others seven days after Patch Tuesday. The updates come straight from Windows Update.

The approach differs from WSUS: you do not approve each update individually. You stagger the devices in time and hide a single update when it causes problems. What that means is listed under the limits below.

Migration

From WSUS to maintenance windows in four steps

  1. 1

    Roll out the agent

    You deploy the fliix Ops agent by Group Policy, Intune or installer. From the first report you see the pending updates per device.

  2. 2

    Create and assign maintenance windows

    One window for pilot devices shortly after Patch Tuesday, one for all others a few days later, one for servers. Each applies as the default for all clients or servers of a tenant, or to a tag, a group or a single device.

  3. 3

    Check the WSUS policy

    The agent searches for and downloads updates directly from Microsoft. If your WSUS policy blocks connections to Windows Update (setting "Do not connect to any Windows Update Internet locations"), lift that setting for the devices before the first window.

  4. 4

    Switch off WSUS

    Once the first windows run cleanly, you remove the remaining WSUS policy from the devices and decommission the server.

What you get instead of WSUS

The jobs of WSUS, without the server

Staggering instead of rings: windows 0 to 27 days after Patch Tuesday, weekly, or on the nth weekday of the month.
The plan is stored on the device and runs by its clock, even when the device has no connection to fliix Ops at window time.
A client that was off during the window catches up on the run for up to 7 days by default. Switched-off devices on a network cable can be woken before the window.
Restart per window: if needed, always or never. Signed-in users are asked. Without an answer the device restarts after 60 seconds by default or, if you choose so, only at the deadline (1 to 24 hours).
A single update can be hidden per device until it has been fixed.
Update history per device with error code and trigger, kept for 25 months, also in the monthly report per tenant.
Missing security updates and the oldest open gap are shown as figures on the device.
New Windows versions arrive through a separate step with pilot devices and a way back, never alongside the monthly updates.
Tenants separate customers or sites, each with its own windows and reports.

Limits

Where fliix Ops works differently from WSUS

  • There is no approval per update and device group. All pending updates that are not hidden on the device are installed.
  • fliix Ops does not cache updates. Every device downloads from Microsoft and needs an internet connection for it. This is not for isolated networks without internet access.
  • Updates for other Microsoft products come through Microsoft Update; on Windows Server 2016 only the updates from Windows Update are installed. Programs from other vendors are updated through WinGet and Chocolatey, as far as the WinGet catalog or the fliix Ops Chocolatey repository knows them.
  • fliix Ops manages Windows 10, Windows 11 and Windows Server 2016 and later (64-bit). Older systems are out of scope.

Licence

Which licence includes this?

Windows updates, Store apps and restarts in the maintenance window are part of Windows Agents Lite and Full. Drivers, BIOS, WinGet, Chocolatey, own scripts and the security check in the window are part of Full.

FAQ

Frequently asked questions about moving away from WSUS

Is WSUS being switched off?
Not so far. Microsoft deprecated WSUS in September 2024: it receives no new features, but it is still included in Windows Server 2025. Microsoft did not name an end date with that announcement.
Can I test updates before all devices receive them?
Yes, through the stagger in time. Pilot devices get a window shortly after Patch Tuesday, all others one a few days later. If the pilot shows a problem, you pause the remaining windows or hide the update on the affected devices.
Can I hold back a single update?
Yes, per device. A hidden update is not installed until you unhide it. An approval list for whole device groups as in WSUS does not exist.
What about devices working from home?
The agent connects to fliix Ops over the internet; no VPN is needed for that. The maintenance window plan is stored on the device, and the updates come straight from Microsoft.
Does this strain our internet connection?
Every device downloads from Microsoft itself; fliix Ops caches nothing. So that not all devices download at once, the devices of a window start spread over the first 30 minutes.
Do servers get updates in the same window as clients?
You decide. A window applies to servers, clients or both. For servers, own scripts before the updates and after the restart are possible, for example to stop a service and start it again (Full).

Roll out updates without maintaining a server for it

In the demo you see a maintenance window from creation to the update history on the device.