SEC.01

The playbook

The run starts read-only: the recon probes decide what happens next. The steps that follow are adapted to the distribution and state found — a real machine is rarely clean.

1. 01reconis the PSWindowsUpdate module present?
2. 02actInstall PSWindowsUpdateverify
3. 03actInstall the updatesdestructiveverify

SEC.02

What it verifies

Each step ships its own check. The run only moves on when the check passes, so what the recipe reports as done is what is actually on the server.

1. 01verifyInstall PSWindowsUpdateVerified byGet-Command Get-WindowsUpdate -ErrorAction SilentlyContinue
2. 02verifyInstall the updatesVerified by(Get-WindowsUpdate | Measure-Object).Count

SEC.03

How a recipe runs in Servor

Servor is zero-knowledge: the platform cannot execute anything on its own. When you launch this recipe, a run reads the reconnaissance, plans the steps and asks for your approval. Each approved command is signed by your browser — with a key the server never sees — then relayed verbatim to the agent, which verifies the signature locally before executing.

SEC.04

More system recipes

1. 01TimezoneSets the server timezone.
2. 02CockpitCockpit web administration console, on :9090.
3. 03Zsh + Oh My ZshZsh with Oh My Zsh for the current user.
4. 04Synchronized clock (chrony)NTP synchronization via chrony.
5. 05User + sudoCreates a user with SSH key and sudo access. Destructive: system account.