Adding a Report to a Management Pack using VSAE

I thought I would post how to get a simple custom SSRS report included in a management pack using VSAE.

There are articles out there but I was not, for some reason, making the connection between the REPORT and the RESOURCE in my head. The following article link explains in more detail the report options. I only wanted to understand the most basic  requirements to get a report into a Management Pack.

I’ll use the following file name for the example “My.Report.rdl” which contains the entire XML for the report definition.

Step 1

Add the “My.Report.rdl” file to the solution.

Step 2

Add a management pack fragment named “MyReport.mpx” and add the following XML code:

      <Report ID=”REPORT.IDAccessibility=”InternalVisible=”true“>
    <ReportResource ID=”RESOURCE.IDAccessibility=”InternalFileName=”MyReport.rdlMIMEType=”application/octet-stream HasNullStream=”false” />

REPORT.ID you define
RESOURCE.ID you define

The <ReportDefinition> tag should contain the RESOURCE.ID you define in the <ReportResource ID=””…> attribute. This links the report to the resource.

The <ReportResource FileName=””> attribute contains the file name of the RDL file that was added to the solution. This links the resource to the file in the solution.

So at this point the REPORT tag points to the RESOURCE tag which points to the FILE with the report definition and can be included in the management pack.  You don’t actually include the XML for the report in a management pack fragment.

At this point the solution should be ok to build and then import.

I used the “Data Warehouse Main” as a shared data source in my SSRS report so that I can leverage the Data Source that is already there.  If you create a custom data source, you will have to create the custom data source to the SSRS implementation in order to leverage it.

2 thoughts on “Adding a Report to a Management Pack using VSAE

  1. curtmcgirt

    craig, i’m actually responding to another blog post/download, but this site won’t let me reply to that one. did you happen to update your notification subscription HTML report powershell script for scom 2012? I think it’s written for 2007:


    it’s not including any groups for me. “Get-MonitoringObjectGroup” and “Get-MonitoringClass” don’t return any values when I run them manually against my management server.

  2. Craig Pero Post author

    I’m sorry… it’s been a while since I’ve been back online with SystemCenterCentral.  I have not updated it but if you are still trying to and not having success, the cmdlets now include “SCOM” so Get-MonitoringClass is now Get-SCOMMonitoringClass.  I do need to get back to this script and update it… It was a huge help at a company I used to work for and seemed to need to know which subscription was sending alerts to what groups.

    I’ll post when I get back to it.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.