Best Practices: Adding Custom Branding to SCOM reports

A few months ago I received a request for how to customize SCOM report headers to remove some corporate branding  which had been added by a consultant. This used to be a fairly easy topic to track down posts on, but a lot of the old posts aren’t around anymore.

If you want to modify SCOM 2007/2012 reporting with custom branding you need to go to the server that hosts your SSRS reporting instance and make a few changes.

If you aren’t sure where this is you can go to:


You need to go the URL: http://servername/reports (depending on your network you may have to remote that
server and go to http://localhost/reports)

Select Details View

If you upload and replace the banner_landscape.jpg, and banner_portrait.jpg with your custom branding images with files with the identical names

Go to Upload File

Upload and overwrite a new image to replace each. I attached the two images from one of my test environments. You can either use these, download the original images from any other SCOM reporting environment, or make your own banners just make sure you rename the files to match the existing file names.

You will now have SCOM reports with custom branding instead of the standard Microsoft System Center branding.


Best Practices: Migrating/Restoring SCOM Notification Subscriptions

This doesn’t come up often, but every once in awhile there is a need to move notification subscriptions from one SCOM Management Group to another. There is also the occasional instance where every once in awhile after an upgrade or change you realize you lost some or all of your notification subscriptions and subscribers to some good old fashioned upgrade related corruption.

In SCOM 2007/2012 the location where all notification subscriptions and subscribers are stored is the Notification Internal Library MP.

To migrate or restore a copy of the MP do the following:

1. Export a backup of the existing MP + check the version number of the MP

2. Retrieve file from prior to upgrade. (This is where periodic backups of all your management packs comes in handy) If version number present internally in the file differs from the post upgrade version number increment version number to match by editing in notepad and resaving being sure to preserve original file extension.

3. Import MP file into your production environment

4. Check and confirm that subscriptions and subscribers are present, as well as that they are working.

The contents of this site are provided “AS IS” with no warranties, or rights conferred. Example code could harm your environment, and is not intended for production use. Content represents point in time snapshots of information and may no longer be accurate. (I work @ MSFT. Thoughts and opinions are my own.)