Quick facts

Release: SCOM 2025 Update Rollup 1 (UR1)

Headline additions: TLS 1.3 support, SQL Server 2025 compatibility, Windows Server 2025 role support, expanded Linux/Unix agent coverage

New agent support: Oracle Linux 10, Rocky Linux 10, Alma Linux 10, RHEL 10, Debian 13

Also fixes: broken monitor authoring, VM Reset State, several Web Console UI bugs, CSP image blocking, Storage Spaces Direct (S2D) failures, a WMI memory leak, GB18030-2022 encoding compliance

Is SCOM 2025 UR1 required, or optional? Microsoft ships UR1 as a rollup rather than a mandatory patch, but it resolves enough day-to-day friction - broken monitor authoring, Web Console bugs, a memory leak - that most teams running SCOM 2025 should plan to apply it rather than skip it

If the previous post in this series settled the "is SCOM dead?" question, this one gives you the proof. UR1 is the clearest evidence yet that on-premises SCOM 2025 is a platform worth redeploying on, not just the least-bad option while SCOM MI shuts down.

SCOM 2025 shipped as a major platform release, dropping legacy OS support and resetting the security and compatibility baseline. UR1 is the first significant rollup on top of that foundation, and it's less "bug fixes" and more "the release that makes SCOM 2025 production-ready for teams who were waiting to see it mature."

SCOM 2025 UR1 Feature Additions: What Changed

1. TLS 1.3 support - closes a compliance gap for regulated environments.
2. SQL Server 2025 support - keeps the whole database stack current.
3. Expanded Linux/Unix agent support - adds Oracle Linux 10, Rocky 10, AlmaLinux 10, RHEL 10, Debian 13.
4. Windows Server 2025 & modern browser support - server roles and Web Console both updated.

The SCOM 2025 UR1 Fixes That Actually Matter Day to Day

Feature tables are one thing; what actually annoyed SCOM admins is another. UR1 quietly resolves a handful of issues that had been genuine friction points:

• Monitor authoring was broken. Authoring new monitors directly in the console now works again - a basic capability that had been quietly failing.
• Reset State didn't work on virtual machine objects. Fixed - useful for anyone doing routine health-state resets on VM-backed computer objects.
• The Web Console was rough. Alert dashboard columns can now be resized, topology widget icons are draggable, and contextual widgets no longer misbehave. Small things individually, but they add up to a console that finally feels current rather than dated.
• Content Security Policy was blocking images in the Web Console. Fixed - a silent, confusing issue for anyone relying on the web experience day to day.
• Storage Spaces Direct (S2D) workflow failures and a WMI memory leak. Both resolved, which matters if any part of your estate runs on S2D-backed infrastructure.
• Character encoding compliance (GB18030-2022). Fixed for teams operating in non-Latin-character environments.

None of these are individually dramatic. Together, they're the difference between "SCOM 2025 technically works" and "SCOM 2025 is something I'd trust to run my production monitoring."

Why SCOM 2025 UR1 Matters for the Redeploy Decision

Go back to the decision from Part 1: teams choosing to redeploy on-prem instead of chasing Azure Monitor were making a bet that SCOM 2025 would keep maturing fast enough to be worth it. UR1 is early evidence that bet is paying off:

• Security posture is current (TLS 1.3), which removes a common blocker in regulated or security-conscious environments.
• The data platform is future-proofed - SQL Server 2025 support means you're not redeploying onto a database version that's already aging out.
• Hybrid and Linux-heavy estates get meaningfully better coverage, which matters if your redeploy plan includes anything beyond pure Windows Server
• .The console itself is fixed, which matters because the console is what your team will actually live in every day post-migration.

Before You Deploy SCOM 2025 UR1: A Pre-Flight Checklist

A quick practical checklist, regardless of which side of the SCOM MI decision you're on:

1. Confirm your environment against Microsoft's current SCOM 2025 requirements, and check SQL Server 2025 readiness if you're planning that upgrade path too.
2. Back up the OpsDB, Data Warehouse, and Reporting databases, and export your management packs and overrides before touching anything.
3. Pull UR1 from the Microsoft Update Catalog and apply it in order: management servers → gateways → Web Console → reporting → agents.
4. Update Linux/Unix agents last, once the new distro support is confirmed in your environment.
5. Test in staging before touching production — dashboards, widgets, and workflows specifically, since several of the fixes above touch exactly those areas.

What SCOM 2025 UR1 Doesn't Fix

UR1 makes the platform itself solid. It doesn't touch the thing that actually makes migrations painful: years of accumulated overrides, undocumented tuning, and management-pack drift that nobody fully understands anymore. That's a people-and-process problem, not a rollup — and before we get into how to fix it, it's worth putting a number on what it actually costs to leave it unfixed.

Next in this series: Migration Planning - The infrastructure is the easy part. Sorting out the overrides to bring with you is the real challenge. Why Your Overrides Are the Real Risk.