Microsoft has released UR6 for SCOM 2019 this week.
The article is found here Update Rollup 6 for System Center 2019 Operations Manager – Microsoft Support on the System Center Blog. This will bring the KB5035285 version to 10.19.10649.0 for the server and 10.19.10253.0 for the agents.
This time we see a number of fixes, improvements, additions for Linux monitoring (newer distros supported).
UR6 msp files: Download the Operations Manager update package now.
UR6 exe file: Catalog location
Linux/UNIX MP: Download System Center 2019 Management Pack for UNIX and Linux Operating Systems from Official Microsoft Download Center
What does this update contain? I will copy some text from Microsoft’s site mentioned near the top of this post below:
Issues that are fixed
Operations Manager 2019 Update Rollup 6 includes fixes for the following issues:
- Fixed an issue which reported High CPU in MOMPerfSnapshotHelper due to shutdown in aspnet_perf.dll by TerminateProcess instead of normal return.
- Fixed 13 Reports displaying GB (Chinese) characters incorrectly.
- Fixed GB characters from GB18030-2022 version which were not displaying in Alert Description field on Create Monitor/rule Wizard.
Security Enhancements
- Addressed multiple security vulnerabilities and enhancements w.r.t Linux agent.
- Added support for compiler-mitigated Linux Agent.
- Disabled HTTP tracing to mitigate potential misuse.
Unix/Linux/Network monitoring fixes and changes
- Added support for new Linux distributions including Alma 9, Rocky 9, and Debian 12.
- Resolved an issue with Apache MP where the Apache product version was not correctly returned on SLES 15/OpenSUSE 15.
- Addressed Linux agent installation problems when SeLinux is disabled on the agent machine.
- Fixed Linux agent installation issues on Solaris 10X86 caused by outdated references to OpenSSL.
- Resolved a query failure issue due to the filter size exceeding 64 symbols.
- Fixed leap day issues identified by CodeQL analysis.
- Resolved a memory leak problem in the Linux agent, which previously led to unresponsiveness.
- Fixed an issue causing OMIAgent to use 100% CPU.
- Addressed a problem where timeouts were not functioning correctly when the elevation type was set to Sudo.
- Fixed the problem of extended OMI uninstallation.
I will be updating again and will also reflect the changes in the TopQore SCOM Health Check.
Bob Cornelissen