Endpoint troubleshooting with evidence before action.
A Windows IT support engineering project for collecting endpoint evidence, isolating DNS/TCP/service faults, scoring incidents, documenting escalation, and validating troubleshooting workflows across a Windows environment.
Windows endpoint verification.
The evidence below shows a completed Windows Server 2025 verification session for the endpoint triage and regression-testing workflow.
Built around repeatable support work.
Collect first
System identity, disk pressure, DNS resolution, TCP reachability, Windows service state, and recent Event Log errors are captured before remediation.
Change safely
Network remediation is separated from diagnostics and supports PowerShell -WhatIf/ShouldProcess behavior.
Escalate with context
Runbooks and an escalation matrix emphasize timestamps, scope, exact failures, recent changes, actions attempted, and current workaround.
Failures are kept visible.
The project history keeps the bugs I ran into during development and Windows verification, together with the fixes and retests.
While expanding the collector, I found bugs in disk threshold logic, DNS exception handling, and service-state normalization. I added regression coverage, fixed each root cause, and retested the collector.
A PowerShell interpolation error surfaced during Windows verification. The failing expression was isolated, corrected, and retested successfully.
A Python evidence-template issue was identified during verification, corrected, and validated before the final documentation pass.