Part 1: Use VSAE to create a new Management Pack Project


 

This is Part 1 in a multi-part series explained here:  https://blogs.technet.microsoft.com/kevinholman/2016/06/04/authoring-management-packs-the-fast-and-easy-way-using-visual-studio/

 

 

Step 1:  Install a supported version of Visual Studio.

 

Step 2:  Install the VSAE components from https://www.microsoft.com/en-us/download/details.aspx?id=30169

 

Step 3:  Open Visual Studio.  File > New > Project

 

image

 

Step 4:  Pick the version you want to write for, and give your project a name based on a naming standard.  My naming standard will be “CompanyID.AppName” so if my company abbreviation is “Fab” (for Fabrikam) and I am writing this to monitor a custom application (I will make up a fake “DemoApp”)  I will call mine “Fab.DemoApp”

 

image

 

Step 5: 

Right click your “Fab.DemoApp” in solution explorer, and choose properties:

 

image

 

Here you can make changes to the core properties of your MP:

 

image

 

you can configure these to automatically deploy as you build the MP, to a development management group if you wanted, and even seal the MP as you build.

You are almost done!  We have the basic framework of a MP now, which is mostly empty except for some default references.  Let’s build this one just for fun.

 

 

 

Step 6: Build > Build Solution

 

image

 

In your output – you will see if it built successfully or if you had a problem that needs to be fixed:

 

image

 

In your bin\Debug path, which is where the management pack is written – open the XML using XML Notepad just to view it:

 

<?xml version="1.0" encoding="utf-8"?> <ManagementPack SchemaVersion="2.0" ContentReadable="true" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <Manifest> <Identity> <ID>Fab.DemoApp</ID> <Version>1.0.0.0</Version> </Identity> <Name>Fab.DemoApp</Name> <References> <Reference Alias="System"> <ID>System.Library</ID> <Version>7.5.8501.0</Version> <PublicKeyToken>31bf3856ad364e35</PublicKeyToken> </Reference> </References> </Manifest> </ManagementPack>

 

As you can see – it is pretty much empty, having only a Manifest section.  This will grow as we start to use fragments to add monitoring.

 

Step 7:  Save your MP

Use the “Save All” buttons at the top to make sure you save your changes.

image

 

This will be the foundation MP for all the Parts moving forward.


Comments (7)

  1. Alex says:

    Thank you a lot Kevin for a really nice introduction! This is something I seriously lacked, a good step-by-step guidance how to start exploring VSAE features. I’ll definitely use some of the fragments, great job!

  2. Excellent Article Kelvin.

  3. Kelvin do we need to install VSAE on Management server. I have database sever on remote location. Please guide.

  4. Karl says:

    Unable to save SCOM MP VSAE Projects – “The operation could not be completed”
    ———————————————————————————–
    I’ve loaded a fresh copy of VS2015 and set the default environment to “VB Settings”.
    Tested the install by creating a quick-n-dirty VB.net project and can save with no problem

    Now I’ve loaded Visual studio Authoring extensions and re-started VS2015
    Selected Management template – Operations manager 2007 R2 management pack
    Click on Save ALL but then a popup message appears “The operation could no be completed”.

    This is driving me mad. Tried the same on a fresh copy of VS2013 on my work machine using the steps above with the same results

    Any ideas ?
    Cheers
    Karl.

    1. Stef says:

      How do you add a report to a management pack.
      I cannot find any how to
      If someone can create some step by step instructions/video that would be awesome.

  5. Eric says:

    Nice introduction.
    A suggestion: add a “step 5b” about the deployment of the MP, i.e. to the ManagementGroup: it is possible to define the connection to your Service Manager server and push your MP directly there when you click the “Start” Button.
    AFAIK, the credentials for that push has to a domain account member of the domain group “Management group administrators” that was set during the installation of ServiceManager!

Skip to main content