Update Rollup 1 for System Center 2022 Operations Manager

Introduction

This article describes the new features and issues that are fixed in System Center Operations Manager 2022 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 What's New in System Center Operations Manager 2022 Update Rollup 1.

Issues that are fixed

Operations Manager 2022 Update Rollup 1 includes fixes for the following issues:

Operations Console  

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

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

• When setting Maintenance Mode via PowerShell, the Availability Reports were not reflecting correct information.

• The Summary page of the Notification Subscription Wizard was empty if any Alert Criteria was configured.

• For some non-US languages (depending on data format), the Patch information was either missing or not being updated.

• Trying to update a Management Pack from the Console from the Update Catalog after another one was updated would throw a connection error.

• Running custom imported (directly via SSRS Web Portal) Reports would fail to get executed in the SCOM Console with error NullReferenceException.

• The OpsMgrDBPercentFreeSpaceMonitor monitor was not reporting the free space correctly in all configuration scenarios. The used script has been moved from VBS to PowerShell and now reports the OpsDB free space correctly.

Web Console

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

• Fixed several Web Console Security Vulnerabilities. Note that the Web.config files of both HTMLDashboard and MonitoringView WebApps will be replaced, so any changes done to settings inside of these will have to be remade.

Other Fixes:

• When trying to setup Log Analytics connection a timeout would sometimes get an error 200.

• When for some reason a badly formatted XML would be encountered, the contents of this XML would be saved to a file called "Bad.xml" inside of the System32 directory. This functionality has been disabled, to enable it (for debugging purposes) this registry key should be created and set to the value of 1.

• Crashes of MonitoringHost.exe instances which are related to SNMP Discovery.

• Added a configurable Timeout setting in the registry to control the SDK Client Task timeout. This is now configurable via creating this registry key (this needs to be created and set on all existing Management Servers):
  
  [HKLM\SOFTWARE\Microsoft\System Center\2010\Common\SDK Service] - SDK Task Timeout Seconds DWORD type and should have the value set in seconds (default is 1800 seconds).

• Teams integration failing due to incorrectly named binary file.

Performance improvements:

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

Unix/Linux/Network monitoring fixes and changes:

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

• Privilege escalation security issue related to Kerberos setup.

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

• Fixed the random omiengine crash issue.

• A memory leak in the MonitoringHost process monitoring Unix/Linux servers.

• Randomly adding spurious characters in the commands during script-based monitoring in Solaris.

Previous fixes

In addition to these issues, all the issues that are fixed in SCOM 2019 UR4 are also fixed in SCOM 2022.

Known Issues

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

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

Note: Before applying Management Server patch KB5020318-amd64-Server.msp, navigate to %SystemDrive%\Program Files\Microsoft System Center\Operations Manager\Server\AgentManagement\amd64 and delete the files named KB3117586-amd64-Agent.msp and KB9999999-amd64-Agent.msp. Do this step on each Management Server.

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 2022 UR1

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 2022, 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 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 1 to your System Center Operations Manager 2022 environment.

2. Download the updated management packs for System Center 2022 from the following Microsoft website: 
   System Center 2022 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.Library.mp

• Microsoft.SystemCenter.OperationsManager.Internal.mp

• Microsoft.SystemCenter.2007.mp

• Microsoft.SystemCenter.Advisor.mpb

Files updated in this rollup

Updated SQL files