Update Rollup 2 for System Center Operations Manager 2019

Applies to: System Center Operations Manager

Introduction


This article describes the new features andissues that are fixed in System Center Operations Manager 2019 UpdateRollup 2. This article also contains the installation instructions forthis update.

For the list of features that are released in UpdateRollup 2, see the following Microsoft Docs article: 

What'sNew 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 and now the REST API now supports classnameID, 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 being 1440 minutes.
  • Cross-Site Scripting (XSS) attacks are prevented in the web console.
  • When creating a custom dashboard and using the performance widget, time displayed in graph will convert correctly to the local machine's time. 
  • Web Console Performance View "Look for: Items by text search" will have consistent formatting.
  • Web Console wording related to closure of alerts from rules and monitors is corrected for clarity.
  • Added icons for information-based alerts in web console.
  • Fixed the issue around ability to schedule a report using App Advisor web console.

Operations Console fixesand changes

  • 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 which 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 incorrect end date being 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 Help > About pane of web console.
  • After applying 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/Networkmonitoring 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 with overridable process name in Universal Linux Management Pack as per below matrix.

 

Monitor Name

RHEL 8

SLES 15

Other Linux Universals

 Process Name

Enabled

Process Name

Enabled

Process Name

Enabled

Process Audit Service Health 

 

auditd

True

Auditd

False

auditd

False

Process Cron Service Health 

 

crond

True

Cron

True

crond

False

Process Syslog Service Health 

 

systemd-journal

True

systemd-journal

True

systemd-journal

False

Process Udev Service Health 

 

systemd-udevd

True

systemd-udevd

True

systemd-udevd

False

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 patch had a dependency on .net3.5 ,this dependency is now removed.

  • Registry values under following path will be preserved through patching:
    • SYSTEM\CurrentControlSet\Services\EventLog\Operations Manager; MaxSize
    • SYSTEM\CurrentControlSet\Services\HealthService\Parameters; Persistence Checkpoint Depth Maximum

We continue to recommend that users back upthose 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 Packfor 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 UR2Management 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 UR9and 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 forSystem Center Operations Manager 2019

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

Microsoft Update

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

  1. Select Start,and then select Control Panel.
  2. InControl Panel, double-click Windows Update.
  3. Inthe Windows Update window, select Check Online forupdates from Microsoft Update.
  4. Select Importantupdates are available.
  5. Selectthe update rollup package, and then select OK.
  6. Select Installupdates to install the update package.

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

  1. Select Start >Settings > Updateand Security.
  2. On the Windows Update tab, select CheckOnline for updates from Microsoft Update.
  3. Select Important updates are available.
  4. Select the update rollup package and install the update package.

Manual download

Note MSP files are included in the updaterollup package. Apply all MSP files that relate to a specific computer. Forexample, 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 aserver for each specific role that the server holds.

Installation instructions for Operations Manager 2019 UR2


Installation notes

  • You must run thisupdate rollup as a SCOM administrator.
  • If you don't wantto restart the computer after you apply the console update, close the consolebefore you apply the update for the console role.
  • If thisis a fresh installation of System Center Operations Manager 2019, wait for afew hours (generally 6–8 hours) before you apply this update rollup.
  • If User AccountControl is enabled, run the .msp update files at an elevated command prompt.

Simplified Management Server Patching

  • SCOM 2019 Update Rollup 1 introduced africtionless way of updating the SCOM management server.
  • For more information see the followingKnowledge Base article:4538900 SimplifiedSCOM 2019 Management Server Patching

Supported installation order

  1. Installthe update rollup package on the following server infrastructure.

    Note Management server or servers can be updated by using eitherthe msp or simplified management server patching user interface.
     
    • Audit Collection Services
    • Web console server role computers
    • Gateway
    • Operations console role computers
    • Reporting
Note Youmay encounter an error at the Management Pack import step during the managementserver update. To mitigate this error, do either of the following:
    • Install .NET Framework 3.5, and then rerun themanagement server update.
    • Import the management packs manually.
        2. Applyagent updates.
        3. UpdateUnix and Linux MPs and agents.

UNIX and Linux management pack update

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

  1. ApplyUpdate Rollup 2 to your System Center Operations Manager 2019 environment.
  2. Downloadthe updated management packs for System Center 2019 from the following Microsoftwebsite:

    SystemCenter 2019 Management Pack for UNIX and Linux Operating Systems 

  3. Install themanagement pack update package to extract the management pack files.
  4. Import the updatedmanagement pack for each version of Linux or UNIX that you are monitoring inyour environment.
  5. Upgrade each agentto the latest version by using the Update-SCXAgent Windows PowerShellcmdlet or the UNIX/Linux Agent Upgrade Wizard in the Administrationpane of the Operations Console.

Uninstallation information 


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

Note The <PatchCodeGuid> placeholder represents one ofthe following GUIDs.

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

Component 

RTMGUID 

PatchGUId 

Server 

{5016D727-313F-451D-9990-4DB326D00F06} 

{856E4D3A-F2BE-4203-8FE8-C436E065858B} 

Webconsole 

{D80F1A1B-200C-421C-B876-F440A7BDAA67} 

{1FC7492B-5B73-4BE0-AEFC-84E51EFAC067} 

Reporting 

{10137A63-5AE9-4B40-8BF2-DBAE7B596359} 

{3BA68042-EFB3-4CA5-808D-A367A539B308} 

Console 

{88D7DF38-306E-4195-8C1A-C19A4E35C728} 

{0947D6C2-D745-47F8-8706-C13DCA329CD9} 

Agent 

{CEB9E45B-2152-4C10-A022-0825B53B632F} 

{93BA6D5D-4FBA-4161-94B2-4D5DAC95347D} 

Gateway 

{4ED3E2E8-E655-4F9C-8A95-10ADD6700181} 

{934FF8AF-81FB-4A8D-83F1-CDFC0520AB4E} 

Files updated in this update rollup


The following management packs are included in the Servercomponent at:

%SystemDrive%\Program Files\Microsoft SystemCenter\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 inthis rollup:

File Name

Version

File size

MOMAgentInstaller.exe

10.19.10407.0

401KB

MOMAgentInstallerPS.dll

10.19.10407.0

95.9KB

Microsoft.Mom.Common.dll

10.19.10407.0

228KB

MOMAgentManagement.dll

10.19.10407.0

266KB

Microsoft.SystemCenter.DbUpdateHelper.dll

10.19.10407.0

18.9KB

sm-auto-discovery.dll

10.19.10407.0

4.27MB

sm-discovery.dll

10.19.10407.0

2.40MB

sm-snmp.dll

10.19.10153.0

616KB

AgentConfigManager.dll

10.19.10153.0

134KB

HealthService.dll

10.19.10153.0

3.03MB

HealthServiceRuntime.dll

10.19.10153.0

289KB

MOMWsManModules.dll

10.19.10153.0

224KB

MOMModules.dll

10.19.10153.0

2.34MB

AgentControlPanel.exe

10.19.10153.0

1.21MB

HealthService.exe

10.19.10153.0

26.4KB

PerfCounterMonitor.dll

10.19.10153.0

1.05MB

sm-snmp.dll

10.19.10153.0

616KB

AgentConfigManager.dll

10.19.10153.0

134KB

HealthService.dll

10.19.10153.0

3.03MB

HealthServiceRuntime.dll

10.19.10153.0

289KB

MOMWsManModules.dll

10.19.10153.0

224KB

MOMModules.dll

10.19.10153.0

2.34MB

AgentControlPanel.exe

10.19.10153.0

1.21MB

HealthService.exe

10.19.10153.0

26.4KB

Microsoft.EnterpriseManagement.UI.Administration.dll

10.19.10407.0

4.43MB

Microsoft.Mom.UI.Wrappers.dll

10.19.10407.0

91.9KB

Microsoft.SystemCenter.OperationsManagerV10.Commands.dll

10.19.10407.0

668KB

Microsoft.Web.Infrastructure.dll

1.0.20105.407

44.3KB

Microsoft.EnterpriseManagement.Runtime.dll

10.19.10407.0

76.9KB

ARViewer.dll

10.19.10407.0

911KB

Microsoft.EnterpriseManagement.DataAccessLayer.dll

10.19.10407.0

2.44MB

SEMCore.dll

10.19.10407.0

0.99MB

ARCore.dll

10.19.10407.0

694 KB

Microsoft.EnterpriseManagement.UI.Administration.resources.dll

10.19.10407.0

2.48MB

Microsoft.EnterpriseManagement.DataAccessService.core.dll

10.19.10407.0

687KB

Microsoft.EnterpriseManagement.DataAccessLayer.QueryCache.dll

10.19.10407.0

2.18MB

Microsoft.EnterpriseManagement.DataAccessLayer.dll

10.19.10407.0

2.44MB

Microsoft.EnterpriseManagement.HealthService.Modules.DataWarehouse.dll

10.19.10407.0

1.05MB

Microsoft.EnterpriseManagement.DataWarehouse.DataAccess.dll

10.19.10407.0

223KB

Microsoft.EnterpriseManagement.Core.dll

10.19.1035.100

3.94MB

Microsoft.EnterpriseManagement.DataAccessService.OperationsManager.dll

10.19.10407.0

576KB

Microsoft.Mom.UI.Components.dll

10.19.10407.0

5.70 MB

Microsoft.Mom.UI.Components.resources.dll

10.19.10407.0

2.07MB

Microsoft.SystemCenter.CrossPlatform.ClientLibrary.MPAbstractions.dll

10.19.1122.0

87.3KB

Microsoft.SystemCenter.CrossPlatform.ClientLibrary.ClientTasks.dll

10.19.1122.0

53.8KB

Microsoft.SystemCenter.CrossPlatform.ClientLibrary.WorkflowActivities.dll

10.19.1122.0

47.3KB

Microsoft.SystemCenter.Instrumentation.dll

10.19.1035.83

52.4KB

InstrumentationConfig.xml

 

1.01KB

Microsoft.ApplicationInsights.dll

2.12.0.21496

377KB

Microsoft.SystemCenter.Telemetry.EventData.dll

10.19.10407.0

43.9KB

Microsoft.EnterpriseManagement.UI.Console.Common.dll

10.19.10407.0

779KB

Microsoft.EnterpriseManagement.Monitoring.Console.exe

10.19.10407.0

3.93MB

Microsoft.EnterpriseManagement.OperationsManager.MonitoringViews.dll

10.19.10407.0

1.77MB

Microsoft.EnterpriseManagement.Monitoring.Console.resources.dll

10.19.10407.0

397KB

Microsoft.Mom.Sdk.ServiceHost.exe

10.19.10407.0

46.9KB

Microsoft.EnterpriseManagement.OperationsManager.dll

10.19.10407.0

1.05MB

Microsoft.EnterpriseManagement.Reporting.Code.dll

10.19.10407.0

44.9KB

Microsoft.MOM.UI.Common.dll

10.19.10407.0

2.21MB

Microsoft.EnterpriseManagement.OMDataService.dll

10.19.10407.0

543KB

OMVersion.dll

10.19.10407.0

10.9KB


Updated SQLfiles
 

File Name

File Size

UR_DataWarehouse.sql

392KB

update_rollup_mom_db.sql

357KB

Release Notes


For more information, see theRelease Notes for this release