How to Import Additional Reports in SCCM

By | August 21, 2015

I’d say that the reports that come bundled with Configuration Manager are adequate. Useful, sure, but not as fancy as some other tools that are out there. They provide a great starting point on a robust platform (SQL Server Reporting Services) that is completely customizable, but they can leave a bit to be desired if you’re looking for fancier reports straight out of the box. Unfortunately, I am not an SSRS guru, but here are some great guides out there on how to create custom reports in SCCM if you’re interested in going down that road. Fortunately, people much smarter than me have written their own SCCM 2012 reports and have been generous enough to share their work with the public.

It has been a very common request from clients to implement better reports on my SCCM projects, and I haven’t had a great answer for a while. Everyone needs fancy reports for their VPs to receive in their inboxes, right?

This post is a quick guide on how to import custom reports in SCCM. Specifically, I will be importing the Software Updates Compliance Dashboard created by Gary Simmons for a more graphical report on patching. If you want to find more reports on the Internet, search for files ending in the RDL extension – this is the format SSRS uses.

If you haven’t already, install the Reporting Services Point in SCCM. Follow this guide on Windows-Noob if you need any help with this step.

Find the URL for your Reporting Services server. By default, it’s http://sqlserver/Reports, but you can grab it from Reporting Services Configuration on the SQL server, or you can find it in the SCCM console. Open the URL and ensure that you have access to the reports. You should be able to see the default SCCM reports if it has been set up correctly.

1

Download the reports that you’ll be importing through the web browser interface. In this case, we’re importing the five RDL files for the Software Updates Compliance dashboard mentioned earlier.

2

These specific reports link to each other (and existing out-of-the-box reports) and require a specific directory named “Software Updates Compliance” to be created inside your SCCM reports folder. Do this from the web UI.

3

Once the folder is created, open it, and upload the RDL files.

4

When complete, it will look like this.

5

Some reports will work immediately at this point. For these in particular, a few properties need to be modified inside. Select each report and edit them in Report Editor.

6

Update the Text Box properties in each report to match your own SCCM environment. Right-click the link inside the report and choose the Text Box Properties.

7

Under Action, rename the report path to match your three character site code. This should match the directory inside your SSRS directory. Check each link inside every report that has been imported to ensure that they are working properly.

8

We also need to check to make sure that the report is configured to use your SCCM database as the data source. Delete the current data source under Report Data.

9

Add a new data source.

10

On the general tab, browse for a new source.

11

Choose the data source that is listed in your root SCCM directory in SSRS. This is generated by default.

12

Name the new source “CM” and be sure that it’s highlighted before hitting OK. Save the report when finished.

13

Once this has been completed for all of the imported reports, you’re finished. You should be able to view the reports directly through the report server URL or from the SCCM console. From this point, you can create a subscription to configure how these reports are sent out. Here are some screenshots of the dashboards created by these particular reports:

Servers.png-550x0

SU Information

3 thoughts on “How to Import Additional Reports in SCCM

    1. Josh Heffner Post author

      Thanks for the comment! I had the same problem. I’d try deleting the datasource, re-adding it using the file generated in the CCM_*** directory, and then make sure it’s highlighted in the data source properties window. You may also want to try applying the latest cumulative update for your version of SQL server.

      Reply
    2. Josh Heffner Post author

      Also, it sounds like you may need to rename your datasource to “CM”, since that’s what these particular reports are looking for.

      Reply

Leave a Reply

Your email address will not be published.