Best Practices for Monitoring with the 2000/2003 Terminal Services Management Pack

5 Essential Guides to the ⁄₂₀₀₃ Terminal Services Management Pack

Below are five concise guide outlines (one per essential guide) describing what each guide covers, key steps or sections, and the target reader.

Target: Administrators new to SCOM/OPS Mgr and Terminal Services.
Sections: prerequisites (OS, SCOM version), download sources, installing prerequisites (agents, .NET), importing the MP into SCOM, configuring discovery rules, verifying discoveries and initial alerts.
Key steps: confirm service accounts and permissions → import MP → configure run-as accounts → enable discovery → check event/health views.
Outcome: working MP with discovered Terminal Services servers and baseline alerts.

Target: Admins who need tailored monitoring and thresholds.
Sections: enabling/disabling rules and monitors, tuning thresholds, creating overrides, custom dashboards and views, alert routing and subscriptions.
Key steps: review default monitors → create overrides scoped to groups → suppress noisy rules → map alerts to tickets/teams.
Outcome: reduced noise, prioritized alerts, dashboards showing key Terminal Services KPIs.

Target: Capacity planners and performance engineers.
Sections: key counters (sessions, CPU, memory, load, licensing), collecting baseline metrics, trend reports, forecasting capacity needs, automating reports.
Key steps: enable performance collection for critical counters → define collection intervals → build charts and reports → analyze peaks and plan scaling.
Outcome: actionable capacity plan and performance baselines to prevent resource exhaustion.

Target: Troubleshooters handling session, licensing, and service issues.
Sections: common problems (session disconnects, excessive sessions, licensing failures), diagnostic workflows, log locations and useful Event IDs, remediation steps.
Key steps: reproduce issue → check MP alerts and related events → collect logs and perf counters → apply fixes (service restart, quota changes, license server checks) → verify resolution.
Outcome: faster root-cause identification and standard remediation procedures.

Target: Teams migrating from older MPs or securing Terminal Services.
Sections: compatibility considerations, removing deprecated MPs, migrating overrides, securing management communications, least-privilege run-as accounts, patching guidance.
Key steps: export overrides and run-as profiles → test MP removal in lab → import updated MP and apply overrides → validate security settings and encryption.
Outcome: safe migration path with preserved tuning and improved security posture.

If you want, I can expand any single guide into a full step-by-step document (example: full install checklist or troubleshooting playbook).