Update Rollup 3 for System Center Operations Manager 2019 (KB4594078)

Introduction

This article describes the new features and issues that are fixed in System Center Operations Manager 2019 Update Rollup 3. This article also contains the installation instructions for this update.

For the list of features that are released in Update Rollup 3, see the following Microsoft Learn article:

What's New in System Center Operations Manager 2019 Update Rollup 3.

Improvements and issues that are fixed

Operations Console fixes and changes

• SCOM UI scaling issues for high resolution displays have been fixed to work seamlessly.

• Some IPv4 resources were being discovered as IPv6 in a cluster where both resources co-existed. This logic has been fixed to make sure that IPv4 resources are no longer discovered as IPv6.

• Fixed the issue of the UR2 setup stalling at the “Removing backup files” stage. The task wait time threshold has been set to 30 mins. We recommend that you have Service Broker always enabled for smooth functioning of Operations Manager.

• The assumption to have provider element be the first reference in the connection string hw removed in the OleDB module.

• Fixed the combo box-related text issue regarding the domain of a new RunAs account getting incorrectly changed. This issue occurred when you created a new RunAs Account in the SCOM console for an account that belongs to an untrusted domain. The fix makes sure that the domain of the newly created RunAs Account remains the one that was initially specified during the account creation.

• Fixed the “invalid class” error that occurred when you added a subscriber by having user details that exceeded 1,024 attributes.

• Daily aggregation of reports now takes date and time into consideration to ensure that time period calculation is accurate.

• Fixed the monitoring agent-related issue that affected formatted strings. These are now read from the provider DLLs to show a localized string.

• Fixed an issue in which the monitor erroneously turns critical because of the URL module incorrectly parsing the charset header value.

Web Console fixes and changes

• The security issue regarding reverse tab nabbing has been fixed in the Operations Manager web console.

• Fixed the filter issue that occurred when a state view was created in “My Workspace” in the web console.

• Global search option for Metrics section of Performance Widget in the Web Console is fixed.

Other fixes

• Updating Management Groups with a shared Data Warehouse to UR2 sometimes caused issues that affected reports deployment. This is now fixed by restricting Installation of sealed MP by using the same version in the Data Warehouse.

• Migrated SSL Admin certificates to Microsoft PKI - Pinning Thread for Agents.

• Fixed the issue that occurs when the UR2 SQL patch is run again on a previously patched database.

• Fixed the deadlock issues that occur when SCOM agents are put into maintenance mode by using SCOM API with parallelism. The fix involves adding indexes and updating the SQL queries.

• Performance improvement of the DB function fn_ManagedEntityLifetimeDependency.

• Updated the scoping logic that's used in some State View queries and Console Cache Refresh queries for performance improvement.

• Added "Recompile" flag for sprocs "p_SelectForTypeCache" and "p_SelectForNewTypeCache" for SCOM perf improvement.

Unix/Linux/Network monitoring fixes and changes

• Fixed the issue that affected SSH call failure that, in turn, caused memory corruption.

• Fixed a thread race condition that was causing Linux script-based monitoring failures because of child process that didn't start.

• Fixed an infinite loop condition that was causing the "100 percent CPU"-related issue.

• Fixed the MonitoringHost.exe process crashes on the Management Servers that run the Unix/Linux workflows.

• Fixed the memory leak that occurs inside the WsMan modules when UseMIAPI is enabled abd uses workflows that have SplitItems set to TRUE for the EnumerateAsWA WriteAction.

Previous fixes

In addition to these issues, all the issues that are fixed in SCOM 2016 UR10 and earlier update rollups for SCOM 2019 are also fixed in SCOM 2019 UR3.

How to obtain Update Rollup 3 for System Center Operations Manager 2019

Update packages for Operations Manager are available from Microsoft Update or by manual download.

Microsoft Update

To obtain and install from Microsoft Update, follow these steps on a computer that has an Operations Manager component installed:

1. Select Start, and then select Control Panel.

2. In Control Panel, double-click Windows Update.

3. In the Windows Update window, select Check Online for updates from Microsoft Update.

4. Select Important updates are available.

5. Select the update rollup package, and then select OK.

6. Select Install updates to install the update package.

If your computer is running Windows Server 2016 or a later version, follow these steps:

1. Select Start > Settings > Update and Security.

2. On the Windows Update tab, select Check Online for updates from Microsoft Update.

3. Select Important updates are available.

4. Select the update rollup package, and install the update package.

Manual download

• Go to the following website to manually download the update packages from the Microsoft Update Catalog:
  
  Download the Operations Manager update package now.

• For information about how to download Microsoft support files from online services, see Knowledge Base article 119591.

• For the .exe file for "Simplified SCOM Management Server Patching," go to this Microsoft Download Center webpage.

Note MSP files are included in the update rollup package. Apply all MSP files that relate to a specific computer. For example, if the web console and console roles are installed on a management server, apply the MSP files on the management server. Apply one MSP file on a server for each specific role that the server holds.