Tag Archives: VisualStudio

Authoring SCOM Reports in VS 2010

14 Jan


Short post on how to get you dev environment ready for authoring scom reports.


You have installed SCOM 2012 on SQL 2008. You want to author a custom report using Visual studio 2010. When you open visual studio you will notice that NO BI project template is shown. Normally you selected this project template and selected the new report project to make your custom report. How now to continue ?


Grab a SQL 2012 ISO (YES 2012) and startup the setup.

1) Select installation:


2) New sql or add features


3) Select SQL features Install


4) Now the important step. Select the 3 options here. Most important is the “SQL Server Data Tools”. This features contains the VS BI project template.


5) Step though the install windows.

And now open Visual studio 2010 and create a new project. And what do we see ?

Yes the BI template Knipogende emoticon 



Now you can create the new SCOM reports. Notice also the NEW chart types !!!



Remember that if you use custom report code components you must copy the correct .dll assemble to the directory:

C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies

The End.

Happy Scomming

Michel Kamp

SCOM author meets VisualStudio

11 Feb


As promised I will write 1 blog post a week. This time I will describe a method I used the last 5 years for authoring my management packs. I can say that all of this below will change completely over about 2(?) months. This because the “VisualStudio Authoring Console Extensions” will be officially released by Microsoft. But I was one of the lucky ones to test this extensions and I must say its amazing. Before you think ‘give me more’ I say… wait till next blog post .. This blog post will be all about the old method making authoring less time consuming.

For daily authoring I use VisualStudio , VSS and the Scom Authoring Console. This combination works really good. The main MP body I make in VS and when I must create modules / rules / monitors … I use the Scom authoring console. Then when I want to verify the MP I use the MPverify tool and when I want to seal it I use the MPseal tool. Because I didn’t want to open a external window every time, I created  External tools in VS. So now I simply click the external tool and the work (verify / seal / import) is done. The output of the external tool will be displayed in VS. So no need for switching windows.

Using this combination is really decreasing the duration of making a SCOM management pack.

Here’s my External tool window in VS:


And here is a (old) MP I created using XML in VS and the authoring studio


So when I want to Verify the MP I go to the tools menu and select the “MP Verify” tool. Now the MP XML will be checked and the output will be written to the output windows below.


If any error is detected it will report also in this window so you can quickly see what’s wrong without leaving VS.



For the MP seal action it’s the same way. Pick the tools –> mp fast seal. The output will be:


When I want to add a module I could choose to create it in XML (see also my blog on how to enable the MP schema check in VS) but I could also simply use SCOM authoring console , select tools > MP autoing console ,  and create the module here , save it , and reload the XML file by clicking YES to all in VS.



Hope you see the time saving here.

Okay enough bla bla. Give me the the code to do this…

What you have to do is:

1. Install VSS 2005 if you want to safe you’re work with revisions. I say this is a MUST for every MP author USE A SOURCESAFE TOOL!! Sometime later this will be your live safer.

2. install VS 2010

3. install the SCOM authoring console AND the Authoring tools so you can use the workflow simulator.

4. create empty VS solution

5. add a Empty VS project

6. make a directory tree and put here your certificate you want to use for MP sealing.

7. now create the external tools in VS. Press tools > External tools…


And press Add.


Fill in the new name “MP verify” and fill in the command , arguments , install directory .

See the table below for all the tools I created.


Title MP Verify
Command C:\Program Files\System Center Operations Manager 2007\MPVerify.exe
Arguments /I "$(ProjectDir)" /I "G:\OPS\Development\Root MP Libs" $(ItemFileName)$(ItemExt)
Initial directory $(ItemDir)
Title MP Authoring Console
Command C:\Program Files\System Center MP Authoring Console 2007\Microsoft.EnterpriseManagement.UI.MPAuthoring.exe
Arguments $(ItemFileName)$(ItemExt)
Initial directory $(ItemDir)


Title MP Fast Seal
Command C:\Program Files\System Center MP Authoring Console 2007\FastSeal.exe
Arguments /KeyFile "d:\ONTW\ScomVirtualSourceSafe\ScomVirtualSourceSafe\mpseal\tbb.snk" /Company "Your Company" $(ItemPath)
Initial directory /KeyFile "d:\ONTW\ScomVirtualSourceSafe\ScomVirtualSourceSafe\mpseal\tbb.snk" /Company "Your Company" $(ItemPath)


The tool below need a Powershell script. If you google Bing you will find plenty of MP import scripts you can use.

Title Import MP To LAB
Command C:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe
Arguments -NoExit  "D:\ONTW\ScomVirtualSourceSafe\ScomVirtualSourceSafe\SCOM_VS_AddIn\ImportMP.ps1" $(ItemFileName)$(ItemExt)
Initial directory


Now you have created all the tools you need.

One thing before I stop. Save your just created tools settings. I have seen plenty of issues after installing VS patches that will reset you tools configuration. You can save it by doing an export. And if needed you can restore it by using the import function.







So now you are ready to develop with speed.

Next time I will blog on the new way of doing the SCOM authoring by using the “VisualStudio Authoring Console Extensions” and believe me this tool you may not miss !!

Happy Scomming,

Michel Kamp