First part: https://maxcoreblog.com/2020/07/23/implementing-scom-managed-modules-part-1/ Second part: https://maxcoreblog.com/2020/08/05/implementing-scom-managed-modules-part-2/ Multiple Instances. In the past examples, the rules and the monitors target a class, which has singular instance per SCOM Agent. In other words (under usual circumstances), one SCOM Agent monitors single Windows Computer. The next experiment aiming to answer another question: how many instances of a managed module… Read More
Implementing SCOM Managed Modules. Part 2.
First part: https://maxcoreblog.com/2020/07/23/implementing-scom-managed-modules-part-1/ In the first part, a simplest probe action managed module was created to investigate SCOM managed modules live cycle. For that purpose, the module was fit with excessive logging for very each step. Initial testing scenario was: deploy the MP with the test probe action module, let it run two times, then… Read More
Implementing SCOM Managed Modules. Part 1.
Introduction First of all, what are SCOM modules in general, and managed modules in particular? A module is the smallest building block of any monitor, rule, or discovery. Like composition of atoms create molecules and matter, composition of modules create monitors, rules, discoveries, or other composite modules. Like the ancient meaning of the word “atomos”,… Read More
Are SCOM Ids random?
Objects and entity identifiers Every single monitored object (class instance), or class, or monitor, or rule, or any other management pack element in SCOM has its own unique identifier. The id is of type of Guid in PowerShell/C# or uniqueidentifier in SQL. Looking at a Guid property (where GUID is an abbreviation for Globally Unique Identifier), it is reasonable… Read More