There are several management packs that come packaged with SCOM. If you know well how to use them, you do not have to go through a tough time customizing one for your specific needs.

A packaged management pack is in the MP format. You can export this management pack into XML and get started from there. But there is a catch, you can export unsealed management packs only. So, how do you get the XML equivalents of the sealed management packs.

Well we have some tricks up our sleeve here. We can use the following powershell script to just what we want. save this in a file with a ps1 extension and execute it with powershell passing 2 parameters, first parameter being sealed management pack path and second one will be the directory where you want the XML file created.

param($mpFilePath,$outputDirectory)

$assembly = System.Reflection.Assembly::LoadWithPartialName("Microsoft.EnterpriseManagement.OperationsManager")

$mp = new-object Microsoft.EnterpriseManagement.Configuration.ManagementPack($mpFilePath)

$mpWriter = new-object Microsoft.EnterpriseManagement.Configuration.IO.ManagementPackXmlWriter($outputDirectory)

$mpWriter.WriteManagementPack($mp)

Now that you have a getting started XML MP, you can start customizing it to add your own references, discoveries, data sources and attributes to make it fit your requirement.

We really think that XML based MP creation is for very advanced users, so we recommend that you just know the structure of a MP and try and use attributes to achieve your requirement.

Here are the various steps to create a GETTING STARTED management pack

1. Export existing management pack from SCOM console and modify the MP

2. Generate XML based MP from a sealed MP using the powershell script shared above.

3. From SCOM console create a management pack, export it and then modify it.

Adding attributes

1. Attributes can be added to any existing management pack

2. Good practice to create your own management pack and add your attributes to it

3. Attributes cannot be deleted, the management pack has to be deleted for attributes to be deleted

Scenario

Refer the smartdrive requirement and challenge from here

In such a scenario, the path to go down would be to design the management pack to get the file counts using a script based discovery. Then add all other items like application discovery and performance counters using attributes.

Or create a specialized class Blog entry to get the file count into WMI and then use a default management pack to get all the discoveries using WMI.

Last edited Oct 13, 2009 at 8:37 AM by vondino, version 1

Comments

No comments yet.