BuildsWindows patching
Meridian
Remediation console
A patching console that separates the plan from the apply step, and keeps drivers, definitions, and reboot windows legible.
SelectedCumulative update
In the plan. The reboot is pinned to the Thursday window.
What it solves
Patching fails when a list of updates is treated as permission to change a machine. Operators need to see what will happen, what is held, and who has to approve it.
Capabilities
- Scan results grouped into a remediation plan
- Separate gates for operating system, drivers, and definitions
- A dry run that changes nothing
- A named maintenance window and a hold list
Where it gets hard
- Updates do not share one reboot story
- Drivers need a different check than cumulative updates
- Dry-run and apply are different states and must look different
- An approval window has to survive contact with real machines
In the loop
An agent drafts the plan from the scan: what to include, what to hold, and which reboot window fits.
Nothing is applied until a person accepts the plan.
Studio product example. Not a client case study, and not a claim about results.