Category Archives: Update Rollup

SCOM 2019: Update Rollup 3 released!

The much anticipated UR3 for SCOM 2019 is out as usual available through windows update or via the packages here

This is a solid update with many useful fixes and includes the security hotfix released last month for previous versions of SCOM 2019

Improvements and issues that are fixed

Operations Console fixes and changes

  • SCOM UI scaling issues for high resolution displays have been fixed to work seamlessly.
  • Some IPv4 resources were being discovered as IPv6 in a cluster where both resources co-existed. This logic has been fixed to ensure IPv4 resources are no longer discovered as IPv6.
  • The UR2 setup stalling issue at the “Removing backup files” stage has been fixed. The task wait time threshold has been set to 30 mins. It is also recommended to have Service Broker always enabled for smooth functioning of Operations Manager.
  • The assumption of having provider element to be the first reference in the connection string has been removed in the OleDB module.
  • Fixed the combo box related text issue regarding the domain of a new RunAs account getting incorrectly changed.This issue was arising when creating a new RunAs Account in the SCOM console for an account that belongs to an untrusted domain, the fix ensures that the domain of the newly created RunAs Account should remain the one initially specified during the account creation.
  • Fixed the “invalid class” error that was occurring when adding a subscriber with user details having more than 1024 attributes.
  • Daily aggregation of reports now takes date and time into consideration to ensure time-period calculation is accurate.
  • Fixed the monitoring agent related issue around formatted strings, these are now read from the provider dlls to show a localized string.
  • Fix has been provided for when the monitor erroneously turns critical due to the URL module incorrectly parsing the charset header value.

Web Console fixes and changes

  • The security issue regarding reverse tab nabbing has been fixed in the operations manager web console.
  • Fixed the filter issue that occurred when state view was created in “My Workspace” in the web console.
  • Global search option for Metrics section of Performance Widget in the Web Console has been fixed.

Other Fixes:

  • Updating Management Groups with a shared Data Warehouse to UR2 sometimes lead to issues with reports deployment. This is now fixed by restricting Installation of sealed MP with same version in the Data Warehouse.
  • Migrate SSL Admin certificates to Microsoft PKI – Pinning Thread for Agents
  • Fixed the issue that was occurring when the UR2 SQL patch is executed again on a previously patched database.
  • The deadlock issues arising when SCOM agents are put into maintenance mode using SCOM API with parallelism have been resolved by adding indexes and updating the SQL queries.
  • Performance improvement of the DB function fn_ManagedEntityLifetimeDependency.
  • Updated the scoping logic used in some State View queries and Console Cache Refresh queries for performance improvement.
  • Added “Recompile” flag for sprocs “p_SelectForTypeCache” and “p_SelectForNewTypeCache” for SCOM perf improvement.

Unix/Linux/Network monitoring fixes and changes:

  • The issue with SSH call failure leading to memory corruption has been fixed .
  • Fixed a thread race condition that was leading to Linux script based monitoring fails due to child process that failed to start.
  • Fixed an infinite loop condition, which was leading to the 100% CPU related issue.
  • The issue of the MonitoringHost.exe process crashing on the Management Servers that run the Unix/Linux workflows has been fixed.
  • Fixed the memory leak inside of the WsMan modules when UseMIAPI is enabled with workflows that have SplitItems set to TRUE for the EnumerateAsWA WriteAction.

SCOM 2016: UR10 released!

Update rollup 10 for SCOM is out you can get it here.

This is a reasonably solid update with a few fixes for some long outstanding issues.

Improvements and issues that are fixed


  • Management Pack Import is now compatible for SCOM 2007 –> SCOM 2016 Upgrade version when upgraded directly or Indirectly.
  • The exception which blocked further progress when the user attempted to configure web application availability monitoring has been fixed.
  • The security issue regarding reverse tabnabbing has been fixed in the operations manager web console.
  • Fixed the Cross-site Scripting (XSS) related security issue in the operations manager web console.
  • The cmdlet Export-SCOMEffectiveMonitoringConfiguration has been fixed to give a correct summary of the applicable monitors, rules and overrides on an object.
  • Quarterly report end date will be shown correctly for the first quarter when the “From” field is selected as “First day of previous quarter” and “To” field is selected as “Last day of previous quarter”.
  • Reports have been fixed to not show objects which have been deleted before the selected start time.
  • VB scripts for partition and grooming, calculate operations manager free space and detecting duplicate agent will now run without failure even if SNAC or MSOLEDBSQL are not installed.
  • The issue regarding the TLS 1.2 compatibility in the OleDB module has been fixed. It is no longer mandatory for the provider element to be the first reference in the connection string.
  • Fix has been provided for when the monitor erroneously turned critical due to the URL module incorrectly parsing the charset header value.
  • The  .NET API  issue regarding scheduling reports via the schedule management wizard has now been fixed.  
  • Performance improvement: Added “Recompile” hint to the stored procedures “p_SelectForTypeCache” and “p_SelectForNewTypeCache” that run frequently on SCOM DB.

SCOM 2019: Update Rollup 2 Released!

UR 2 for SCOM 2019 is out and it’s a big one get it here

This is a fantastic update with the long awaited MP change tracking feature and tons of fixes.

What’s new?

  • Change tracking for management packs
  • Improvements in scheduled maintenance mode
  • Favorite reports in web console
  • Support for folders in monitoring view of web console
  • Support for CentOS 8

What’s fixed?

This is a big update and the list of fixes is long as this includes not only the recent SCOM hotfix but also many other useful changes see here for the full list.

SCOM 2016: UR9 released!

The latest Update Rollup for SCOM 2016 is out, you can get it here

A decent update fixing a couple of issues that have been around for a while. As always test before applying to your production environments.

What’s new and fixed?


  • Fixed: On Windows Computer View of SCOM Console, Queries are optimized for better performance.
  • Fixed: We have updated SPROC to handle Alert Source Path Names which are greater than 512 in length. It was a mismatch where the table which 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.
  • Fixed: Made changes to the IP address parameter to support both IPv4 and IPv6 windows cluster.
  • Fixed: Fixed the issue with conversion of data smaller than 0.01 which was generated by Rule or Monitor. The data was transformed to a wrong (big) value on systems with OS locale language which has comma (“,”) instead of dot (“.”) as decimal format.
  • Fixed: Fixed the schedule reports through the Schedule Management Wizard in APM AppAdvisor. Previously, it was failing with XML Malformed exception.
  • Fixed: In a scenario where SCOM monitors 100s of virtual machines hosted on a single Hyper-v server; every hour the MonitoringHost.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\MonitoringHost\MemoryTrimmingEnable – 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)

  • Fixed: Downtime duration will be calculated correctly for non-US time format in Downtime Report.
  • Fixed: fn_MPVersionDependentId creates an ID for each installed MP. The ID is a SHA1 hash of string “MPName, Version, Schema”. When the “Schema” part is omitted, it generates different hash which doesn’t match with the expected value. In the fix, “Schema=2” part is re-added in fn_MPVersionDependentId.
  • Fixed: We have made sure that correct end date for Availability, Health and Performance Details are shown in reports
  • Enabled support for MSOLEDBSQL driver so that users may move from SQL Native Client.

SCOM 2019: UR1 has been released!

The much anticipated release of UR1 for SCOM 2019 is here and you can get it from the update catalog.

There’s quite a bit to unpack here so lets have a look

The big changes are of course support for gMSA which I for one have been looking forward to for a while. The security benefits are obvious and I can say while it does work well be aware that it is complex to implement so read those instructions thoroughly.

The one click upgrade experience is also a step in the right direction making things much simpler for the SCOM admin, just note it only includes the server update so you will still need to upgrade your console, reporting etc manually.

See below for a complete list of all the changes

Improvements and issues that are fixed


Web Console 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. 
  • SNMP GET or SNMP WALK resulted monitoring host to crash when the network object ID is 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

 Admin Console 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

 In addition to these, all the issues fixed in SCOM 2016 UR8 and prior UR for SCOM 2016 are also fixed in SCOM 2019 UR1. 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 port details 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 CPU Processes’ when using Windows Management Infrastructure (MI) APIs.
  • Fixed an issue that caused the corruption of /etc/login.cfg file on AIX 7 machines during install/upgrade of the agent.
  • AIX Agent is now transitioned to 64-bit package to accommodate more stack and heap space if needed to avoid any stack/heap overflow which occasionally leads to heartbeat failure.
  • Free memory calculation accommodated appropriately on RHEL-7 platform.

SCOM: News from Ignite

This year at Ignite SCOM had it’s own dedicated session which is great to see. Here is a summary of the new upcoming features in UR1.

Version Agnostic Management Packs
Storage Spaces Direct (S2D) MP
RHEL 8 Support
One click patching experience
Support for gMSA
Relability and Performance Improvemennts for Linux Agent
Common Management Pack for Linux
Resource Group monitoring in Azure MP
Azure MP Web Console Dashboards

The ones I’m most looking forward to are of course the support for gMSA, with security being so critical in today’s IT real-estate this features adds an additional layer of peace of mind to your SCOM monitoring.

The one click patching experience is also a nice quality of life improvement, I had the privilege to see this in action and I like the direction this is going.

More agnostic management packs are also on the way which will simplify administration of products the same way we’ve seen them improve the SQL monitoring experience.

What do you think of this update? Leave a comment or if you have an idea head over to the SCOM Uservoice https://systemcenterom.uservoice.com/forums/293064-general-operations-manager-feedback and let the product group know.

SCOM 2016: UR 8 is now available!

Update Rollup 8 for SCOM 2016 is now available, as usual you can get it through windows update or via the download catalogue here

Improvements and fixes


  • Fixed: 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)

  • Fixed: 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.
  • Fixed: 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.
  • Fixed: 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.
  • Fixed: CPU Spike issues because of workflows running on all agents at the same time is addressed through script optimization and removing the sync time.
  • Fixed: If the registry key under “Computer\HKey_Local_Machine\Software\Microsoft\Microsoft Operations Manager\3.0\Setup\UseMIApi” is set and a Unix/Linux Script task without a parameter is executed then this task fails. 
  • 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.

SCOM 2016: UR7 is Live

Update rollup 7 for SCOM is now available as usual you can get it through windows update or here

How to guide – here note the known issues and slight change to getting started.

A decent update with quite a few fixes listed below:

Improvements and issues that are fixed


  • Fixed: Cannot use SQLOleDB.dll to probe databases like Oracle/MySQL.
  • Improved the performance of SCOM console in listing the groups.
  • Operations Manager grooms out the alert history only on an alert closure.
  • Agents by Health State report shows duplicate agent names.
  • Users of a scoped group are not able to use the Console.
  • Fixed an issue that prevented addition of a group in the Storage Spaces Direct 2016 management pack dashboard.
  • SCOM Network Device Re-Discovery now probes for SNMP V3 devices too.
  • Fixed re-registering for SNMP Traps in the Proxy Management Server.
  • Windows Computer Property “NetbiosDomainName” is not discovered properly.
  • SCOM console crashes while trying to connect to Azure Log Analytics and Azure Monitor.
  • Linux agent is not able to get the correct version and port details 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 CPU Processes’ when using Windows Management Infrastructure (MI) APIs.
  • XPlat agent now supports monitoring of SUSE-11 SP4 platform with Security Module installed on it for TLS 1.2 compliance.
  • Fixed an issue that caused the corruption of /etc/login.cfg file on AIX 7 machines during install/upgrade of the agent.
  • AIX Agent is now transitioned to 64-bit package to accommodate more stack and heap space if needed to avoid any stack/heap overflow which occasionally leads to heartbeat failure.
  • Free memory calculation accommodated appropriately on RHEL-7 platform.

SCOM 2016: Update Rollup 6 released

A brief overview of the recently released UR6 for SCOM 2016 – get it here

Updates and Fixes

  • Application pool crashes and SharePoint application crashes because of APM agent and the profiler are now fixed. These occurred because the profiler was always on. This issue is fixed by disabling the profiler by default and enabling it only when APM is configured.Note If you’re using APM, restart IIS after you deploy the patches.
  • Improved logging to display error messages and suggest that you check performance counters when PdhExpandWildCardPath fails.
  • Fixed: Session Events tab in Application Diagnostics web console doesn’t display any data.
  • Fixed: Scheduled Maintenance Mode doesn’t work in an availability group that uses SQL Always-On configuration. In case of a failover to a secondary node, the Maintenance Mode Schedules that are created on the primary node don’t run. This has now been fixed. For details, see the “Enabling Schedule Maintenance Mode with SQL Always ON” section.
  • Updated fix: The Get-SCOMGroup cmdlet is slow to query large (more than 2,000) groups. A previous fix has been improved for faster querying of any number of groups.
  • Fixed: Users could not edit the Maintenance Schedule in the SCOM console if all the objects were removed. The schedule can now be edited. However, it cannot be saved unless it contains at least one object.
  • Fixed: SCX cannot connect with Linux machine if the KEX algorithms are configured as any of the following: ecdh-sha2-nistp256diffie-hellman-group-exchange-sha256, or diffie-hellman-group14-sha256.
  • Fixed: Using MI APIs causes MonitoringHost.exe to crash. This event is logged in the Application log, but no crash events are reported in the Operations Manager event log. After this fix, MonitoringHost doesn’t crash even if the useMIAPI registry key is enabled.
  • OMS (now Azure Log Analytics) connection onboarding wizard isupdated to communicate with the new APIs. This is because the OMS services were moved to the Azure Portal (link), and also because of the planned retirement of the OMS portal. This change will not affect any existing connection to OMS. However, for new connections or to reconfigure existing connections, the relevant management packs that are bundled together with this update rollup must be imported.
  • This update rollup creates a new “omi” user (system account).
  • XPlat support matrix changes:
    • SLES 10 is not supported.
    • CentOS 5 is not supported.
    • AIX 6.x is not supported.

SCOM 1807: What you need to know and yes it’s available!

The first update for System Center Operations Manager has just been released, what do you need to know about SCOM 1807?

Updates work the same way as the Update Rollups you are used to you can use windows update or get the packages manually here

First what’s fixed?

Issues that are fixed and improvements that are included


  • Fixes an issue that sometimes cause the Performance widget in the web console to throw an ArgumentExceptionmessage.
  • Fixes an issue that prevented the Alert view URL in the notification channel from to pointing to the new drill-down Alert page.
  • Fixes an issue that causes the web console to throw an ArgumentException message when the state widget is added to a dashboard or scoped to a specific group.
  • Improvement to the web console so that is now supports nondefault ports.
  • Fixes an issue that causes the pseudo file system to be enumerated.
  • Fixes an issue that caused the DNS 2016 Management Pack to throw false alerts for “DNS unused Zone Detected.”
  • Fixes an issue that caused the MySQL version to be listed as “for,” “on,” or NULL in Detail view for some platforms.
  • Improvement that enables Monitoring Solaris 10 Agents (x86) to provide heartbeat alerts and configuration errors about the SSL certificate.
  • Fixes an issue that prevented the Operations Manager console, the Service Manager console and PowerShell modules to coexist on the same server.Note Both Operations Manager and Service Manager must be upgraded to version 1807 to resolve this issue.
  • Fixes an issue in which Active Directory Integration rules were not visible or editable in an upgraded 2016 Management Group. This issue prevented the ongoing management of Active Directory integration assignment in the upgraded Management Group.
  • Fixes an issue that caused the system and MonitoredBy information to be displayed incorrectly in the Unix/Linux Computers view when the UNIX host name on the server is lowercase.
  • Fixes an issue that caused Active Directory integrated agents not to display correct failover server information.
  • Fixes an issue in Performance views in the web console that caused the selection of counters not to persist after a web console restart or refresh.
  • Fixes an issue in which the PowerShell cmdlet Get-SCXAgent fails and returns a “This cmdlet requires PowerShell version 3.0 or greater” error.
  • Fixes an issue in which a group name is changed through the operations console, the Get-SCOMGroup cmdlet does not retrieve the group data that includes the changed group name.
  • Fixes an issue that causes error HTTP 500 to occur when you access Diagram view through the web console.
  • Improvement in which the SQLCommand Timeout property is exposed so that it can be dynamically adjusted by users to manage random and expected influx of data scenarios.
  • Fixes an issue that caused the MonitoringHost process to crash and throw the exception “System.OverflowException: Value was either too large or too small for an Int32.”
  • Fixes an issue when company knowledge is edited by using the Japanese version of Microsoft Office through the Operations Manager console, you receive the following error (translated into English): “Failed to launch Microsoft Word. Please make sure Microsoft Word is installed. Here is the error message: Item with specified name does not exist.”
  • Fixes an issue that causes Microsoft.SystemCenter.ManagementPack.Recommendations to log errors on instances of Microsoft SQL Server that have case-sensitive collations.

And then what’s new?

  • Improvements to the HTML5 webconeole experience including:
    • Addition of a Powershell widget
    • Create HTML5 dashboards in MyWorkspace.
    • View HTML5 Network Node and Network Interface dashboards.
    • Create maintenance schedules from the HTML5 web console.
  • You can now enable or disable APM when pushing the agent from the console.
  • The Linux agent now supports Log rotation monitoring
  • Support for SQL 2017, there is a catch however you will need to update your existing SCOM to 1807 before you can upgrade your SQL to 2017