Update Rollup 4 for System Center Operations Manager 2019

Update Rollup 4 for System Center Operations Manager 2019

Applies to: System Center 2019 Operations Manager 

Introduction

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

For the list of features that are released in Update Rollup 4, see What's New in System Center Operations Manager 2019 Update Rollup 4.

Prerequisite

Before installing Update Rollup 4 for System Center 2019 Operations Manager, follow the instructions at Remove duplicate Management pack aliases to remove duplicate Management pack aliases.

Improvements

• Support for Windows 11

• Enabled .NET4.8 support

• UI improvements in Operations console:

  • Support for sort option by column, in Overrides Summary.

  • For Monitors, Rules, Task and Discoveries, Management Pack label text is selectable in the workflow Properties window.

  • Added new fields for Class Technical Name in the State Views. Added the same in the wizard for creating a new Alert, Event, Performance or State View.

  • Added Target Class Display Name to help identify the target of a rule while selecting rules during the creation of a new Performance View.

  • Added 3 new columns Management Pack, Sealed and Members in the Authoring pane > Groups.

  • Added new column for Management Pack Display Name in the Authoring pane > Create Group wizard.

Issues that are fixed

Operations Manager 2019 Update Rollup 4 includes fixes for the following issues:

Operations Console  

• Get-SCOMGroup CmdLet in PowerShell not reflecting the updated name of a group .

• Edited alert properties in the alert views not being reflected sometimes without switching views.

• The Reason and/or Comment field not being updated correctly in an existing maintenance mode schedule.

• Maintenance Mode Schedules fail to work when creating multiple schedules at once.

• Information around update rollup applied to Management Servers not being reflected correctly in the Ops console Admin view.

• MonitoringHost.exe process(es) crashes when a Management Server had neither Microsoft OLE DB Driver 18 for SQL Server nor SQL Server 2012 Native client 11.0 installed.

• In high-load environments, when AlertUpdate data was put in the Pending send queue, there was an issue processing these and event 5204 would get logged which was causing the All-Management Resource Pool to go down.

• Updating an existing Console Task would automatically switch the Task Target (class) to System entity instead of the one that was initially selected.

• Edit an existing Active Directory Integration Failover Configuration when wanting to add or remove Management Servers in the Failover list.

• The MP Reference Alias generator is case-sensitive now and will create only unique Aliases for Management packs.

• The “Installed column” is now sortable in the Operations Manager product views.

Web Console

• Authentication failing in web console if password of the account used would contain the “:” character.

• New Dashboard Wizard in the web console would fail with MPInfra_p_ManagementPackInstall exception.

Other Fixes:

• Database Registry that was created for temporary usage after patch or upgrade installation in 2019UR3 is now being deleted.

• There was a special scenario where APM would crash IIS Application Pools when W3WP was trying to load any type of managed DLL which was built as 64bit. These types of DLLs will no longer cause APM to crash the IIS Application Pool.

• The Insecure Direct Object Reference Vulnerability issue related to APM websites

• SNMP Traps sent through a proxy would not be received.

• Network discovery failure for network devices with HSRP that do not have the AF_NET IP address.

• Generic event reports coming up empty for events generated by SNMP devices.

• SDK service not being able to reconnect to SQL after a long SQL AG failover.

Performance improvements:

• Optimized the table indexes to improve record insertion rate.

• Added indices to 2 Data Warehouse tables to improve performance.

• Included Date and time information for Performance Data collected by PowerShell scripts.

• The PerformanceRuleInstance table which was causing performance issues is now being groomed correctly.

• Improved performance of ACS report queries that are using the [dbo].[spInsertString] stored procedure .

Unix/Linux/Network monitoring fixes and changes:

• Added supportability on Operations Manager Linux Agent for Rocky Linux 8, and Alma Linux 8.

• The counter name “% Free Space” has been changed to “Used Megabytes” in Linux RHEL 6 and RHEL 7 MP for accurate representation.

• Corrected the performance counter collected by “Used Megabytes” rules in RHEL 6 and 7 MPs.

• The file system statistics have been enhanced to match the data with Linux standard commands.

• Linux agent  now uses SHA2 to encrypt for certificates.

• log rotate configuration files were getting deleted as part of Linux agent upgrade.

• OMI agent crash issue during log rotate.

• OMI logrotate SELinux module was getting uninstalled as part of Linux agent upgrade

• Memory corruption issue that would cause a crash of MonitoringHost.exe when it would fail to perform a SSH call to a Cross-Platform Agent has been fixed.

• ECDSA and ED25519 keys are now able to authenticate with Operations manager Console.

• Some JBOSS applications were not discovered from JEE MP.

• Fixed the /etc/opt/microsoft/scx/conf/scx-release file content for Oracle Linux

• Increased the limit to 128 words (from 64 words) for the filter associated with OMI WQL queries.

• Process monitoring related issues for Unix/Linux servers with a very large number of processes.

• Privilege escalation security issue related to Kerberos setup.

• Non-IP cluster resource (ex. Disk) getting discovered as an IPv6 resource.

• TLS 1.2 is now enabled by default for Linux agents.

• Cross platform DLLs hash mismatch is fixed.

• Linux Agent memory leak issue.

Previous fixes

All the issues that were fixed in SCOM 2016 UR10 and the earlier hotfixes for SCOM 2019 are also included in SCOM 2019 UR4. 

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

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 UR4

Installation notes

• You must run this update rollup as an 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, after installation, 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 about simplified see the g 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.
    

   • 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:

• 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 4 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/Linux Agent 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.OperationsManager.Telemetry.mp

• Microsoft.SystemCenter.Library.mpb

• Microsoft.SystemCenter.OperationsManager.Infra.mp

• Microsoft.SystemCenter.OperationsManager.Infra.(LANGUAGECODE_3LTR).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

• Microsoft.SystemCenter.DataWarehouse.Internal.mp

• Microsoft.SystemCenter.DataWarehouse.Internal.(LANGUAGECODE_3LTR).mp

• Microsoft.SystemCenter.Apm.Infrastructure.mpb

• Microsoft.SystemCenter.DataWarehouse.Library.mp

Files updated in this rollup:

Updated SQL files