Monitoring Using PowerShell
summary
PowerShell scripts run on a central scheduler and actually monitor Servers, Websites, Active Directory, Exchange, DNS, DHCP, antivirus and WSUS — scripts are shared as CSV/HTML output and email alerts. Examples: a server C‑drive monitor runs daily; a server status page pings ~650 servers every 15 minutes and dynamically discovers new machines via AD; a website monitor runs every five minutes, logs response times and HTML errors. Scripts send alerts, keep long historical logs, detect missing AV or >20 patches, and have prevented real outages.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 0:44Why use PowerShell
- 1:46C Drive Monitor
- 2:44Server SeeDr
- 3:40Server Status Page
- 5:06Server Down
- 6:12Script Overview
- 8:27Monitoring Websites
- 16:43Exchange
- 18:04Mailbox Reporter
- 20:20Mailbox Snapshot
- 23:26Static DNS
- 24:46DHCP
- 26:27Antivirus
- 27:43Status Inquiries
- 29:34Patching
- 30:52Updates
- 31:18Patches
- 33:46Script
- 38:27Suggestions for Monitoring
- 42:42Problems with Monitoring
related talks
47mAutomating Active Directory Health Checks
39mPowerShell with SQL Statement Data Gathering
11mSysmon Monitoring Different Way
46mAn IT Operations Approach to Observability
43mWindows Monitoring 3.0 – Now more than ever!
36mInventory Your Server Environment and Detect Change at Scale
01h 30mSimple Network Management... PowerShell
47mEvent-Driven Automation with PowerShell: Listening for Change, Acting in Real Time