Importing the SharePoint MP into SCOM 2012

If you follow this guide you shouldn’t encounter any issues when installing the SharePoint 2010 MP into SCOM 2012


Ensure the following MPs are imported and healthy:-

  • Windows OS – Same version as SharePoint
  • IIS – Same version as SharePoint
  • SQL – Same version as SharePoint

It is important to ensure that the SharePoint Run-As account is set up as more secure and points to all your SharePoint servers

Also ensure that your SharePoint Run-As account has the following permissions or you will definitely encounter issues! :-

Local admin on all SharePoint 2010 Front End and Application Servers

Local admin on all SQL machines that host SharePoint 2010 databases

Full Farm Administrator rights within SharePoint 2010

DBO for all SharePoint databases

The original Microsoft SharePoint 2010 Management Pack for OpsMgr/SCOM 2007 must first be downloaded and imported into SCOM 2012 before installing this updated management pack and you can download it from here (make sure to download the guide too):

Follow the instructions in the guide for the Microsoft SharePoint 2010 Management Pack for SCOM 2007 to install and import it into your environment. Make sure you have configured your Run As account as per the guide recommendations as they will be required later in this process.


Once you have the Microsoft SharePoint 2010 Management Pack for SCOM 2007 imported, you can now go about installing the updated management pack for SCOM 2012. Download the System Center 2012 Monitoring Pack for SharePoint 2010 to a location on your SCOM 2012 server from here:

When the management pack installer has been downloaded, right-click on the .msi and choose the Install option.

Accept the license agreement, then click Next

At the Select Installation Folder dialog box, make a note of the default installation location and notice that it will deploy to the  ‘Program Files (x86)’ directory (this is important to know for a later step), then click Next

Click Close to finish the initial installation of the extracted the files

Browse to the aforementioned location ‘Program Files (x86)’ directory  that the installer recommended and make sure that you can see the ‘Microsoft.SharePoint.2010.SCOM2012’ folder

Double click on the folder and you should see the new ‘’ file inside

**Now, this is where things can start to go wrong with this management pack if you’re not careful.**

From the original location of ‘C:\Program Files (x86)\System Center Management Packs\Microsoft.SharePoint.2010.SCOM2012’, copy the ‘’ file and the SharepointMP.Config file to:-

C:\Program Files\System Center Management Packs

Do this on all of your SCOM management servers if you have more than one (not the database servers)

Edit the SharepointMP.Config file so that it contains the hostnames of all your SharePoint servers.

I needed to do this to prevent the Run As account for SharePoint overwriting the Run As account for all of my other servers being monitored by SCOM.


– For “Agent” type, discovery proxy is also enabled on the matched machines so that farm level discoveries can work correctly.
<Association Account=”SharePoint Discovery/Monitoring Account” Type=”Agent”>
<Machine Name=”” />
<Machine Name=”” />
<Machine Name=”” />
<Machine Name=”” />
<Machine Name=”” />
<Machine Name=”” />
<Machine Name=”” />
<Machine Name=”” />

Once you have copied the management pack file from the (x86) folder to the new location, in the SCOM 2012 console, browse to the Administration tab on your console, expand the Administration view, right-click on Management Packs and then choose the Import Management Packs option to start the wizard.

In the Import Management Packs wizard, choose the Add from Disk option and then browse to the new location that you copied the’ file to.

If you’ve followed the instructions above correctly, this location will be C:\Program Files\System Center Management Packs

Double click on the copied management pack file and you will then see something similar to the screenshot below.

Note: If you haven’t met the prerequisites and first installed the Microsoft SharePoint 2010 Management Pack for SCOM 2007, you will receive an error here stating that there is a dependency missing.

When you click on the Install button, you should then see confirmation that the new management pack has been imported successfully. Click the Close button to exit the dialog box.

Browse back to the Monitoring tab, expand the SharePoint 2010 Products view and then click on the Administration view. If all has gone according to plan, you should see your Microsoft SharePoint 2010 Farm Group in the central screen and on the right-hand side in the Tasks pane, you will now see the new ‘Configure SharePoint Management Pack (SCOM 2012)’ task

Click on the new task and you will be presented with the following dialog box – notice that the Working Directory value is set to: %ProgramFiles%\System Center Management Packs

It’s this value that had the requirement for us to earlier copy the management pack file out of the (x86) directory and move it as without the file being copied, this task wouldn’t run.

If you have correctly configured your Run As account for the Microsoft SharePoint 2010 Management Pack as per the MP guide recommendations, then you should be able to just click on the Run button inside this task.

You will then be presented with a screen confirming that the discovery of your SharePoint 2010 Farm Group has been successful.

Note: Make sure to wait a while for the discovery process to complete in your environment as it won’t always show up in the console immediately.




This entry was posted in Management Packs, Misc Stuff and tagged , , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s