1.

User Login Failure (AD / SSO / IAM)

Symptoms: Wrong password, account locked, SSO redirect loop.
Troubleshooting Steps:
1. Check authentication logs for failed attempts.
2. Verify account status (locked/disabled/password expired).
3. Validate SSO/IdP connectivity & certificate validity.
4. Test login via alternative auth endpoint (e.g., LDAP bind).
5. Sync AD replication status.
6. Reset password or unlock account.

2. Application 500 Errors / Service Unresponsive

Symptoms: HTTP 500, server errors, sudden crash.
Troubleshooting Steps:
1. Capture app logs, error traces, recent exceptions.
2. Check CPU/memory usage, GC events, disk I/O.
3. Validate DB/service dependencies.
4. Restart application service (if safe).
5. Roll back recent deployment or config change.

3. Slow Application Performance

Symptoms: High response time, slowness reports.
Troubleshooting Steps:
1. Check APM metrics: latency, DB calls, external API delays.
2. Review server resource utilization.
3. Validate network path, packet drops, DNS resolution.
4. Clear app/service caches if applicable.
5. Scale up/scale out resources temporarily.

4. Network Slowness or Latency Spikes

Symptoms: Ping delays, slow file access, intermittent lag.
Troubleshooting Steps:
1. Run traceroute/pathping.
2. Check switch/router interface errors or congestion.
3. Validate bandwidth usage (top talkers).
 4. Check for spanning tree events or route flaps.
5. Switch user to alternate network/VLAN.

5. VPN Connection Failure

Symptoms: Cannot connect to VPN, disconnects, auth error.
Troubleshooting Steps:
1. Validate VPN gateway health & logs.
2. Check user cert validity or MFA token.
3. Confirm IP pool availability.
4. Reset tunnel; reboot VPN client.
5. Check firewall rules for blocked ports.

6. Email Delivery Issues (O365 / Exchange)

Symptoms: Email not received, bounced, stuck in queue.
Troubleshooting Steps:
1. Check message trace for routing or spam filtering.
2. Validate mailbox quota & rules.
3. Inspect connector and MX configuration.
4. Check for blacklisting.
5. Restart transport service if needed.

7. File Share Access Failure

Symptoms: Access denied, share unreachable.
Troubleshooting Steps:
1. Validate permissions (ACL, group membership).
2. Check SMB service availability.
3. Confirm network connectivity and DNS resolution.
4. Review storage backend health.
5. Reset or reassign NTFS permissions.

8. Printer Not Working / Offline

Symptoms: Print job stuck, printer offline.
Troubleshooting Steps:
1. Clear stuck jobs on print server.
 2. Restart spooler service.
3. Verify printer network connectivity.
4. Reinstall printer driver.
5. Check for paper jams or low toner.

9. High CPU / Memory on Server

Symptoms: Slow response, server unresponsive.
Troubleshooting Steps:
1. Identify top processes consuming resources.
2. Check memory leaks or runaway threads.
3. Validate scheduled tasks or cron spikes.
4. Restart affected services if safe.
5. Scale resources or redistribute load.

10. Disk Space Full / Low Disk Alert

Symptoms: Cannot write logs, services crash.
Troubleshooting Steps:
1. Identify large files / log growth.
2. Rotate logs, clear temp directories.
3. Expand disk volume or add storage.
4. Move large data to secondary storage.
5. Validate snapshot/backup cleanup jobs.

11. Database Connection Timeout

Symptoms: App unable to connect to DB.
Troubleshooting Steps:
1. Check DB listener status & port availability.
2. Validate credentials & DB user lock status.
3. Review connection pool exhaustion.
4. Check network path between app & DB.
5. Restart DB listener if needed.
12. Database Performance Issue (Slow Query)
Symptoms: High latency queries, DB locking.
Troubleshooting Steps:
1. Identify slow queries and locking/blocking.
2. Check CPU, buffer cache, I/O wait.
3. Review recent schema changes.
4. Rebuild indexes (if safe).
5. Tune query or increase compute.

13. DNS Resolution Failure

Symptoms: Site not reachable, “DNS not found.”
Troubleshooting Steps:
1. Validate DNS server health.
2. Flush DNS cache on client/server.
3. Check zone file entries or missing A/CNAME records.
4. Inspect DNS replication issues.
5. Fix TTL or propagation delays.

14. Storage Latency / SAN Issues

Symptoms: Slow disk I/O, VM sluggishness.
Troubleshooting Steps:
1. Check SAN fabric health & port errors.
2. Validate LUN mappings and multipathing.
3. Inspect RAID rebuilds or disk failures.
4. Check latency in storage controller.
5. Move workload to alternate datastore.

15. Backup Job Failures

Symptoms: Backup missed/skipped/errored.
Troubleshooting Steps:
1. Review backup job logs.
2. Validate storage target availability.
3. Check agent health on client system.
4. Verify credentials and backup policy.
 5. Rerun job or reseed backup.

16. Patch Deployment Failure

Symptoms: Patch not installed, rollback triggered.
Troubleshooting Steps:
1. Check deployment logs.
2. Validate WSUS/SCCM connection or repo sync.
3. Restart patch agent service.
4. Manually install patch & capture logs.
5. Reassign device to correct patch group.

17. Endpoint Device Not Booting / BSOD

Symptoms: Device stuck, kernel panic.
Troubleshooting Steps:
1. Boot in safe mode.
2. Check recent drivers or patch updates.
3. Run disk check for corruption.
4. Restore from last known good config.
5. Reimage device if needed.

18. Security Alert: Suspicious Activity

Symptoms: Malware, abnormal login patterns.
Troubleshooting Steps:
1. Isolate affected device from network.
2. Run endpoint security scan.
3. Validate login attempts against AD logs.
4. Reset credentials for user/device.
5. Escalate to SOC if high-risk.

19. Cloud VM / Instance Unresponsive

Symptoms: No SSH/RDP, high CPU, stuck state.
Troubleshooting Steps:
1. Check cloud provider console for health.
2. Review CPU/network spikes.
 3. Restart instance or reset network interface.
4. Check storage IOPS throttling.
5. Capture diagnostics (serial logs).

20. Configuration Drift / Compliance Failure

Symptoms: Server config not matching baseline.
Troubleshooting Steps:
1. Compare drift report against golden policy.
2. Validate config mgmt agent (Chef/Puppet/Ansible).
3. Reapply correct configuration.
4. Audit last changes (user, deployment).
5. Schedule compliance scan.