Before you start
Capture the current state, preserve recoverable data and record recent changes before remediation. Use production-impacting commands only within an approved maintenance or change window.
Establish scope
Record affected servers, users, applications, start time and recent patch, reboot, certificate, firewall or DNS changes. Determine whether one or many servers are affected.
Check services
List stopped services and compare with the server role. Inspect dependencies and Service Control Manager events before restarting repeatedly.
DNS and networking
Test name resolution, gateway reachability and required application ports. Check active adapter, routes and Windows Firewall.
Storage and performance
Check free space, disk health, CPU and memory. A full system volume can create secondary failures in services and updates.
Event logs
Filter System and Application logs around the incident time. Look for the earliest relevant failure and correlate repeated errors with the original symptom.
Validate recovery
Repeat the original user or application operation. Confirm stability after any required reboot and document root cause and prevention.
Baseline
Get-ComputerInfo | Select-Object WindowsProductName,WindowsVersion,OsBuildNumber,OsLastBootUpTimeServices
Get-Service | Sort-Object Status,DisplayName | Format-Table Status,Name,DisplayNameNetwork
Get-NetIPConfiguration
Get-NetRoute -AddressFamily IPv4Critical events
Get-WinEvent -FilterHashtable @{LogName='System';Level=1,2;StartTime=(Get-Date).AddHours(-4)} | Select-Object TimeCreated,Id,ProviderName,MessageTroubleshooting validation
- Confirm the original symptom is resolved.
- Verify dependent services and application health.
- Review logs or command output for secondary errors.
- Document the root cause and corrective action.
- Retain rollback evidence until the change is accepted.
Frequently Asked Questions
What should I check first?
Capture the current state, exact error, affected scope and recent changes before making changes. Then test the failing layer from the lowest dependency upward.
How do I validate the fix?
Repeat the original failing operation, check dependent services and confirm the issue remains resolved after any required restart or service recovery.
Can this troubleshooting be automated?
Automate read-only diagnostics first. Add remediation only after commands, permissions, logging and rollback behavior have been validated.