Tag Archives: #2016

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.

SCOM 1801: Updated SQL Server Management Packs v7.0.4.0

New versions of the SQL server management packs are available at the following locations:

SQL Server 2008/1012 – here
SQL Server 2014  – here
SQL Server 2016 – here

New in 7.0.4.0

SQL Server 2008/2012/2014/2016

  • Updated the “Security Considerations” section in the
    operations guide
  • Updated the default value of SP Level in the “Service
    Pack Compliance” monitor for SQL Server 2012 (SP 4)
  • Added the actual value of free space (% and MB) in
    the alert description of the “Transaction Log Free
    Space (%)” monitor (SQL 2012 only)

SQL Server Dashboards

No changes introduced; increased the version number to 7.0.4.0 to
comply with the current version of SQL Server management packs

XPost SCOM 1801: Caveat when upgrading from 2012R2/2016

Just a quick cross post from my college Robert Bird original posting here.

Be aware that when upgrading to SCOM 1801 in order to upgrade reporting successfully you need to install the SCOM console onto the SSRS instance first otherwise the upgrade will fail.

SCOM 2016: Updated management pack for AudioCodes™ v1.0.5.65

An updated management pack has been released for AudioCodes™ get it here.

The following AudioCodes gateways are currently supported:
Mediant 4000 E-SBC
Mediant 3000 Gateway and E-SBC
Mediant 2600 E-SBC
Mediant 2000 Media Gateway
Mediant 1000 Media Gateway
Mediant 1000B Gateway and E-SBC
Mediant 1000B MSBR
Mediant 800 MSBR
Mediant 800B Gateway and E-SBC
MediaPack Media Gateways MP-124 (FXS)
MediaPack Media Gateways MP-118 (FXS and FXO)
MediaPack Media Gateways MP-114 (FXS and FXO)
MediaPack Media Gateways MP-112 (FXS)
MediaPack 1288

SCOM 2016: Updated SQL Management Packs v7.0.2.0

New versions of the SQL management packs have been released get them using the links below:

SQL Server 2016here
SQL Server 2014here
SQL Server 2008/2012here
SQL Server Dashboardshere

New in Version 7.0.2.0

SQL Server 2008/2012/2014/2016

  • Fixed issue: Always On data source scripts fail as Microsoft.SqlServer.Management.PSSnapins.dll is not imported
  • Fixed issue: Always On monitoring scripts may fail because of “No coercion operator is defined…” error (caused by an issue in PowerShell 5.0)
  • Fixed Dashboards issue: “DW data early aggregation” rule crashes on SCOM 2016

SQL Server Dashboards

  • Fixed issue: “DW data early aggregation” rule crashes on SCOM 2016

SCOM 2016: New management pack for Lenovo XClarity Integrator Hardware

Lenovo has released a new management pack to integrate SCOM with XClarity it is available here.

Key features include:

  • Extensive monitoring of the health of hardware components for System x and ThinkSystem servers,  Flex chassis nodes and BladeCenter blades via BMC (out-of-band mode).
  • Extensive monitoring of the health of hardware components for System x servers, Flex chassis nodes and BladeCenter blades running Windows (in-band mode).
  • Rich monitoring of the health of Flex and BladeCenter chassis/modules via the SNMP protocol.
  • Easy determination of overall system health by the aggregation of hardware health monitors.
  • Power Monitoring of UEFI/BMC System x Servers and Blades running Windows. Offers the ability to monitor overall system power usage, and generates alerts when power consumption rises above predefined consumption thresholds. Enable Power Capping and set the maximum power consumption wattage via Operation Manage Agent task.
  • BladeCenter and Blade hardware health correlation and event propagation providing BladeCenter specific hardware health condition monitoring under the Windows health explorer view.
  • Remote power on and off of Blades Servers via the Operations Manager console.
  • Offer the ability to launch a CMM Web Console of a Flex System Chassis from the Operations Manager Console.
  • Offer the ability to view System x power data using the System x Power Data Chart.
  • Offer the ability to support SQL Server database and migrate data from the PostgreSQL to the SQL Server.
  • Offer the ability to discover and manage system BMC automatically.
  • Offer the ability to configure Unified Service from the Operations Manager Console

SCOM 2016 the importance of Backing up your SSRS encryption key

Definitely not something you want to see on your second day back at work:

The report server cannot decrypt the symmetric key used to access sensitive or encrypted data in a report server database. You must either restore a backup key or delete all encrypted content.

Luckily my customer had a recent backup of the SSRS key and it was a simple matter to restore the key and restore SCOM reporting functionality.

You may be asking “How do I backup my SSRS encryption key?” no worries it is a simple procedure, I recommend making this process part of a monthly set of tasks.

First open your SQL Reporting Services Configuration Manager
Then navigate to Encryption Keys on the left hand side
Then click Backup, you will be promoted for a file name and a password

Restoring the key is similar you just select Restore from the same page and locate the key file and provide the password.