Update Rollup 1 for System Center Operations Manager 2019 (KB4533415)

Introduction

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

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

• What’s New in System Center Operations Manager 2019 Update Rollup 1

Improvements and issues that are fixed

Web Console fixes and changes

• The State widget now supports sorting by health and age.

• Alert widgets can now be searched on by Date Time and sorted based upon age and severity.

• The alert link in an email notification returned the following error message when it's browsed: “Your session with the Web Console server expired." This occured even though the user was not logged in to web console. You will now see the login page post this fix.

• The Alert summary view window in SCOM Web console can now be expanded as required.

• When the Alert state was changed to some custom state, these alerts were not displayed in the web console. Alerts that have custom resolution states are now displayed.

• Some additional scrollbars appear if a customer widget is created in the web console or if the browser window size is reduced.

• Improvement: SCOM views load and save much faster than previously.

Unix/Linux/Network monitoring fixes and changes

• By default, SCX did Info level logging that caused SCX logs to become filled up quickly. In 2019 UR1, Warnings and Errors are logged by default instead of Info.

• During network device monitoring, if the node property is changed to null/empty, it displays the old value of the property, not the null value. The actual value, including null, is now displayed.

• In a scenario in which multiple (about 500) virtual network interfaces are running on an agent, SCOM sometimes receives heartbeat failure alerts for such agents. SCOM monitors only physical interfaces that are hosted on these computers. For monitoring virtual interfaces, you have to set "enumvif" to true.

• SNMP GET or SNMP WALK caused the monitoring host to stop responding if the network object ID was equal to ULONG Max. Error Event ID 4000 is logged because of this issues.

• For Linux distros servers, if the kernel version was 4.18 or later, file system-related performance data was shown as 0 in SCOM. This is fixed in FS provider to make it kernel version agnostic and collect file system stat info.

• Using Async Windows Management Infrastructure (MI) APIs is the default functionality from SCOM 2019 UR1 for scalability improvements. For more information, see this Learn article. 

 Admin console fixes

• When an admin created a “one-time maintenance mode schedule” for non-English locales, SCOM console displayed the following error message: “The client has been disconnected from the server. Please call ManagementGroup.Reconnect() to reestablish the connection.” Admins can now create one-time maintenance schedules.

• If the SCOM agent was multi-homed, SCOM 2019 MS always displayed the logon type as Interactive for this agent. The correct logon type is now displayed.

• The Unit monitor to check the correct logon type for "Run as Account" had an incorrect name and operational state. This is now fixed.

• The “Operations Manager Products” view in the Admin console did not update the Version column for the installed component version. This column now reflects the updated version of all the listed components.

Other fixes

• If system proxy is configured on the Reporting Server, proxy overrides are ignored by the “Report Console Watcher Monitor” and “Web Console Watcher Monitor.” This causes HTTP and HTTPS access to fail.  In the UR1 fix, the “Set proxy Direct” parameter of these monitors can be set to true so that the URLs can be accessed.

• If the IPV6 network was enabled, SCOM did not discover Windows clusters. (Windows clusters are deployed on servers only if the IPV6 network is enabled.) The IPV6 network is now supported for cluster monitoring.

• If the domain controller is moved to a different AD site, SCOM does not display the correct site name. Any dynamic groups that are created for SiteName will also fail. This management pack contains the fix for this issue. 

• If the working directory in profile.ps1 is changed, the “Restart System Center Management Health Service” recovery task fails. This is fixed now.

Previous fixes

In addition to these issues, all the issues that are fixed in SCOM 2016 UR8 and earlier update rollups for SCOM 2016 are also fixed in SCOM 2019 UR1. The details of the fixes are as follows.

• In a scenario in which SCOM monitors hundreds of virtual machines are hosted on a single Hyper-v server, the Health Service services for all virtual machine write into the VM page file simultaneously every hour. Because of this concurrent paging, disk I/O increases every hour, and the database becomes unresponsive. By default, HealthService.exe now has Memory Trimming enabled on an hourly schedule. The MemoryTrimming registry key is now provided in the following subkey to disable the memory trimming and control the duration:
  
  HKLM\Software\Microsoft\Microsoft Operations Manager\3.0\Setup\MemoryTrimming

  Values:
  
  Enable: 0 (trimming is disabled), 1 (trimming is enabled)​

  DelayInSeconds: Time that the agent waits to start trimming (default is 120)​

  ​PeriodInSeconds: Recurring period during which the working set should be trimmed (default is 3600)

• Historical data does not appear if the input reporting end time occurs before the group creation time. In this fix, historic data for a group (if data is available for objects in the group) is displayed regardless of the group creation time.

• Maintenance mode state changes that are recorded in the MaintenanceModeStage table require grooming as the table grows. If the table is large, grooming takes longer and the operation times out and returns an SQLTimeOut exception.

• If a group is renamed in a management pack, the console shows the new value but the PowerShell command Get-SCOMGroup returns the old name of the group. Database Updates functionality was inconsistent for SCOM group renaming through management packs and the SCOM console.

• CPU spike issues that occurred because of workflows that ran on all agents at the same time are fixed through script optimization and by removing the sync time.

• Improvement: Sometimes, the SQL stored procedure “p_SelectForNewTypeCache” took a long time to finish, and the SDK service did not start. This is now fixed so that this SQL stored procedure finishes faster.

• Improvement: The performance of the SCOM console when it lists groups is now improved.

• Users of a scoped group were not able to use the console.

• SCOM console crashed while it tried to connect to Azure Log Analytics and Azure Monitor.

• SCOM Network Devices Discovery now also probes for SNMP V3 devices.

• The "Agents by Health State" report showed duplicate agent names.

• Fixed an issue that prevented the addition of a group in the Storage Spaces Direct 2016 management pack dashboard.

• Linux agent cannot get the correct version and port details for JBoss EAP 7.1.

• An issue that cause creation of multiple empty temp files in the /tmp directory of Linux servers is fixed.

• Fixed the formatting issue that affected the output for the "Top10 CPU Processes" task when you used Windows Management Infrastructure (MI) APIs.

• Fixed an issue that corrupted the /etc/login.cfg file on AIX 7 computers during an installation or upgrade of the agent.

• AIX Agent is now transitioned to a 64-bit package to accommodate more stack and heap space if it is needed. This is to avoid any stack or heap overflow that occasionally causes heartbeat failure.

• The free memory calculation is now accommodated appropriately on the RHEL-7 platform.

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

To be able to see the correct agent version in SCOM, download this management pack.

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 UR1

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 introduces a frictionless way of updating the SCOM management server. The improvised user interface guides you through the installation steps that will update the management server, the databases, and the management packs.

You can also use the KB4533415-AMD64-Server.msp for an interfaceless updating mechanism, such as updating through SCCM, and so on. This also updates the server, the databases, and management packs.

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.

   • 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 mitigated 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 1 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.OperationsManager.Internal.mp

• Microsoft.SystemCenter.HtmlDashboard.Library.mp

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

• Microsoft.SystemCenter.2007.mp

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

• Microsoft.SystemCenter.Advisor.mpb

• Microsoft.SystemCenter.Advisor.Internal.mpb

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

• Microsoft.SystemCenter.DBUpdateHelper.mpb

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

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

Files updated in this rollup
 

Updated SQL files

Release Notes

For more information, see the Release Notes for this release.