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.
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
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
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
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
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
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?
Can I test updates before all devices receive them?
Can I hold back a single update?
What about devices working from home?
Does this strain our internet connection?
Do servers get updates in the same window as clients?
More tasks
What else fliix Ops takes care of
Each page answers one task from daily Windows work, with the workflow, the limits and the licence.
All solutions →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.