ManagementPack can be seen as an extension package that extends SCOM functionality, importing the appropriate MP can monitor things that need to be monitored, such as Windows, SQL, Exchange, Linux, AIX, Routers, and so on.

Essentially, SCOM cannot do without MP. Only MP platform is created by the product itself, which makes SCOM have strong monitoring function.

So here's a closer look at ManagementPack:

1. MP is a container: previous blogs Introduction to SCOM working concepts It has been explained that some basic concepts of SCOM are Monitoring Class, MonitoringObject, Monitor, Rule and so on. For migration and management convenience, SCOM is just like the concept of MP. Some of our defined classes, Workflow can be placed in an MP, which can be imported and exported.Users have great flexibility in choosing which MPs to apply according to their actual situation.

Like one of our DLL s, it can contain Class and its methods.MP defines monitoring object classes and how to monitor them.

2. MP can be encapsulated by signature: mp exists in two formats: one is.xml format, which is defined in clear text, the other is.mp format which is encapsulated by signature and can no longer be changed, but can be referenced.mp signature encapsulation can be used with SupportTools\MPSeal.exe under the installation disk. The encapsulation is to provide a key file with the name of Company Name and to generate a key file with sn.exe.

3. MP can refer to each other: this function makes MP look more like DLL, a concept defined in MP, another MP does not need to be redefined, just refer to the first MP.Just like we write programs, there is no need to repeat the code, just refer to each other if needed. Unsigned encapsulated MPs cannot be referenced, but you must ensure that the referenced MPs are imported when using them.

Here's a simple MP snippet:

<ManagementPack xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <Manifest>
    <Identity>
      <!--MP Of ID，Cannot have spaces, similar to the general file name format.
      File name must be{MPID}.xml，this ID Decided that the file name must be Microsoft.Mom.Samples.xml perhaps Microsoft.Mom.Samples.mp，
      Otherwise, an error will be reported when pouring in.-->
      <ID>Microsoft.SCOM.SampleMP</ID>
      <Version>1.0.0.0</Version>
    </Identity>
    <!--MP Display the name, this can be arbitrary.-->
    <Name>Sample Management Pack</Name>
    <References>
      <!--Add the following to be referenced MP Information, you can add more than one reference.-->
      <Reference Alias="System">
        <ID>System.Library</ID>
        <Version>6.0.5000.0</Version>
        <PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
      </Reference>
      <Reference Alias="Performance">
        <ID>System.Performance.Library</ID>
        <Version>6.0.5000.0</Version>
        <PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
      </Reference>
    </References>
  </Manifest>
  <!--The structure is given below, not in detail, and then the specific code will be posted later.-->
  <TypeDefinitions>
    <EntityTypes>
      <ClassTypes></ClassTypes>
      <RelationshipTypes></RelationshipTypes>
    </EntityTypes>
    <ModuleTypes></ModuleTypes>
    <MonitorTypes></MonitorTypes>
  </TypeDefinitions>
  <Monitoring>
    <Discoverys></Discoverys>    
    <Rules></Rules>
    <Tasks></Tasks>
    <Monitors></Monitors>
    <Overrides></Overrides>
  </Monitoring>
</ManagementPack>