Update Rollup 1 for System Center Operations Manager 2019

Applies to: System Center 2019 Operations Manager

Introduction


This article describesthe System Center Operations Manager 2019 new features and issues that are fixed in UpdateRollup 1. This article also contains the installation instructions forthis update.

For the list of featuresreleased in Update Rollup 1, please refer:

  • What’s New in System CenterOperations Manager 2019 Update Rollup 1 here

Improvements and issues that are fixed


WebConsole Fixes/Changes:
  • State widget now supports sorting by health and age. 
  • Alert widgets can now be searched on Date Time and sorted based upon age and severity.
  • The alert link in email notification when browsed throws an error, “Your session with the Web Console server expired" even though the user was not logged in web console . You will now see the login page post this fix.
  • Alert summary view in SCOM Web console was fixed in size.  This can be expanded as required now.
  • When Alert state is changed to some custom state, then these alerts are not displayed in web console. Alerts with custom resolution states will be displayed now.
  • Few additional scrollbars appear when a customer widget is created in web console or browser window size is reduced.
  • Improvement: SCOM views will load/save much faster than before. 
Unix/Linux/Network Monitoring Fixes/Changes:
  • SCX by default does Info level logging which causes SCX logs to be filled up soon. With 2019 UR1, Warnings and Errors will be logged by default not Info.
  • In the 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 will be displayed now which includes null.
  • In a scenario where multiple (~500) virtual network interfaces are running on agent, SCOM sometimes received heartbeat failure alerts for such agents. SCOM will monitor only physical interfaces hosted on these machines. For monitoring virtual interfaces, you need to set "enumvif" to true. 
  • SNMPGET or SNMP WALK resulted monitoring host to crash when the network object IDis equal to ULONG Max. There is an error with event ID 4000 due to this crash.
  • For linux distros servers, when the kernel version >= 4.18, then file system related performance data is shown as 0 in SCOM. This is fixed in FS provider to make it kernel version agnostic and collect file system stat info.
  • Use of Async Windows Management Infrastructure (MI) APIs is default functionality from SCOM 2019 UR1 for scalability improvements.
    More details here

 AdminConsole Fixes:
  • When admin created “one-time maintenance mode schedule” for non-English locales, SCOM console displays an error “The client has been disconnected from the server. Please call ManagementGroup.Reconnect() to reestablish the connection”. Admin would be able to create one-time maintenance schedule now.
  • When SCOM agent is multihomed, then SCOM 2019 MS always displays logon type as “Interactive” for this agent. The correct logon type will be displayed now.
  • Unit monitor to check correct logon type for Run as Account had incorrect name and Operational State.
  • “Operations Manager Products” view in Admin console did not update the “Version” column for the installed component version. This column will now reflect the updated version of all the components listed.
Others:
  • When system proxy is configured on the Reporting Server; proxy overrides are ignored by the “Report Console Watcher Monitor” and “Web Console Watcher Monitor” and as a result HTTP/HTTPS access fails.  With UR1 fix, “Set proxy Direct” parameter of the mentioned monitors can be set to true and URLs will be accessed.
  • SCOM did not discover Windows Cluster which are deployed on servers with IPV6 network only enabled. IPV6 network will be supported for cluster monitoring now.
  • When the Domain controller is moved to a different AD site, then SCOM does not display the correct site name. Any dynamic group which are created for SiteName will also fail. This MP contains the fix. 
  • When working directory in profile.ps1 is changed, recovery task  “Restart System Center Management Health Service” fails. This is fixed now.
 
In addition tothese, all the issues fixed in SCOM 2016 UR8 and prior UR for SCOM 2016 are also fixed in SCOM 2019UR1. Details of the fixes are below.
  • In a scenario where SCOM monitors 100s of virtual machines hosted on a single Hyper-v server; every hour the healthservice.exe of each Virtual machine write into the VM page file simultaneously. Due to this concurrent paging, every hour disk I/O increases and database becomes unresponsive. HealthService.exe now have Memory Trimming enabled by default on an hourly schedule. A registry key is provided to disable the memory trimming and control the duration.
          Registry key is: "HKLM\Software\Microsoft\Microsoft Operations Manager\3.0\Setup\MemoryTrimming"

         Enable – 0 (Trimming is disabled); 1 (trimming is enabled)

         DelayInSeconds – Time period agent waits to start trimming (default is 120s)

         PeriodInSeconds – Recurring period at which the working set should be trimmed (default is 3600s)
  • Historical data do not appear, if input reporting end time is before group creation time. With this fix, historic data for a group (if data is available for objects in the group) would be displayed irrespective of group creation time.
  • Maintenance mode state changes which are recorded in MaintenanceModeStage table requires grooming when table grows. If the table is large, grooming takes longer and the operation times out with SQLTimeOut exception.
  • If a group is renamed in a Management pack, then console shows the new value but Powershell command Get-SCOMGroup returns the old name of group. Database Updates functionality was inconsistent for SCOM group renaming through MP and SCOM Console.
  • CPU Spike issues because of workflows running on all agents at the same time is addressed through script optimization and removing the sync time. 
  • Improvement: Sometimes SQL stored procedure “p_SelectForNewTypeCache” takes long time to complete, and SDK service fails to start. This is fixed and above SQL stored procedure will complete faster now.
  • Improved the performance of SCOM console in listing the groups.
  • Users of a scoped group are not able to use the Console.
  • SCOM console crashes while trying to connect to Azure Log Analytics and Azure Monitor.
  • SCOM Network Device Re-Discovery now probes for SNMP V3 devices too.
  • Agents by Health State report shows duplicate agent names.
  • Fixed an issue that prevented addition of a group in the Storage Spaces Direct 2016 management pack dashboard.
  • Linux agent is not able to get the correct version and portdetails for JBoss EAP 7.1.
  • An issue that lead to creation of multiple empty temp files in the/tmp directory of Linux servers has been fixed.
  • Fixed the formatting issue with the output for the task ‘Top10 CPUProcesses' when using Windows Management Infrastructure (MI) APIs.
  • Fixed an issue that caused the corruption of /etc/login.cfg fileon AIX 7 machines during install/upgrade of the agent.
  • AIX Agent is now transitioned to 64-bit package to accommodatemore stack and heap space if needed to avoid any stack/heap overflow whichoccasionally leads to heartbeat failure.
  • Free memory calculation accommodated appropriately on RHEL-7platform.

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


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

Microsoft Update

To obtain and install fromMicrosoft Update, follow below steps on a computer that has an OperationsManager component installed:Click Start, and then click Control Panel.

  1. In Control Panel, double-click Windows Update.
  2. In the Windows Update window, click Check Online for updates from Microsoft Update.
  3. Click Important updates are available.
  4. Select the update rollup package, and then click Ok.
  5. Click Install updates to install the update package.

If your computer isrunning Windows Server 2016 or later, follow these steps:

  1. Click Start ->Settings -> Update and Security
  2. On the Windows Update tab, click Check Online for updates from Microsoft Update.
  3. Click Important updates are available.
  4. Select the update rollup package and install the update package.

Manual download

Go to the followingwebsites to manually download the update packages from the Microsoft UpdateCatalog:

 For information abouthow to download Microsoft support files from online services, click the article119591 

Exe for "Simplified SCOMManagement Server Patching" can be found at this DLC link.

Please download this MP to see the correct version agent version in SCOM.

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 thatthe server holds.

Installation instructions for Operations Manager 2019 UR1


Installation notes

  • You must run this update rollup as 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.
  • Do not apply an update rollup immediately after you install System Center Operations Manager 2019. Wait several hours after deployment of a new management group before you apply any update rollup.
  • If User Account Control is enabled, run the .msp update files from an elevated command prompt.

Simplified Management Server Patching:

SCOM 2019 Update Rollup 1 introduces a frictionless way ofpatching the SCOM management server. The improvised user interface will guideyou through the installation steps which will patch the management server,update the databases and update the management packs.

You may also use the KB4533415-AMD64-Server.msp forinterface-less patching mechanism such as patching via SCCM etc. It shall alsopatch the server, update the databases and management packs.

For more details please refer here.

Supported installationorder

  1. Install the update rollup package on the following server infrastructure:
    • Management server or servers can be patched 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
  2. Apply Agent updates.
  3. Update Unix/Linux MPs and Agents.

UNIX and Linuxmanagement pack update

To install the updatedmonitoring packs and agents for UNIX and Linux operating systems, follow thesesteps:

  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 Center2019 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.
Uninstall information
To uninstall an update,run the following command:
msiexec /uninstall PatchCodeGuid /package RTMProductCodeGuid
Note: The PatchCodeGuid placeholderrepresents one of the following GUIDs.
For uninstalling theserver component, only binaries are rolled back while databases and importedmanagement packs remains unaffected.
 
PatchCodeGUID
RTMProductCodeGuid
Component
D2E044CF-67FA-4863-A179-D79E6FC232E6
5016D727-313F-451D-9990-4DB326D00F06
 
Server
83575003-4912-4E9B-B775-183D27A4C4AF
88D7DF38-306E-4195-8C1A-C19A4E35C728
 
Console
F5E87081-ACA4-47A2-B054-03DCB64A187A
D80F1A1B-200C-421C-B876-F440A7BDAA67
 
Web Console
F8E61F75-5E22-4455-A402-58D99CD00924
10137A63-5AE9-4B40-8BF2-DBAE7B596359
 
Reporting
156EB41D-0CB6-4493-B751-E0F548EA8878
4ED3E2E8-E655-4F9C-8A95-10ADD6700181
 
Gateway
10E492C5-51D7-40A1-A33D-CF9DF282C8C3 
 
CEB9E45B-2152-4C10-A022-0825B53B632F
 
Agent

Files updated in this update rollup


Followingmanagement packs are included in the Server component at "%SystemDrive%\Program Files\Microsoft System Center\OperationsManager\Server\ManagementPacks 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 Updates in this rollup are:

File

Version

File Size

Microsoft.EnterpriseManagement.DataAccessService.Core.dll

10.19.10311.0

686KB

Microsoft.EnterpriseManagement.DataAccessLayer.dll

10.19.10311.0

2.43KB

MOMAgentInstaller.exe

10.19.10311.0

401KB

MOMAgentInstallerPS.dll

10.19.10311.0

96.1KB

Microsoft.Mom.Common.dll

10.19.10311.0

228KB

MOMAgentManagement.dll

10.19.10311.0

266KB

Microsoft.SystemCenter.DbUpdateHelper.dll

10.19.10311.0

18.9KB

sm-auto-discovery.dll

10.19.10311.0

4.27MB

sm-discovery.dll

10.19.10311.0

2.40MB

sm-snmp.dll

10.19.10140.0

616KB

AgentConfigManager.dll

10.19.10140.0

133KB

HealthService.dll

10.19.10140.0

3.03MB

HealthServiceRuntime.dll

10.19.10140.0

289KB

MOMWsManModules.dll

10.19.10140.0

222KB

MOMModules.dll

10.19.10140.0

2.34MB

Microsoft.SystemCenter.CrossPlatform.ClientLibrary.MPAbstractions.dll

10.19.1064.0

86.3KB

Microsoft.Mom.Sdk.ServiceHost.exe

10.19.10311.0

46.6KB

AgentControlPanel.exe

10.19.10140.0

1.21MB

HealthService.exe

10.19.10140.0

26.3KB

PerfCounterMonitor.dll

10.19.10140.0

1.05MB

sm-snmp.dll

10.19.10140.0

616KB

AgentConfigManager.dll

10.19.10140.0

133KB

HealthService.dll

10.19.10140.0

3.03MB

HealthServiceRuntime.dll

10.19.10140.0

289KB

MOMWsManModules.dll

10.19.10140.0

222KB

MOMModules.dll

10.19.10140.0

2.34MB

AgentControlPanel.exe

10.19.10140.0

1.21MB

HealthService.exe

10.19.10140.0

26.3KB

Microsoft.EnterpriseManagement.UI.Administration.dll

10.19.10311.0

4.44MB

Microsoft.MOM.UI.Components.dll

10.19.10311.0

5.70MB

Microsoft.Mom.UI.Wrappers.dll

10.19.10311.0

92.1KB

Microsoft.SystemCenter.OperationsManagerV10.Commands.dll

10.19.10311.0

668KB

Microsoft.IdentityModel.Clients.ActiveDirectory.dll

2.0.1965.0

86.7KB

Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms.dll

2.0.1965.0

36.2KB

Newtonsoft.Json.dll

8.0.2.19309

473KB

Microsoft.SystemCenter.CrossPlatform.ClientLibrary.MPAbstractions.dll

10.19.1064.0

86.3KB

Microsoft.EnterpriseManagement.OperationsManager.dll

10.19.10311.0

1.05MB

Microsoft.EnterpriseManagement.Runtime.dll

10.19.10311.0

76.9KB

Microsoft.EnterpriseManagement.OMDataService.dll

10.19.10311.0

537KB

Microsoft.Web.Infrastructure.dll

1.0.21105.407

44.3KB

System.Web.Webpages.dll

3.0.60510.0

208KB

System.Web.Webpages.Deployment.dll

3.0.61128.0

42.1KB



Updated SQL files

update_rollup_mom_db.sql

293KB

UR_Datawarehouse.sql

 1KB



Release Notes


Release notes for this release can be found here.