Microsoft SCOM 2025 UR1

What’s New and Why It Matters

System Center Operations Manager (SCOM) continues to evolve to meet modern infrastructure needs. With SCOM 2025, released in November 2024, Microsoft introduced major updates for security, compatibility, and platform support.

Now, Update Rollup 1 (UR1) builds on that foundation with critical fixes and enhancements.

What Is SCOM 2025?

SCOM 2025 modernized monitoring by:

• Expanding support for newer infrastructure.
• Dropping legacy OS support (older Windows Server versions).
• Introducing a stronger security and compatibility baseline.

For more background, check out https://kevinholman.com or https://blog.topqore.com.

What’s New in UR1?

According to https://learn.microsoft.com and https://support.microsoft.com, UR1 delivers:

Why This Matters for SCOM Users/Admins

Better security: TLS 1.3 + updated OpenSSL + newer OS/SQL support hardens your environment.

Future-proofing: Compatibility with SQL Server 2025 and latest Linux distros keeps SCOM relevant for hybrid/cloud setups.

Broader compatibility: Easier monitoring for modern Linux/Unix environments.

Simplified upgrades: Cumulative fixes and updated support matrix reduce upgrade friction.

Known Issues Fixed in UR1

UR1 addresses several long-standing issues (per https://support.microsoft.com):

• Console content blocked — Fixed issue caused by legacy IE control.
• Monitor authoring failure — Authoring new monitors in the console now works.
• “Reset State” task issue — Fixed for monitors linked to virtual Windows computer objects.
• Web Console dashboard columns — Columns in Active Alerts Dashboard can now be resized.
• Topology widget icons — Icons are now draggable.
• Contextual widgets malfunctioning — Resolved widget behavior issues.
• S2D workflow failure / WMI memory leak — Fixed RPC_S_UNKNOWN_AUTHN_SERVICE error and WMI leak.
• Web Console image blocking (CSP) — Images no longer blocked by Content Security Policy.
• Encoding compliance (GB18030-2022) — Fixed character encoding issues for internationalization.

Additionally, it includes all prior update rollups and hotfixes, and adds Linux/Unix agent fixes for new distro support.

Before UR1, Users Experienced

• Failed monitor authoring.
• Reset-state tasks not working for VMs.
• Web Console usability issues (columns, widgets, CSP image blocking).
• S2D monitoring failures and memory leaks.
• Encoding issues for non-Latin environments.

✅ Upgrade Checklist for UR1

Before deploying UR1, follow these steps:

1. Review prerequisites
   • Ensure your environment meets https://learn.microsoft.com/system-center/scom/plan-requirements.
   • Verify SQL Server 2025 readiness if planning to upgrade DB components.
2. Backup your environment
   • Back up OpsDB, Data Warehouse, and Reporting databases.
   • Export management packs and custom configurations.
3. Download UR1 packages
   • Get the latest update rollup from https://www.catalog.update.microsoft.com.
4. Apply updates in sequence
   • Management servers → Gateways → Web Console → Reporting → Agents.
5. Update Linux/Unix agents
   • Deploy updated agents for new distro support (Debian 13, RHEL 10, etc.).
6. Verify TLS 1.3 configuration
   • Confirm TLS settings align with your security policies.
7. Test in staging
   • Validate dashboards, widgets, and workflows before production rollout.
8. Monitor post-upgrade health
   • Check for alerts, performance counters, and agent connectivity.