Following the trend away from SCOM’s old UNIX/Linux agents, Holman points to:
: Currently, the SCOM console may not reflect the UR1 version in the "About" section; this UI bug is expected to be resolved in UR2. For ongoing updates and detailed step-by-step guides, refer directly to Kevin Holman's Blog . AI can make mistakes, so double-check responses Copy Creating a public link... You can now share this thread with others Good response Bad response 6 sites Kevin Holman's Blog – SCOM and anything else I find ... Mar 6, 2026 — kevin holman scom 2025
: If Harlan continues in his role, fans can expect more of the high-quality commentary and analysis they've grown to appreciate. Following the trend away from SCOM’s old UNIX/Linux
Kevin Holman’s Guide to SCOM 2025: Deployment, UR1, and Best Practices You can now share this thread with others
: As with any long-tenured figure in media, there's always speculation about retirement or transitioning into new roles. Harlan's age and the ever-evolving landscape of sports broadcasting could potentially lead to changes in his current role.
: Regardless of Harlan's future, TNT and other networks are always on the lookout for emerging talent to bring fresh perspectives and voices to sports broadcasting.
| Current State (as of 2024) | What “2025” could mean | |----------------------------|------------------------| | System Center Operations Manager 2022 (with cumulative updates up to CU12). | Speculative roadmap: A major version bump (e.g., SCOM 2025 ) that aligns with the “Windows Server 2025” and “Azure Arc 2025” product cycles. | | Focus on hybrid & cloud‑native monitoring (Azure Monitor, Log Analytics, Azure Arc). | Potential new features: • Deep integration with Azure Monitor Metrics Explorer. • Native support for Azure Arc‑enabled servers and Kubernetes without the need for the Operations Management Suite (OMS) gateway. • AI‑driven anomaly detection powered by Microsoft Copilot for IT. | | On‑premises heavy‑lift: Requires Management Packs, agents, and a dedicated data warehouse. | Simplified deployment: • “Zero‑touch” agent deployment via Intune/Endpoint Manager. • Cloud‑first data store (Azure Data Explorer) with optional on‑prem replication. • Declarative monitoring definition using Infrastructure as Code (IaC) (ARM/Bicep + PowerShell DSC). | | Management Packs (MPs) are still the primary extensibility mechanism. | Extensibility shift: • MP‑to‑ OPM (Operations Pack Modules) conversion tool. • Support for OpenTelemetry exporters and custom Prometheus metrics. • Marketplace of community‑verified monitoring modules (similar to Azure Marketplace). | | Performance & scalability improvements via newer SQL Server/Oracle back‑ends. | Scalability leaps: • Built‑in horizontal scaling using Azure Service Fabric clusters. • Integrated Time‑Series Database (TSDB) for high‑frequency metrics (sub‑second granularity). |