Learn
Technical guidance for the decisions that happen before and after the command.
Start with the system and the evidence, not a copied fix. These guides focus on failure boundaries, execution context, validation strategy, operational tradeoffs, and the reasoning that makes a technical action defensible in a real environment.
Questions Worth Asking
Start with the question the work needs to answer.
01What did we assess?Find inventory, scope, baseline, and assessment guidance that makes the result meaningful.Explore assessment guidance →02Which systems did we miss?Find audit, reconciliation, coverage-gap, and discovery guidance that exposes what fell outside the evidence.Explore coverage guidance →03What changed, and can we prove it?Find before-and-after validation, output, logging, and reporting patterns that leave reviewable evidence.Explore validation guidance →04What is the safest next action?Move from uncertainty to a focused check, script, or workflow when the evidence points to the next step.Open Tools →
Browse By Problem
Build durable operator judgment
01Windows OperationsWindows Server and workstation operations, patching, baselines, build evidence, servicing, recovery, configuration, and troubleshooting.4 guides02Identity & AccessActive Directory, authentication, authorization, service accounts, permissions, access paths, and identity-related operational troubleshooting.3 guides03Automation & ScriptingPowerShell and shell automation, repeatable operational workflows, scripting, task automation, and evidence-collection automation.3 guides04Linux, Cloud & ContainersLinux operations, cloud and hybrid infrastructure, containers, platform runtimes, virtualization, and operational self-hosting.9 guides05Networking & Remote AccessDNS, connectivity, routing, ports and protocols, VPN, remote access, file-transfer access paths, and network-facing operational troubleshooting.3 guides06Storage, Backup & Data MovementStorage and filesystems, backup and restore, recovery evidence, migrations, file transfer, transfer validation, and data-movement workflows.3 guides07Observability & EvidenceMonitoring, logging, telemetry, reporting, reconciliation, validation, maintenance evidence, handoff, and audit-oriented operational proof.0 guides
Learn Library
Browse technical guidance by problem domain
Windows Operations
Windows Server and workstation operations, patching, baselines, build evidence, servicing, recovery, configuration, and troubleshooting.
Comparing Windows Repair Paths: SFC, DISM, Restore, Rollback, and ReinstallCompare Windows repair paths before reaching for SFC, DISM, restore workflows, update rollback, or full rebuilds.Planning Windows Recovery and Repair Without Making the Outage WorseUse an incident-lead decision model that separates known evidence from assumptions, identifies the likely failure domain, preserves evidence, chooses the smallest discriminating...Windows Evidence-First Recovery Workflow Before Repair CommandsCapture 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.Windows Patch Compliance Without Blind SpotsSeparate discovery, evidence coverage, baseline assessment, and verified compliance so a Windows patch report shows both what is known and what could not be proved.
Identity & Access
Active Directory, authentication, authorization, service accounts, permissions, access paths, and identity-related operational troubleshooting.
Comparing Identity Validation Paths Across DNS, LDAP, Kerberos, and SMBDecide whether an identity or Windows access failure should be validated from DNS, LDAP, Kerberos, or SMB first.Identity Evidence-First Comparison Between Good and Broken PathsCompare a working identity or protocol path against the failing one before you change AD, DNS, trust, or service settings.Planning Identity and Windows Protocol Troubleshooting Without GuessingIsolate identity and Windows protocol failures by mapping the failing boundary before changing DNS, AD, SMB, or auth settings.
Automation & Scripting
PowerShell and shell automation, repeatable operational workflows, scripting, task automation, and evidence-collection automation.
Comparing Automation Fix Paths: Logic Repair, Context Repair, Retries, and ObservabilityChoose whether an automation failure needs logic repair, context repair, retries, or better observability before you change the workflow.Planning Admin Automation and Script Failure Response SystematicallyClassify the automation failure, compare the real interactive and unattended runtimes, improve observability, and make the smallest evidence-backed correction before rewriting code.Windows and PowerShell Execution Context Checks Before Script RewritesCompare the successful interactive context with the actual automation runtime before rewriting a script.
Linux, Cloud & Containers
Linux operations, cloud and hybrid infrastructure, containers, platform runtimes, virtualization, and operational self-hosting.
Cloud Pre-Change Validation for DNS, Gateways, Identity, and StorageCapture resource-specific cloud state and request-path evidence before changing DNS, gateways, identity, endpoints, or storage access.Comparing Cloud Validation Paths for DNS, Identity, Gateway, and Storage FailuresDecide whether a cloud failure should be validated from DNS, identity, gateway, or storage first.Comparing Container Validation Paths for Runtime, Registry, Network, and IngressDecide whether a container failure should be validated from runtime, registry, network, or ingress first.Comparing Healthy and Failing Container Service PathsCompare image, runtime, service, DNS, policy, and ingress state between a healthy and failing container path before redeploying or changing shared platform configuration.Comparing Healthy and Failing Linux Hosts Before Broad ChangesCompare concrete host, service, package, resolver, route, and authentication state between a healthy and failing Linux system before restarting or rewriting configuration broadly.Comparing Linux Validation Paths for SSH, Services, Packages, and Network ReachabilityChoose between SSH, service, package, and network validation branches before changing a Linux host.Planning Cloud App Publishing, Access, and Managed-Service Validation SafelyPlan cloud app publishing and access troubleshooting around path validation, service boundaries, safe changes, and rollback.Planning Container Runtime, Registry, and Service-Networking Failures SystematicallyIsolate container failures by separating image, runtime, service-networking, and ingress branches before changing the stack.Planning Linux Service and Access Validation Without Taking Risky ShortcutsSeparate Linux host access, service state, package-source, and network-path failures before making broad system changes.
Networking & Remote Access
DNS, connectivity, routing, ports and protocols, VPN, remote access, file-transfer access paths, and network-facing operational troubleshooting.
Comparing Healthy and Failing Network Edge PathsCompare WAN, switching, routing, VPN, and policy state between a healthy and failing path before renewing leases, reloading devices, or loosening access controls.Comparing Network Edge Validation Paths for DHCP, VPN, Switching, and Policy FailuresChoose between WAN handoff, switching, VPN, and policy validation branches before changing the network edge.Planning Network Edge, Access, VPN, and Switching Failures Without GuessingSeparate provider handoff, switching, VPN, and edge-policy failures before making broad network changes.
Storage, Backup & Data Movement
Storage and filesystems, backup and restore, recovery evidence, migrations, file transfer, transfer validation, and data-movement workflows.
Comparing Robocopy, PowerShell, rsync, and Storage-Native Replication for File MigrationsUse this when you need to choose the right file-migration path instead of defaulting blindly to Robocopy, PowerShell, rsync, or storage replication.Planning Data Migrations and File Moves Without Creating Validation GapsPlan file-share and data migrations around scope, tool choice, validation, rollback, and evidence before running the copy path.Validating File Migrations Before Cutover and Proving the Target Is AuthoritativeUse this when you need a validation model that proves a migrated target is ready before users, apps, or cutover steps depend on it.
Observability & Evidence
Monitoring, logging, telemetry, reporting, reconciliation, validation, maintenance evidence, handoff, and audit-oriented operational proof.
New technical guidance for this path is still being developed.