If your System Center Operations Manager Data Warehouse has been quietly growing past every retention setting you configured, Update Rollup 4 for SCOM 2022 is the patch you’ve been waiting for. UR4 (KB5120166, build 10.22.12369.0) fixes a Standard Dataset grooming bug that let aged data survive far longer than it should have — and it ships alongside a security tightening of the Web Console PowerShell widget, support for the newest OpenSSL 3 Linux distributions, and a handful of console and notification fixes that admins have been reporting since UR3.
Here’s everything in the rollup, what it actually means in a production environment, and how to install it cleanly.
Standard Dataset grooming now honours retention
What was broken: In the Data Warehouse, Standard Dataset grooming was not correctly removing data older than the configured retention period. Rows that should have been aged out stayed put.
Why it matters: This is the kind of bug you don’t notice until you do. Retention settings look correct in the console, the grooming workflows report success, and yet the OperationsManagerDW database keeps climbing — consuming storage, slowing reporting queries, and stretching maintenance windows month after month. Teams running large agent estates or long retention profiles have been absorbing the cost of this without an obvious cause to point at.
After UR4: Retention settings are honoured, aged data is removed as configured, and Data Warehouse maintenance behaves the way the documentation always said it would. If your DW has been growing unexplainably, patch first — then look at whether a controlled grooming catch-up is needed once UR4 is in place.
PowerShell widget access is now Administrators-only
The PowerShell widget in Web Console dashboards was accessible to all users, not just administrators. Non-admin users could view — and in practice execute — PowerShell through the dashboard interface. That’s a meaningful access-control gap in any environment where the Web Console is broadly published to application owners, service desk staff, or read-only stakeholders.
UR4 restricts editing of PowerShell widgets to Administrators only. If you’ve published Web Console dashboards widely and hesitated over exactly who could reach that widget, this fix closes the question.
Web Console and dashboard fixes
Several of the UR4 fixes address regressions and long-standing annoyances that admins hit daily:
- State View returning HTTP 500 in the Web Console. Monitoring classes with no containment children caused the Web Console State View to fail outright. In practice this is why views such as Windows Service State and Process State stopped loading in the Web Console after 2022 UR3. UR4 restores them.
- Dashboard View not loading State View when the Physical Memory column is added. Adding that one column broke the view. Fixed.
- SCOM group name inconsistency. Dynamically created groups appeared under different names in the User Role Wizard than they did elsewhere in the console — a genuine hazard when you’re scoping user roles and can’t be certain the group you’re picking is the group you mean. Names are now consistent across the console.
Notifications, discovery and management packs
- Teams notifications containing double quotes were not delivered. If your alert templates included quoted text — and many do, since alert descriptions frequently contain them — those notifications silently failed to arrive. Fixed in UR4.
- Agent discovery wizard failure. Discovery could fail with “The Operations Manager Server could not find directory \\SERVERNAME\C$\WINDOWS\. Agent will not be installed on computer SERVERNAME.domain.com. Please verify the required share exists.” — even where the share was present and permissions were correct. Resolved.
- Management packs not updated or imported after install. A frustrating post-patch state where MPs simply didn’t land. UR4 fixes the import behaviour.
Chinese language (GB character) fixes
UR4 corrects a cluster of issues with GB Amendment characters — the Chinese national standard character set — across the product:
- Reports could not display GB Amendment characters at all.
- Input fields didn’t display specific GB Amendment characters when creating a Dashboard View.
- On the Active Alert page, alert names dropped some GB Amendment characters in the right-hand Task pane.
- On the alert view page, the alert name title didn’t display some GB Amendment characters.
If you operate SCOM for users in Greater China, this is the rollup that makes those consoles and reports readable again.
UNIX and Linux: OpenSSL 3 and the newest distributions
The cross-platform side of UR4 is where the genuinely new capability sits:
- OpenSSL 3.x distribution support for the Operations Manager Linux agent — including Debian 13, RHEL 10, Rocky Linux 10, AlmaLinux 10 and Oracle Linux 10. If your Linux estate has been moving to the 10-generation enterprise distributions, this is what unblocks monitoring them.
- Ubuntu 26 support added for the Linux agent.
LastBootUpTimereturned empty inSCX_OperatingSystemon distributions that no longer maintain UTMP records — Debian 13 among them. Fixed.NumberOfUsersalways returned 0 inSCX_OperatingSystemon distributions usingsystemd-logindfor session management, such as Ubuntu 26. Fixed.- SCX agent certificate signing restored.
scxcertconfig.exefunctionality is working again, which unblocks certificate signing and SCX agent installation.
How to install SCOM 2022 UR4
Update rollups are cumulative. UR4 includes every fix from SCOM 2022 RTM, UR1, UR2, UR3 and all interim hotfixes, so if you’ve skipped a rollup you can go straight to UR4.
Packages are available from the Microsoft Update Catalog or as a manual download.
For Simplified SCOM Management Server Patching, the .exe is available from the Microsoft Download Center.
Updated management packs for Linux Operating Systems can be downloaded from the following Microsoft website:
Download System Center 2022 Management Pack for Linux Operating Systems from Official Microsoft Download Center.
For more information visit related Microsoft Support Page
The rollup contains these MSP files (KB5120166):
| Role | MSP file |
|---|---|
| Management Server | KB5120166-amd64-Server.msp |
| Operations Console | KB5120166-amd64-Console.msp |
| Web Console | KB5120166-amd64-WebConsole.msp |
| Gateway Server | KB5120166-amd64-Gateway.msp |
| Reporting | KB5120166-amd64-Reporting.msp |
| Agent | KB5120166-amd64-Agent.msp |
| ACS | KB5120166-amd64-ACS.msp |
Run each MSP from an elevated command prompt on the servers holding that role. Apply every MSP relevant to a given machine — if a server hosts both the Web Console and the Operations Console, it needs both. One MSP per role, per server.
Updating the UNIX/Linux management packs
To pick up the new distribution support, patching the management servers isn’t enough:
- Apply UR4 across your SCOM 2022 environment.
- Download the updated System Center 2022 Management Pack for Linux Operating Systems from the Microsoft Download Center.
- Run the management pack update package to extract the MP files.
- Import the updated management pack for each UNIX/Linux version you monitor.
- Upgrade each agent using the
Update-SCXAgentPowerShell cmdlet, or the UNIX/Linux Agent Upgrade Wizard in the Administration pane of the Operations Console.
Rolling back
If you need to uninstall an update:
msiexec /package {RTMProductCodeGUID} /uninstall {PatchCodeGUID}Note that uninstalling a server component rolls back binaries only — databases and imported management packs are unaffected. The RTM product code and patch code GUIDs for each component (Server, Console, Reporting, Agent, Gateway, Web Console, ACS) are listed in the Microsoft KB article for the rollup.
Should you patch now?
For most environments, yes — and the grooming fix is the reason. Every month you run without it is another month of Data Warehouse growth you didn’t budget for and reporting performance you’re paying for twice. Add the PowerShell widget access-control change and the restored Web Console state views, and UR4 is a rollup with a clear operational case rather than a routine cumulative refresh.
As always: patch a test or pre-production management group first, take a database backup before touching the management servers, and plan the agent updates in waves rather than all at once.
TopQore works with organisations running System Center Operations Manager at scale — from health checks and upgrade planning to update rollup deployment and management pack tuning. If you’d like a hand planning your UR4 rollout, get in touch.