Update rollup management pack

Disclaimer

Use this management pack at your own risk. I accept no responsibility if it causes damage.

Intro

A simple little management pack to help you monitor update rollups versions.

Tested on:

• SCOM 2012, 2016.
• Windows Server 2008, 2012, 2016.

Elements

Classes

• Microsoft.SCOM.UpdateRollup.Class.WindowsComputer

Module Types

• Microsoft.SCOM.UpdateRollup.DataSource.ManagementGroupReport
• Microsoft.SCOM.UpdateRollup.DataSource.ManagementPackBackup
• Microsoft.SCOM.UpdateRollup.DataSource.WindowsComputer
• Microsoft.SCOM.UpdateRollup.WriteAction.DailyReport
• Microsoft.SCOM.UpdateRollup.WriteAction.GetLogAnalyticsWorkspaces
• Microsoft.SCOM.UpdateRollup.WriteAction.GetTlsSettings
• Microsoft.SCOM.UpdateRollup.WriteAction.GetWindowsDiskInfo
• Microsoft.SCOM.UpdateRollup.WriteAction.GetWindowsServices
• Microsoft.SCOM.UpdateRollup.WriteAction.LogWindowsTestEvent
• Microsoft.SCOM.UpdateRollup.WriteAction.ManagementGroupReport
• Microsoft.SCOM.UpdateRollup.WriteAction.ManagementPackBackup
• Microsoft.SCOM.UpdateRollup.WriteAction.RemoveManagementGroup
• Microsoft.SCOM.UpdateRollup.WriteAction.RunCommand
• Microsoft.SystemCenter.ResetServiceStoreAction

Discoveries

This discovery is enabled by default.

• Microsoft.SCOM.UpdateRollup.Discovery.WindowsComputer

Rules

The rules in bold below are disabled, the rest are enabled.

• Microsoft.SCOM.UpdateRollup.Rule.AlertOnLogWindowsTestEvent
• Microsoft.SCOM.UpdateRollup.Rule.DailyReport
• Microsoft.SCOM.UpdateRollup.Rule.MgReport
• Microsoft.SCOM.UpdateRollup.Rule.MpBackup
• Microsoft.SCOM.UpdateRollup.Rule.PowerShellScriptWarning

Tasks

• Microsoft.SCOM.UpdateRollup.Task.GetLogAnalyticsWorkspace
• Microsoft.SCOM.UpdateRollup.Task.GetTLSRegSettings
• Microsoft.SCOM.UpdateRollup.Task.GetWindowsDiskInfo
• Microsoft.SCOM.UpdateRollup.Task.GetWindowsServices
• Microsoft.SCOM.UpdateRollup.Task.LogWindowsTestEvent
• Microsoft.SCOM.UpdateRollup.Task.RemoveMgmtGroup
• Microsoft.SCOM.UpdateRollup.Task.ResetHealth
• Microsoft.SCOM.UpdateRollup.Task.RunCommand

Views

These views sit under the Operations Manager folder.

Properties collected from Windows computers.

Links

• Download monitoring mp
• Download views mp

Issues

1. Change the target on rule Microsoft.SCOM.UpdateRollup.Rule.PowerShellScriptWarning. On some servers the discovery fails to run and it doesn't detect the warning event 17610 because the rule targets Microsoft.SCOM.UpdateRollup.Class.WindowsComputer so an instance needs to exist for it to work. If you change it to HealthService, we'll get the alert because an instance already exists for that class. You need to be careful here though, in new environments you could get spammed.
2. On 2008 servers the script is failing because PowerShell 2.0 doesn't support this parameter: -ErrorAction:Ignore. so it throws this error: Cannot bind parameter 'ErrorAction'. Cannot convert value "Ignore" to type "System.Management.Automation.ActionPreference" due to invalid enumeration values. Specify one of the following enumeration values and try again. The possible enumeration values are "SilentlyContinue, Stop, Continue, Inquire".
3. Get disk info task is broken. The code isn't formatted properly so some lines are missing a carriage return.
4. Rule Microsoft.SCOM.UpdateRollup.Rule.UnsealedMpBackup no longer uses data source Microsoft.SCOM.UpdateRollup.DataSource.ManagementPackBackup. It now uses just a write action module called Microsoft.SCOM.UpdateRollup.WriteAction.UnsealedMpBackup so I can schedule a start time. I left the data source module in there as the import complains on import if you remove it. To get around this you'd need to remove then import new mp.

Changes

MP Name	MP Version	Change
Microsoft.SCOM.UpdateRollup.Monitoring	2024.2.1.0	Fixed issue 1.
Microsoft.SCOM.UpdateRollup.Monitoring	2024.2.2.0	Fixed issue 2.
Microsoft.SCOM.UpdateRollup.Monitoring	2024.2.19.0	Fixed issue 3.
Microsoft.SCOM.UpdateRollup.Monitoring	2024.3.14.0	Fixed issue 4.