Sanitized examples of systems/infrastructure operations work: documentation structure, incident runbooks, PowerShell health automation, escalation writing, and case studies.
All content is fictionalized or generalized. No customer data, credentials, internal host names, production IPs, or proprietary logs.
- Documentation discipline — structure that a regional desk or the next technician can use without a handoff call
- Method-first troubleshooting — isolate guest vs host vs DNS vs site before changing anything
- Operational automation — scheduled health checks that log exceptions instead of hoping someone notices
- Clear communication — escalation summaries and customer-facing updates written for action, not theater
| File | Purpose |
|---|---|
samples/it-glue-documentation-structure.md |
How I organize client documentation in an IT Glue–style system of record |
samples/sop-lpg-004-hyperv-vm-unavailable.md |
Incident runbook: Hyper-V guest unavailable (guest vs host vs storage vs DNS) |
samples/invoke-windows-healthcheck.ps1 |
Scheduled Windows / Hyper-V health check (disk, services, VM state, optional cluster, JSON log, optional email) |
| File | Purpose |
|---|---|
samples/tsm-restore-failure-case-study.md |
Restore failure that exposed backup platform misconfiguration |
samples/escalation-summary-template.md |
Escalation summary format for engineering / senior support handoff |
samples/customer-facing-technical-update.md |
Customer-facing update in plain technical language |
samples/post-remediation-runbook.md |
Runbook created after remediation to prevent repeat incidents |
samples/national-support-desk-standup-case-study.md |
Standing up a 12-person program support desk under a compliance deadline |
samples/hl7-interface-escalation-summary.md |
Intermittent clinical interface issue during hospital go-live |
samples/storage-and-ha-design-case-study.md |
Storage isolation and HA design for a multi-tier deployment |
samples/implementation-lifecycle-case-study.md |
End-to-end multi-site implementation ownership through go-live and turnover |
- IT Glue structure — where the runbook and host Configuration would live
- SOP-LPG-004 — human path after an alert
Invoke-WindowsHealthCheck.ps1— detector that can feed the ticket/RMM picture
The script uses built-in Windows / Hyper-V / FailoverClusters cmdlets only. It is a sample, not production tooling. Review before any use.
Sean Rector — systems / infrastructure engineer (Windows Server, Hyper-V failover clustering, Active Directory / Entra, documentation, L3 escalation). Hampton Roads, Virginia.
- GitHub: SeanRinVA
Samples are shared for evaluation of documentation quality and technical reasoning. Reuse patterns freely; do not treat fictional client details as real environments.