Cloud Pre-Change Validation for DNS, Gateways, Identity, and Storage
Capture resource-specific cloud state and request-path evidence before changing DNS, gateways, identity, endpoints, or storage access.
Search
Search the rebuilt public library in one place. Results stay separated as Learn, Labs, and Tools so you can choose between understanding the system, practicing the workflow, or running a focused operator asset.
Capture resource-specific cloud state and request-path evidence before changing DNS, gateways, identity, endpoints, or storage access.
Create the local PowerShell helper file that every Ops Stack reporting-compatible script can share. This guide walks through the folder structure, the helper contract, the commented PowerShell implementation, a sample validation run, and the artifacts the helper creates so a new reader can build it from scratch and prove it works.
Concrete PowerShell reporting pattern for turning host-check results into an HTML operations summary with a status rollup, per-host table, failure section, saved local artifacts, and optional email delivery.
A ready-to-fill restore-test record with scope, isolated restore evidence, application/data validation, measured RPO/RTO, failures, assumptions, cleanup, owner signoff, and a management/change summary.
Capture the exact symptom, Windows context, relevant logs, rollback signal, and validation criteria before SFC, DISM, reboots, uninstalls, Safe Mode, or other repair commands change the evidence you still need.
A restore-drill evidence template for proving backups are usable, measuring recovery time, and turning failed assumptions into repair tasks before an outage.
Use a disposable ZFS dataset to prove snapshot, replication, retention, destructive-change recovery, and rollback between two TrueNAS systems.
Combine configuration discovery with runtime authentication evidence, SPN/Kerberos review, owner approval, an observation window, and explicit DISABLE / HOLD / ROLLBACK criteria before retiring a domain service account.
A Windows Server-specific observe, compare, repair, validate workflow for one server that fails a monthly update while a peer succeeds, with proxy, update-source, servicing, applicability, CBS/DISM, and before/after evidence.
A patch readiness and repair evidence pack for reboot state, servicing health, update logs, and approved repair actions.
The primary production file-migration workflow: plan, dry-run, pre-seed, freeze writes, final delta, validate data/metadata/access, and make an explicit GO / STOP / ROLLBACK decision before the destination becomes authoritative.
PowerShell scanner that checks fixed local drives on Windows servers for root ACL entries where Authenticated Users have broad access. Produces console and CSV evidence so admins can review exposure before any ACL changes.
Operator checklist for launching an internal IIS-hosted site with evidence capture for IIS role presence, site folder layout, bindings, app pool identity, DNS readiness, browser validation, and rollback notes.
A compact operator note format for capturing symptoms, checks, decisions, and follow-up while the issue is fresh.
Use the Ops Reporting Foundation helper to turn PowerShell checks into consistent HTML, CSV, JSON, and log artifacts. Start here after creating the helper file, then plug health checks, patch checks, certificate scans, AD hygiene checks, and other collectors into the same reporting pattern.
A simple monitoring starter for internal services, homelab systems, and small-office status checks.
Two-phase review checklist for identifying inactive AD user accounts, validating inactivity evidence, applying exclusions, capturing approval, and preparing rollback details before any disable action.
Preflight checklist for onboarding Windows servers to Azure Arc. Confirms supported OS state, outbound connectivity, proxy/TLS behavior, local admin rights, target Azure placement, tagging, pilot scope, and rollback notes before any agent install.