PowerShell.
Every Windows Server I touch gets scripted before it gets documented. Repeatable beats clever.
Primary automation language for Windows Server, RDS and Hyper-V estates. Nothing clever, just scripts I can re-run.
I default to declarative, idempotent scripts: re-running one should be a no-op, not a new incident. This has paid off most on RDS session-host provisioning and on the Tally Prime ERP migration documented in ~/work/rds-migration-tailscale-to-twingate. Two places where a second run used to mean a second ticket.
The same discipline runs the 14-day rolling backup cleanup on a Task Scheduler. A retention script keeps the newest 14 Tally Prime dumps and removes the rest, so re-running the job is a logged no-op rather than a surprise. See ~/work/unified-it-infrastructure-and-digital-transformation-at-maryana-group.
used_in: ~/work/rds-migration-tailscale-to-twingate · ~/work/unified-it-infrastructure-and-digital-transformation-at-maryana-group