The Management Pack Tool Collection

  • Article

The tools described in this section are used specifically with Management Packs.

Business activity monitoring (BAM) Wizard

Use this tool to monitor key performance indicators that are extracted from a BizTalk business process.

Type: Wizard.

File list: bam_readme.txt, BamMP.exe, Microsoft.EnterpriseManagement.Mom.Bam.dll, mputil.dll, regbam.exe, StateRoleMP.exe

How to install:

  • Copy all of the binaries to the MOM Management Server.

  • Copy the Microsoft.EnterpriseManagement.Mom.Bam.dll and regbam.exe to the BizTalk computer (the agent).

  • Run regbam.exe, on both the Management Server and the agent, to register the BAM dll.

How to use:

  • Run BamMP.exe to invoke the BAM Management Pack Wizard.

Configure Action Account

Use this tool to configure the MOM Agents Action account so that most Management Packs can run with a low-privilege account.

Type: Command line.

File list: ConfigActionAccount.exe.

Prerequisites:

  • You must be an Administrator to run ConfigActionAccount.exe.

Only Windows Server 2003 is supported.

How to use: Use this tool as follows:

        ConfigActionAccount.exe <user> <options> [/?] 
 
<user>
 /user:domain\account  //The user to set (or remove) permissions for. For local accounts, use machinename\account.

<options>
 /mommp   //Configure minimum permissions for MOM 2005 Management Pack.
Note: there are also SQL permission required for monitoring the MOM database
 /cleanup   //Removes the user from all permissions granted by /mommp.
Note:/cleanup overrides /mommp.
Notes:
Options may be delimited by '/' or '-'.
- ConfigActionAccount.exe only grants (or removes) permissions needed for a non-administrative Action Account. Use SetActionAccount.exe to set the Action Account used by a MOM 2005 management server or agent.
- Minimum permissions needed by the Action Account for the MOM Management Pack [/mommp] are:
- Member of the "Users" local group
- Member of the "Performance Monitor Users" local group
- Assigned the "SeSecurityPrivilege" user right
- Assigned the "SeInteractiveLogonRight" user right

Convert Management Packs to XML

Use this tool to perform a one-way conversion of MOM 2005 AKM files to an XML format file. The XML file can then be used to determine differences between two versions of the same Management Pack, and for versioning in a source control system.

Note

The xml format created by this tool is currently not supported, but that that it is subject to change going forward.

Type: Command line.

File list: MP2XML.exe, MP2XML_Readme.doc.

Prerequisites: Must be run on the Management Server.

How to use: From the command prompt, use as follows:

        MP2XML.exe <AkmInputFile> <XmlOutputFile> 
 
<AkmInputFile>   // the path and name of the akm input file
<XmlOutputFile>   // the path and name of the xml output file

Event Creator

Use this tool to create events for testing Management Packs. Event Creator enables you to choose event sources for the existing event logs that are currently registered.

Type: Graphical user interface.

File list: EventCreator.msi, EventCreator_Readme.doc.

How to install: Run EventCreator.msi to install the tool.

How to use: At the command prompt, type: EventCreator.exe. From Windows Explorer, navigate to Program Files/Event Creator and double-click EventCreator.exe.

After the program is started, you can specify an event source, select an event ID, type, and category, and then generate the event.

Managed Code Response Utility

Use this tool to obtain the correct strong name that is needed when you are configuring a Managed Code Response in MOM. This utility also enables you to show and select the methods and parameters that are allowed, when configuring a Managed Code Response to run a specific method.

Type: Command line.

File list: MCRUtil.exe, MCRUtil_Readme.doc.

How to use: Run this tool from the command prompt, as follows:

        MCRUtil.exe <Action> <Arguments> 
<Actions>:
/displayname   //Gets the full display name for the assembly (needed if more than one version of the assembly exists on the system).
/methodsig   //Gets the method signature to use when setting up the MCR in MOM.
<Arguments>:
/assembly:<Assembly File Name>   //Required for all actions.
/method:<Method Short Name>   //Needed for the '/methodsig' action, use the name of the method without the class or namespace (prints all matches).

Management Pack Differencing Tools

You use this tool to generate a XML report of what was added, deleted, or changed between a source and a destination Management Pack. The graphical user interface supports interactive viewing of the differences. The command-line interface enables you to automatically generate a report that uses XSLT to create an HTML table.

Type: Command line and graphical user interface.

File list: DiffOutToHTML.xslt, mommp.xsd, MpDiff.Console.exe, MpDiff.Core.dll, MpDiff.exe, MpDiff.LockSys.dll, MpInfoModel.dll, MPDiff_Readme.doc

Prerequisites:

  • These tools expect the Management Pack in XML form. You can use the MP2XML.exe in the MOM 2005 Resource Kit to produce the XML format for a Management Pack.

  • These tools require .NET Framework v1.1.4322 or later.

  • Internet Explorer 6.0, or later, for viewing the XML difference report with the XSLT provided.

How to use: From the command prompt, use as follows:

        MPDiff.Console.exe <required> [<optional>] 
 
<required>
/src:   // The source ManagementPack XML file.
/tgt:   // The target ManagementPack XML file.

[<optional>]
/lock:   // Apply a lockfile against the diff result.
/createLock:   // Create a lockfile from this diff result.
/schema:   // Whether to validate against MOM XSD (default is 'on')
/out:      // The XML diff result file to output (default is 'diffout.xml').
/v:ucad      // Verbosity level. Items can be chained. Example: "/v:cad".
      u = Show unchanged items.
      c = Show changed items.
      a = Show added items.
      d = Show deleted items.

From Windows Explorer:

  1. Open MPDiff.exe.

  2. Click File/Compare Management Packs.

  3. When prompted, identify the first XML Management Pack.

  4. When prompted, identify the second XML Management Pack.

  • The results tree will provide summary, and detailed information, about the differences between the two files.

Management Pack Version Checker

Use this tool to compare the latest Management Packs, published on the Microsoft Web site, against the latest Management Packs that you have installed in your management group. You are notified if there are version differences.

Type: Management Pack.

File list: MPNotifier.akm, MPNotifier_Readme.doc

Prerequisites:

  • MOM 2005

  • Internet access for the MOM Server that you add to the management group and the Agent Account on that server.

How to install: Import MPNotifier.akm, and then add a Management Server to the Microsoft Operation Manager MPNotifier MOM Server computer group.

How to use: Use the same way that you would use a conventional Management Pack.

Management Pack Wizard

Use this tool to create a custom Management Pack for your MOM environment. Based on your input, this wizard creates:

  • Rules to monitor each Windows Service, to adjust the health of selected components.

  • Rules to monitor each performance threshold that is created.

  • A Rule Group for the Management Pack.

  • A class and relationship structure for the monitoring role.

  • A service discovery script and time rule.

  • The Management Pack.

Type: Graphical User Interface.

File list: MPWizard.exe, mputil.dll, MPWizard_Readme.doc.

Prerequisites: User must be a member of the MOM Administrator or the MOM Author group.

How to use: Copy MpWizard.exe and mputil.dll to the computer where you want to create the Management Pack. Double-click MpWizard.exe (or use the command line) to start the wizard.

Remove Blank Rule Names

Use this tool to automatically generate a unique name for any MOM 2000 Service Pack 1 (SP1) rule that has a blank name. In addition, you might not see rules with blank names in the Management Pack if they are marked as deleted.

Note: MOM 2005 does not allow rules with blank names.

After converting the MOM 2000 SP1 AKM file, this tool produces a new AKM file that has names for all of the rules. You can then import this file without causing import errors.

Type: Command line.

File list: RemoveBlankRuleNames.exe, RemoveBlankRuleNames_Readme.doc

Prerequisites: This tool must run on a MOM 2005 server.

How to install:

How to use: Run this tool from the command prompt, as follows:

        RemoveBlankRuleNames.exe <AkmInputFile> 
<AkmInputFile>  // the path and name of MOM SP1 akm file

Response Tester

Use this tool to test your scripts and responses. Test results are displayed on the command-line screen, or can be saved to an XML file.

Type: Command line.

File list: MOMXResponseTester.dll, MOMXResponseTool.dll, ResponseTest.exe, ResponseTest_Readme.doc.

Note: There is a samples folder that contains XML files.

Prerequisites: None

How to install: Copy all of the files to the MOM installation directory on a MOM agent-managed computer, or the Management Server computer. Register the .dlls by running:

  • Regsvr32 MOMXResponseTool.dll

  • Regsvr32 MOMXResponseTester.dll

How to use: Run this tool from the command prompt, as follows:

        ResponseTest.exe [options...] 
 
Options:
   /?      // obtain detailed information about the options
    /config:<path>   // The path to the configuration file. The configuration file must be of the form described. Press 'c' for more information.
/script:<path>    // The path to the script file. The script file must be of the form described. Press 's' for more information.
/out:<path>   // The path to the output xml file. This defaults to 'console'. Press 'o' for more information.
/f         // Overwrites the output xml file if it exists.
/q         // Suppresses all prompts.
/d         // Enables script debugging.
/x         // Breaks on first line of script.

Resultant Set of Rules

Use this tool to view the resultant set of rules that are currently targeted to an agent.

Type: Command line.

File list: RSOR.exe, RSOR_Readme.doc.

Prerequisites: This utility communicates directly with the MOM DB Server hosting the OnePoint database using ActiveX Data Object (ADO).

How to use: Run this tool from the command prompt, as follows:

        RSOR.exe <MOMDBServer[\instance]> <TargetAgent> 
 
<MOMDBServer> // the name of the MOM database server that hosts the OnePoint database
[\instance]     // provide the instance name is the database is not the default instance
<TargetAgent> // the name of the managed computer whose rules you want to obtain

The output from running this tool is a text file that is created in the following folder: C:\ResultantSetOfRules. The file naming convention is: COMPUTERNAME RSOR 2004-11-11 HHMMSS.log.

Note

"HHMMSS" is not hard coded, the hours, minutes, and seconds time stamp is automatically generated when the output is created.

Rule and Group Toggle Utility

Use this tool to enable or disable any of the following, by name or by GUID:

  • Computer Groups

  • Rule Groups

  • Rules

Type: Command line.

File list: RuleUtil.exe, RuleUtil_Readme.doc.

Prerequisites: None

How to use: Run from the command prompt, as follows:

        RuleUtil.exe <Action> [<Specifier>] [<Option(s)>] 
 
<Action>   
            /list:[<all/computer/rule>]   // Lists the computer or processing rule groups (all/computer/rule arguments are optional), defaults to all.
            /enable      // Enables the specified computer or processing rule group
            /disable   // Disables the specified computer or processing rule group.
            /commit:[<true/false>] // Commits any changes (true/false arguments are optional, defaults to true), this flag can be combined with the enable or disable flags.

<Specifier>    
            /compgroupname:<name>   // Specifies the name of the computer group.
            /compgroupid:<id>   // Specifies the id of the computer group.
            /rulegroupname:<name>   // Specifies the name of the computer group.
            /rulegroupid:<id>   // Specifies the id of the computer group.

 <Option(s)>
            /r    // Lists the subgroups as well as the top level groups, only valid with the 'list' action.