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.
- 01reconWindows edition and build (ProductType 1 = workstation, 2 = DC, 3 = server), RAM
- 02reconalready a domain member or DC (DomainRole 4/5)? → do not re-promote; is the machine name final?
- 03reconis the AD DS role already installed?
- 04reconstatic IP (Dhcp Disabled, required for a DC) and DNS configured
- 05actInstall the AD DS roledestructiveverify
- 06actGenerate the DSRM passwordverify
- 07actTest the forest prerequisitesverify
- 08actPromote to DC (new forest)destructiveverify
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.
- 01verifyInstall the AD DS roleVerified by
(Get-WindowsFeature AD-Domain-Services).InstallState - 02verifyGenerate the DSRM passwordVerified by
Test-Path "$env:ProgramData\Servor\secrets\adds-dsrm.txt" - 03verifyTest the forest prerequisitesVerified by
Import-Module ADDSDeployment; $s = ConvertTo-SecureString (Get-Content "$env:ProgramData\Servor\secrets\adds-dsrm.txt" -Raw) -AsPlainText -Force; (Test-ADDSForestInstallation -DomainName ${domain} -InstallDns -SafeModeAdministratorPassword $s -NoRebootOnCompletion -Force).Status - 04verifyPromote to DC (new forest)Verified by
(Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Services\NTDS\Parameters' -ErrorAction SilentlyContinue).'DSA Database file'
SEC.03
Guardrails
Non-negotiable instructions the run must respect, whatever it finds on the server.
Critical operation, irreversible without restoring the snapshot. The DSRM password stays in the secrets file, never displayed. Only on a dedicated Windows Server with a static IP, never on an application server. Do not reboot: say the reboot is mandatory to finish and that the agent will come back afterwards.
SEC.04
Variables
What you choose before launching — the recipe fills in the rest.
| Name | Meaning |
|---|---|
| ${domain} | Domain name |
SEC.05
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.
search by intent — type “firewall”, get ufw
- 01Read-only reconnaissance before any change
- 02Every command signed by your browser, approved by you
- 03Each step verified before the run moves on, every run kept in the history
SEC.06
Deploy on Servor button
Maintain Active Directory (domain controller) or a project that needs it? Put this button in your README or on your site: one click and your users install it on their own server.
SEC.07
More system recipes
- 01TimezoneSets the server timezone.
- 02CockpitCockpit web administration console, local-only (SSH tunnel) by default, on :9090.
- 03Zsh + Oh My ZshZsh with Oh My Zsh for the current user.
- 04Synchronized clock (chrony)NTP synchronization via chrony.
- 05User + sudoCreates a user with SSH key and sudo access. Destructive: system account.
Verified recipe
Run this recipe on your server
Connect a server, launch the recipe, and approve each step as Servor executes and verifies it. Free plan, no card required.