Windows Server: Quick Health Check

Category: Windows Server · Audience: Technicians · Est. time: 10–20 min

Summary

A fast, repeatable health pass for a Windows Server — disk, services, event logs, updates, and backups. Run it when a server is misbehaving or as a routine check.

⚠️ Servers are shared infrastructure. Avoid restarts/changes during business hours unless it's an outage. Confirm with BBN before rebooting a production server.

1. Uptime & pending reboot

• Task Manager → Performance → CPU shows Up time. Very long uptime can mean pending‑update instability; very short can mean an unexpected reboot.
• Check for a pending reboot (post‑update) — a server stuck needing a reboot causes odd failures.

2. Disk space

• This PC — is C: (and data volumes) healthy? Under ~10–15% free on C: causes problems. See *Windows Server: System Drive Full* to reclaim space.

3. Services

• services.msc — confirm the critical roles are Running and set to Automatic: e.g. Active Directory (NTDS), DNS Server, DHCP Server, file services, SQL Server, line‑of‑business app services, and the backup agent.
• A key service Stopped is often the root cause — start it and check the event log for why it stopped.

4. Event logs

• Event Viewer → Windows Logs → System and Application — filter for Errors/Critical in the relevant time window. Note recurring Event IDs (disk, service crashes, AD/DNS).

5. Updates

• Settings → Windows Update — is it patched? Are updates failing (a common cause of instability)? Schedule patching in a maintenance window.

6. Backups

• Confirm the last successful backup (Veeam/agent/BBN M365 as applicable) is recent and green. A server with failing backups is the top priority to fix.

7. Performance snapshot

• Task Manager / Resource Monitor — anything pinning CPU, memory, or disk? Note the process.

If something's wrong

• Address the specific finding (start a stopped service, clear disk, fix a failing update/backup).
• Escalate to BBN Support with the server name, the finding (service/event ID/disk), and whether it's affecting users now.

Prevention

• Monitor disk/services/backups proactively; patch in scheduled windows; keep at least 15% free on C:.