Tag Archives: #2016

SCOM CB: Updated MP Active Directory Domain Services v10.0.2.2

An updated MP has been released for ADDS get it here

New in this version:

  • Updated the RODC Group to include OS version
  • Updated NTService monitors to allow for overriding when the service is not set to automatic start
  • Fixed AD Topology discovery when the SCOM server and action account are in a child domain

SCOM 1807: Updated Management Pack for Microsoft Azure v1.5.20.18

The Azure management pack has had an update get it here

This updated contains primarily new features.

Updates and features

  • Added the “Audience URI” field in the Endpoints Configuration for the Azure Subscriptions Wizard
  • Implemented monitoring of Non-classic storage account
  • Implemented monitoring of Application gateway
  • Fixed issue of obtaining data with Azure Data Factory
  • Implemented monitoring of Azure Data Factory
  • Metric collection for Classic storage account is not supported
  • Implemented monitoring of Service Bus in SPN mode
  • Implemented monitoring  support for Gateway Server

SCOM 1801: Updated management packs for Open Source Software OSS v7.7.1129.0

The updated Management packs for OSS MySQL and Apache can be found here.

The Management Packs for Open Source Software enable discovering, monitoring, and managing MySQL Server and Apache HTTP Server. They provide reactive and proactive monitoring of MySQL Server and Apache HTTP Server running on Linux operating systems. The monitoring provided by the Open Source Software management packs includes availability and configuration monitoring, performance data collection, and default thresholds. In addition to health monitoring capabilities, the Open Source Software management packs include reports, diagnostics, tasks, and views that enable near real-time diagnosis and resolution of detected issues.


The case of the missing override checkbox

One of my customers contacted me regarding a rather strange situation, whenever they try to apply an override they are unable to because the checkbox is missing.

As it turns out this the solution while unusual is quite simple, the screen resolution on their server is too high. In this case, for this particular version of Operations Manager the resolution was higher than 1600×900.

Once we dropped the resolution to 1600×900 the check boxes reappeared.

SCOM 1801: Updates management packs for SQL Server v7.0.7.0

New versions of the SQL MPs have been released you can get them using the links below:

SQL Server

SQL Server 2017+ –  here
SQL Server 2016here
SQL Server 2014here
SQL Server 2008-2012here


SSAS 2016 – here
SSAS 2014 – here
SSAS 2012 – here
SSAS 2008 – here

SSRS (Native Mode)

SSRS 2016 – here
SSRS 2014 – here
SSRS 2012 – here
SSRS 2008 – here

SQL Server 2017+ MP New Features and Fixes

  • Implemented an ability to monitor SQL Server Cluster instances locally; formerly, it was possible only in Agentless and Mixed modes
  • Added the SSIS monitoring
  • Added the “Exclude List” property in DB Engine Discovery in order to filter instances, which are not subject to monitoring
  • Added the “Exclude List” property in DB Discovery in order to filter databases, which are not subject to monitoring
  • Implemented a feature: both “Exclude List” properties support usage of the asterisk character to make the filter more flexible; e.g. “*temp” is used to exclude instances/databases ending with “temp” and having anything in the beginning
  • Added the “Computers” view
  • Added the “ClusterName” property to the AG class and updated AG alerts in order to display the property within
  • Updated the “SP Compliance” monitor in order to support the Modern Servicing Model for SQL Server: the monitor will check build number instead of Service Pack number
  • Updated the “SPN Status” monitor so that it requires only a single SPN record when only TCP/IP is enabled and the instance is the default one
  • Updated the “Database Backup Status” monitor: it is disabled by default now
  • Updated the DB Space monitors so that their alert descriptions include the actual value of space available
  • Updated the “Configuration Security” section in the guide
  • Fixed issue: The “Database Health Policy” monitor ignores the “Critical” state (on Windows only)
  • Fixed issue: The “Alert severity” property of the “DB File Free Space Left” monitor has incorrect Default Value
  • Fixed issue: The “DB Filegroup Fx Container” rollup monitor has an alert parameter with a wrong value within
  • Fixed issue: “Resource Pool Memory consumption” monitor may not change its state to “Critical” for the “default” resource pool
  • Fixed issue: “Number of Samples” parameter of “Resource Pool Memory consumption” alert displays incorrect data
  • Fixed issue: Missed image resources in the SQL Server 2017+ Core Library
  • Fixed issue: “The agent is suspect. No response within last minutes” alerting rule does not catch appropriate events due to the wrong source

SQL Server 2014-2016 MP New Features and Fixes

  • Updated alert severity in some monitors
  • Updated the display strings
  • Updated the “Max worker thread count” data source of the corresponding monitor and performance rule
  • Fixed issue: In some environments, DB Space workflows fail when a secondary database is non-readable
  • Fixed issue: The “Transaction Log Free Space (%)” monitor does not work
  • Fixed issue: The “The agent is suspect. No response within last minutes” alerting rule does not catch appropriate events due to a wrong source

SQL Server 2008-2012 MP New Features and Fixes

  • Fixed issue: In some environments, DB Space workflows fail when a secondary database is non-readable
  • Fixed issue: The “The agent is suspect. No response within last minutes” alerting rule does not catch appropriate events due to a wrong source
  • Fixed issue: The “DB File Space” monitor in the SQL 2008 management pack throws error events due to the unnecessary $ character in its alert configuration
  • Updated the “Max worker thread count” data source of the corresponding monitor and performance rule
  • Fixed issue: The “Transaction Log Free Space (%)” monitor does not work

SSAS 2008-2016 MP New Features and Fixes

  • Updated the Visualization Library

SSRS 2008-2016 MP New Features and Fixes

  • Added support for cases when a connection string of the SSRS instance to the SSRS Database is not in the “MachineName\InstanceName” format; e.g., “<IP Address>, <Port Number>” or “(local)”, etc. Such connection strings are fully supported for default SQL Server instances hosting the SSRS Database. If the instance is named, workflows targeted at the SSRS Instance object work properly, but those targeted at the Deployment object cannot work, as there is no possibility to learn the FQDN of the server.
  • Updated the Deployment Seed discovery so that it does not check if the SQL Server instance hosting the SSRS Database is running
  • Updated the Visualization Library

SCOM 1801: Updated MP for Windows Server 2016 and 1709 Plus v10.0.21.0

An updated management pack has been released for Windows Server 2016 and 1709 Plus get it here

My colleague Kevin Holman has written a fantastic article on the new features in this management pack available here.

The article includes a word of caution regarding the new Port and Process monitoring MP as it can overwhelm your Data Warehouse if you turn this on indiscriminately.

SCOM 1801: Microsoft Advanced Threat Analytics Management Pack updated for 1.9

The ATA management pack has been updated to include support for ATA 1.9 get it here

What is Advanced Threat Analytics?

Advanced Threat Analytics (ATA) is an on-premises platform that helps protect your enterprise from multiple types of advanced targeted cyber attacks and insider threats.

Image result for microsoft advanced threat analytics

SCOM 2016: UR5 Released

Update Rollup 5 for SCOM 2016 has been released.

As usual you can get it from the catalog here or through windows update.

all in all this looks like a good update and solves a few persistent issues form previous versions.

Updates and Fixes

  • SCOM console and Service Manager console for PowerShell modules can now coexist on the same server.Note Both SCOM Update Rollup 5 (this update) and Service Manager Update Rollup 5 (update KB 4093685) must be installed to resolve this issue.
  • Active Directory Integration rules are not visible or editable in an upgraded 2016 Management Group. This prevents the ongoing management of Active Directory integration assignment in the upgraded Management Group.
  • When the UNIX host name on the server is in lowercase, the OS and MonitoredBy information is displayed incorrectly in the Unix/Linux Computers view.
  • Active Directory integrated agents do not display correct failover server information.
  • Performance views in the web console do not persist the selection of counters after web console restart or refresh.
  • The PowerShell cmdlet Get-SCXAgent fails with error “This cmdlet requires PowerShell version 3.0 or greater.”
  • During the upgrade from SCOM 2016 to SCOM 1801, if the reporting server is installed on a server other than the management server, the upgrade fails. Additionally, you receive the error message, “The management server to which this component reports has not been upgraded.”
  • If a group name has been changed through the operations console, the Get-SCOMGroup cmdlet does not retrieve the group data that includes the changed group name.
  • Error HTTP 500 occurs when you access Diagram view through the web console.
  • When you download a Linux management pack after you upgrade to SCOM 2016, the error “OpsMgr Management Configuration Service failed to process configuration request (Xml configuration file or management pack request)” occurs.
  • The SQLCommand Timeout property is exposed so that it can be dynamically adjusted by users to manage random and expected influx of data scenarios.
  • The MonitoringHost process crashes and returns the exception “System.OverflowException: Value was either too large or too small for an Int32.”
  • When company knowledge is edited by using the Japanese version of Microsoft Office through the SCOM console, the error (translated in 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” occurs.
  • Accessing Silverlight dashboards displays the “Web Console Configuration Required” message because of a certificate issue.
  • Microsoft.SystemCenter.ManagementPack.Recommendations causes errors to be logged on instances of Microsoft SQL Server that have case-sensitive collations.
  • Deep monitoring displays error “Discovery_Not_Found” if the installation of JBoss application server is customized.
  • Adds support for the Lancer driver on IBM Power 8 Servers that use AIX.
  • The ComputerOptInCompatibleMonitor monitor is disabled in the Microsoft.SystemCenter.Advisor.Internal management pack. This monitor is no longer valid.