Patch management

Patch management for Windows clients and servers

fliix Ops installs Windows updates, drivers, BIOS and program updates in maintenance windows and shows per device what was installed, what is missing and why. Everything runs in the browser, hosted in Germany.

Operating system, drivers, BIOS and programs Staggered after Patch Tuesday Proof in the monthly report per tenant

The short answer

How do I patch many Windows devices reliably?

With fixed maintenance windows instead of one-off actions. In fliix Ops you define per device group when patching happens, which steps run and how devices restart. The agent on the device works through the steps one after another and reports the result of each step.

A window covers more than Windows Update: drivers from HP, Dell and Lenovo, apps from the Microsoft Store, programs through WinGet and Chocolatey and, if you want, the BIOS. Afterwards a security check examines the device, and the findings show the new state.

Where a window is not enough, you patch right away: on one device or as a bulk action on all devices with pending updates.

Workflow

How a maintenance window runs

  1. 1

    Prepare

    If you want, the device downloads and installs updates before the window, without a restart. Switched-off devices on a network cable can be woken for the window.

  2. 2

    Install

    In the window the enabled steps run one after another: own script, Windows updates, drivers, Store apps, WinGet, Chocolatey, BIOS.

  3. 3

    Restart

    Restart 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. On servers an own script then starts a service again, for example.

  4. 4

    Check and prove

    The security check runs after the restart. The runs show every step with its result per device, the monthly report the update history.

What is included

What a maintenance window can patch

Windows quality and security updates, for clients and servers.
New Windows versions for clients as a separate step: pilot devices first, with the Windows compatibility check and a way back to the previous version for as long as Windows keeps it (usually 10 days).
Drivers from HP, Dell and Lenovo from the vendor catalog and recommended drivers from Windows Update, with a pilot phase and rollback.
BIOS updates for clients from HP, Dell and Lenovo, off by default.
Programs through WinGet (with exceptions and locks per program) and Chocolatey.
Apps from the Microsoft Store. Open apps are not closed for it.
Schedule after Patch Tuesday (0 to 27 days later), weekly, or on the nth weekday of the month, in a fixed time zone or device time.
Assignment per device, tag, group or as the tenant default. Windows can be paused, for example for the year-end closing.
If the scheduled maintenance fails on a device twice in a row, a finding is raised (Full).

Limits

What you should know beforehand

  • fliix Ops manages Windows 10, Windows 11 and Windows Server 2016 and later (64-bit). It does not patch macOS, Linux or mobile devices.
  • Windows updates are not approved individually. Everything pending that is not hidden on the device is installed. Testing happens through the stagger in time.
  • Programs from other vendors are updated only when the WinGet catalog or the fliix Ops Chocolatey repository knows them.
  • Devices download straight from Microsoft and from the vendor. There is no cache in your own network.
  • New Windows versions and BIOS updates are available in the window for clients only.

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 are part of Full.

FAQ

Frequently asked questions about patch management

What happens when a device is switched off during the maintenance window?
fliix Ops can wake switched-off devices on a network cable before the window through another device in the same network; this does not work over Wi-Fi. If a client stays off anyway, by default it catches up on the run once it is back online within 7 days. Servers by default take part again in the next window.
Are users restarted in the middle of their work?
You decide per window. The restart runs if needed, always or never. On clients with a signed-in user the agent asks: without an answer the device restarts after 60 seconds by default or, if you choose so, waits until the deadline (1 to 24 hours). Windows outside working hours and waking the devices avoid the question altogether.
Can I patch programs such as browsers or PDF readers as well?
Yes, with the Full licence through WinGet and Chocolatey. The window updates every program WinGet knows, including ones installed by hand, and all packages installed through Chocolatey. For WinGet you exclude or lock individual programs through the software rules.
How do I prove that patching happened?
The update history per device shows every installation with time, result and error code and is kept for 25 months. The monthly report per tenant contains it as PDF and Excel.
Does this work for servers too?
Yes, for Windows Server 2016 and later. On Server 2016 only the updates from Windows Update are installed, not those for other Microsoft products. Servers get their own windows, if you want with an own script before the updates and after the restart. The window does not install new Windows versions or BIOS updates on servers.
Do I need a server of my own for this?
No. fliix Ops is a cloud console hosted in Germany. Only the agent runs on the devices. If you run a WSUS today, you can retire it.

Patch by plan instead of by reminder

In the demo you see a maintenance window, the runs per device and the monthly report.