Unattended Updates¶
These guides cover the on-box mechanics of installing updates without a human at the keyboard. They complement the program-level guidance in Patch and Upgrade Management — rings, windows, rollback and communication still apply even when the install itself is automatic.
| Guide | Covers |
|---|---|
| Windows Server | sconfig, Group Policy, registry, WSUS, PowerShell, Azure Update Manager, Hotpatch, Cluster-Aware Updating, reboot control |
| Linux | Debian/Ubuntu, Fedora, RHEL family, Amazon Linux, SUSE, Arch, Alpine; reboots, livepatch, kured, fleet orchestration |
| FreeBSD | freebsd-update, pkgbase, pkg, periodic(8) reporting, boot environments, jails |
When to use unattended tooling vs a central scheduler: unattended tooling suits dev/test, homelab, and fleets where per-host autonomy is acceptable. For production fleets that need coordinated windows, reporting and reboots ordered across dependent services, drive patching from a central scheduler such as Azure Update Manager (see Hybrid Server Operations) — and don't run both on the same host.