Update Rollup 2 for System Center Operations Manager 2019 (KB4558752)

Introduction

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

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

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

Improvements and issues that are fixed

Web Console fixes and changes

• When you called the REST API for SCOM 2019 web console to get classes, the ID was being returned as className. This issue has been fixed. The REST API now supports classname, ID and MP!ClassName by using the same parameter names.

• The alerts that were triggered previously in the web console can be closed even after the associated monitor is disabled or an override is created for it.

• The exception handling in legacy web console alert view is fixed to show the correct error message when Alert Closure fails.

• Enabled auto-sign using windows authentication for web console with the session time-out interval value being used from the Web.config file. The default and maximum value for session time-out is 1,440 minutes.

• Cross-Site Scripting (XSS) attacks are prevented in the web console.

• When you create a custom dashboard and use the performance widget, the time that's displayed in graph will convert correctly to the local computer time.

• Web Console Performance View "Look for: Items by text search" now has consistent formatting.

• Web Console wording that's related to the closure of alerts from rules and monitors is corrected for clarity.

• Added icons for information-based alerts in the web console.

• Fixed the issue that affected the ability to schedule a report using the App Advisor web console.

Operations Console fixes and changes

• The updated behavior for auto-resolution of alerts by grooming is as follows:

  • Closing all Alerts from Rules that were not been modified for "x" days.

  • Closing all Alerts from Monitors (that are healthy now) that were not modified for "y'"days

• The cmdlet Export-SCOMEffectiveMonitoringConfiguration was initially giving incorrect "Overridden Status" in the output for overrides on specific parameters. It will now give a correct summary of the Monitors, Rules and Overrides on an object.

• Fixed the Alert Generation logic for Data Access Service SPN rule. Alert will be generated only if the SPNs are not correctly registered for Data Access Service depending on user context. The Alert Knowledge was also fixed to provide correct resolution details to the user.

• Fixed the issue with conversion of data smaller than 0.01 that was generated by Rule or Monitor. The data was being incorrectly transformed to a wrong (big) value on systems with OS locale language that uses a comma (,) instead of period (.) as a decimal format.

• Fixed an issue that affected the date format and loading of controls in the resource downtime report.

• Fixed and issue that caused an incorrect end date to be displayed in the SCOM "Availability" report.

• Fixed the issue for editing Closed Alerts. Closed Alerts can now be edited even if the Source Monitor is unhealthy.

• Alert Auto Resolution SPROC was fixed to check health of actual monitor instead of the Root Monitor.

• Console version is now displayed in the Help > About pane of web console.

• After you apply an UR to SCOM the agent install directory path now displays correct information. This path is used for setting all the registries which require agent path.

• Management Server and database details will be shown under the view  Administration > Operations Manager Products even when the server is configured with a custom port.

• Management Pack Import is now compatible for SCOM 2007 --> SCOM 2016 Upgrade version (Upgraded directly or Indirectly). Property "DisplayName" column is retrieved dynamically from Managed Property.

• The Platform and Platform Version details are now populated while using the Discovery Wizard from console or PowerShell.

• If a user runs a report and selects a date range, the report duration now displays the correct values. The issue was that the EndDate data returned was off by 1 day, this is now fixed.

• Reports will now not show objects which were deleted before start time.

• Improved the usability of the web application alert state view by allowing its expansion for details.

• Improved the usability of the stage change events view in the web application transaction monitors by fixing the scroll bar issue.

Unix/Linux/Network monitoring fixes and changes

• Installing SCOM 2019 agent on a CentOS 7.7 server and getting it to report to SCOM 2012 R2 Management Group is now supported.

• SLES 15 PPC discovery Management Pack introduced by NICE was trying to discover the agent using Universal MP in UR1 which does not work for PPC architecture. This is now fixed to use discovery MP provided by NICE.

• Appropriate changes in OMI to log timing information are made.

• Enabled log rotation on omiserver-recv.trc & omiserver-send.trc files so that it will be rotated once certain threshold is reached.

• When HTTP tracing is set, omiserver-recv.trc & omiserver-send.trc files are filled quickly. But if these files size are not monitored appropriately, file space is fully consumed in about one day. This may cause the system going to enter an "unused" state. This is now fixed.

• Changed time to UTC in OMI log messages.

• IPV6 support in XPLAT: Added capability for monitoring Unix/Linux system which has only IPV6 address in DNS.

• Added support for MIAPI enabled script based monitoring without base64 encoding.

• Split RunAs Account targets to make it easier to create dynamic groups for different Linux distributions and versions.

• Added new monitors that have an overridable process name in Universal Linux Management Pack, per following matrix.

Other fixes:

• SPROC is updated to handle Alert Source Path Names which are greater than 512 in length. The issue was around a mismatch ,where the table that was populating the DB was allowing larger strings while the table which was populated in this view took only 512. This caused data truncation and subsequently console crash.

• Active Directory Integration rules are visible & editable in an upgraded 2019 Console. More Info: https://techcommunity.microsoft.com/t5/system-center-blog/update-on-active-directory-integration-with-scom/ba-p/1226768

• The pending action  task (as part of pending management for management servers) no longer fails because of database permission issue.

• The UR1 update had a dependency on .NET 3.5. This dependency is now removed.

• Registry values under the following path will be preserved through updating:

  • SYSTEM\CurrentControlSet\Services\EventLog\Operations Manager; MaxSize

  • SYSTEM\CurrentControlSet\Services\HealthService\Parameters; Persistence Checkpoint Depth Maximum

We continue to recommend that users back up those values and verify them after updating.

• Fixed an issue that involved the "Version string portion was too short or too long" exception  that blocked further progress on the “Where to Monitor From” page in the Add Monitoring Wizard. An empty string-related check is added to handle the case if the registry entry does not exist.

• Updated the published Management System Center 2019 Management Pack for JEE Application Servers with the correct Beanspy binaries. This helps users connect to JMX Stores that facilitates deep monitoring of applications.

Download  System Center 2019 Operations Manager UR2 Management Pack for Java EE.
 

• OnDemand recalculation of "Apache SSL Certificate Expiration" monitor was configured to change its state to Unhealthy by default. This meant, Re-Calculation of Monitor or Restarting Health Service was changing the monitor to Unhealthy. In this fix, Monitor will be Unhealthy only when Days until Expiration is less than the configured threshold (set to 7 by default).   

Download System Center 2019  Operations Manager UR2 Management Pack for OSS.  

• Performance improvement: Added "Recompile" hint to the query "ModulesByCritera" that runs frequently on SCOM DB.
   

Previous fixes:

All the issues that were fixed in SCOM 2016 UR9 and the hotfix for SCOM 2019 are also included in SCOM 2019 UR2. 

For more information, see:

https://support.microsoft.com/en-in/help/4546986/update-rollup-9-for-system-center-2016-operations-manager

https://support.microsoft.com/en-in/help/4551468/system-center-operations-manager-2019-hotfix-for-alert-management

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

How to obtain Update Rollup 2 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.

Installation instructions for Operations Manager 2019 UR2

Installation notes

• You must run this update rollup as a SCOM administrator.

• If you don't want to restart the computer after you apply the console update, close the console before you apply the update for the console role.

• If this is a fresh installation of System Center Operations Manager 2019, wait for a few hours (generally 6–8 hours) before you apply this update rollup.

• If User Account Control is enabled, run the .msp update files at an elevated command prompt.

Simplified Management Server Patching

• SCOM 2019 Update Rollup 1 introduced a frictionless way of updating the SCOM management server.

• For more information see the following Knowledge Base article:4538900 Simplified SCOM 2019 Management Server Patching

Supported installation order

1. Install the update rollup package on the following server infrastructure.
   
   Note Management server or servers can be updated by using either the msp or simplified Management Server Patching user interface.

2. • Audit Collection Services

   • Web console server role computers

   • Gateway

   • Operations console role computers

   • Reporting

Note You may encounter an error at the Management Pack import step during the management server update. To mitigate this error, do either of the following:

1. • Install .NET Framework 3.5, and then rerun the management server update.

   • Import the management packs manually.

2. Apply agent updates.

3. Update Unix and Linux MPs and agents.

UNIX and Linux management pack update

To install the updated monitoring packs and agents for UNIX and Linux operating systems, follow these steps: 

1. Apply Update Rollup 2 to your System Center Operations Manager 2019 environment.

2. Download the updated management packs for System Center 2019 from the following Microsoft website:

   System Center 2019 Management Pack for UNIX and Linux Operating Systems 

3. Install the management pack update package to extract the management pack files.

4. Import the updated management pack for each version of Linux or UNIX that you are monitoring in your environment.

5. Upgrade each agent to the latest version by using the Update-SCXAgent Windows PowerShell cmdlet or the UNIX/LinuxAgent Upgrade Wizard in the Administration pane of the Operations Console.

Uninstallation information 

To uninstall an update, run the following command:
msiexec /uninstall PatchCodeGuid /package RTMProductCodeGuid

Note The <PatchCodeGuid> placeholder represents one of the following GUIDs.

For uninstalling the server component, only binaries are rolled back while databases and imported management packs remain unaffected.

Files updated in this update rollup

The following management packs are included in the Server component at:

%SystemDrive%\Program Files\Microsoft System Center\OperationsManager\Server\Management Packs for Update Rollups

• Microsoft.SystemCenter.DataWarehouse.Report.Library.mp

• Microsoft.SystemCenter.DataWarehouse.Report.Library.(LANGUAGECODE_3LTR).mp

• Microsoft.SystemCenter.OperationsManager.Reports.2007.mp

• Microsoft.SystemCenter.Internal.mp

• Microsoft.SystemCenter.HtmlDashboard.Library.mp

• Microsoft.SystemCenter.HtmlDashboard.Library.(LANGUAGECODE_3LTR).mp

• Microsoft.SystemCenter.OperationsManager.DataAccessService.mp

• Microsoft.SystemCenter.OperationsManager.DataAccessService.(LANGUAGECODE_3LTR).mp

• Microsoft.SystemCenter.OperationsManager.Internal.mp

• Microsoft.SystemCenter.WebApplicationSolutions.Library.mpb

• Microsoft.SystemCenter.DataWarehouse.Report.Library.mp

• Microsoft.SystemCenter.Library.mpb

• Microsoft.SystemCenter.OperationsManager.DataAccessService.mp

• Microsoft.SystemCenter.WebApplicationSolutions.Library.mpb

• Microsoft.SystemCenter.2007.mp

• Microsoft.SystemCenter.2007.(LANGUAGECODE_3LTR).mp

• Microsoft.SystemCenter.Advisor.Internal.mpb

• Microsoft.SystemCenter.Advisor.mpb

• Microsoft.SystemCenter.Advisor.Resources.(LANGUAGECODE_3LTR).mpb

• Microsoft.SystemCenter.DBUpdateHelper.mpb

 Files updated in this rollup:

Updated SQL files  

Release Notes

For more information, see the Release Notes for this release