Configuring SCOM R2 Management Pack for SharePoint 2010 Foundation Monitoring

This blog post discusses about configuring SCOM management pack for SharePoint 2010 farm.

Most of the part of this document is based on the SharePoint 2010 Management Pack installation and configuration document. I added more visualization and clarify some of the steps that you might miss as I did when configuring this.

These are the steps that you need to do to configure SCOM MP for SharePoint 2010 farm.


  • 2. Identify all of the servers in the farm. You can identify all of the servers in the farm by using the Central Administration Web site. If your installation of SharePoint fails to install components on a particular server, it is recommended you troubleshoot the server or remove the server from the farm so the server does not appear in Central Admin; failing to do so may add complications in the management pack discovery.
    If discovery misses any server in the branch, discovery or monitoring may not function correctly.


  • 3. Install Operations Manager 2007 agent on servers identified in step 2 by running the Operations Manager 2007 Discovery Wizard. It is recommended that you install the agent by adding computers to agent managed through Operations Manager 2007 console. For more information about installing Operations Manager 2007 agents, see the Operations Manager 2007 Deployment Guide at

Note: If an agent is already installed on the farm computers, you can skip this step.

  • 4. Configure Operations Manager 2007 alert notification - refer to the general guideline from Operations Manager 2007 guide.


  • 5. We recommended that you import and configure the Windows Server Operating System, SQL Server, and Windows Server Internet Information Services (IIS) Management Packs according to the Management Pack guides. These Management Packs are available at Ensure that you are using the matching Management Packs for Windows 2008 and Windows 2008 R2.

Put the MP files to the following directory:

C:\Program Files\System Center Management Packs


You need to make sure that the MPs for IIS 7, Windows Server 2008 OS, and SQL Server installed and imported.


  • 6. Download and install the Microsoft SharePoint Foundation 2010 Management Package.


  • 7. In the Operations Manager 2007 console, import the Microsoft SharePoint Foundation 2010 Management Package
  • 1. On the Operations Manager 2007 management server, open the Operation Console
  • 2. On the Administration tab, expand Management Packs.
  • 3. Right click the Management Packs node and select Import Management Packs.
  • 4. Go to "%ProgramFiles%\System Center Management Packs" and select
  • 5. Click Import and then Close.


8.Create a Run As account for Microsoft SharePoint Foundation 2010 discovery and monitoring in Operations Manager 2007 console

  • 1. On the Operations Manager 2007 management server, open the Operation Console
  • 2. On the Administration tab, expand Management Packs.
  • 3. On the Administration tab expand the Security node and right-click Run As Accounts, and select Create Run As Account.

The default name that should be use for Run As account is SharePoint Discovery/Monitoring Account as specified in the SharePointMP.config configuration file. For the Machine Name attribute in this file, I just left it blank, so SCOM will scan thru each machines in the inventory to find Sharepoint machines. You can specify Netbios name as well in the Machine name attribute.

Here's the view of SharePontMP.config file which define the default association account.

The Create Run As Account Wizard prompts for account type and display name which should "SharePoint Discovery/Monitoring Account"

The next step, the wizard will prompt for username and password. You should use account which has SharePoint farm administration privilege


The next step, it will as for distribution security option, you should select more secure and specify sharepoint boxes that are part of sharepoint farm members

Run Admin task to configure the discovery and monitoring

  • i. On the Operations Manager 2007 management server, open the Operations Console
  • ii. On the Monitoring tab
  • iii. Go to Monitoringà SharePoint 2010 Products folder (expand it if needed)
  • iv. Click on Administration node under SharePoint 2010 Products folder
  • v. Go to Actions Menu in the toolbar à Microsoft SharePoint 2010 Farm Group Tasks à Configure SharePoint Management Pack
  • vi. Ensure the the SharePointMP.config file is at the right location. Click Run.


After the previous step is completed, you should see changes on the sharePoint administration to the Microsoft SharePoint 2010 Farm Group, the state should not be "not monitored". It could be healthy, warnings, or critical but not "not monitored".

If it's in "not monitored", check the SharePointMP.config file under the machine name attribute make sure you put the correct NetBIOS name or you put it blank for testing purpose and then you can further refine once you're sure that the discovery run well.

I stumbled in this stage that SCOM couldn't discovery the sharepoint farm, Thanks to my colleague, Lloyd, who helped me with his expertise to sort things out J

  Wait for about half an hour to an hour to allow the discovery process to complete.

 9.Verify discovery results.

  • a) Open the Operations Manager 2007 console,
  • b) Go to the Monitoring tab (bottom left)
  • c) Go to the SharePoint 2010 Products folder (expand it if needed)
  • d) Click the Diagram View node
  • e) Expand the diagram view and review with your SharePoint administrator to see if all services that have been provisioned are discovered, if not, check FAQ to see if this a know issue and what is the workaround, if there is none, please retry.

We'll be able to view SharePoint Foundation Components until this step.

We are now able to view following information

Content databases

Diagram View


Farm State

Servers, services Front Ends, SPHA Rules, Web Application

As well as valuable health explorer features, which I think very cool as it scans thru the farm using the predefined health rules and monitoring unit defined in the management pack. It's like analyzing your Sharepoint farm based on Microsoft recommendations, it's verrry cool.

I'll post separate blog for including SharePoint Server components.

Comments (16)

  1. berryst says:

    You can use the SQL Server Management Pack to monitor the databases both the content and configuration database.

  2. Anonymous says:


    I'm having all kinds of grief configuring the SP 2010 MPs. The MPs install fine and running the Configure SP MP task runs without any errors. The RunAs account has local admin privs on all SP and SQL servers as well as on the SP farm. But… The SP servers end as "unidentified machines" and there's an error in the OpsMgr log on at least one of the servers saying "Cannot identify which SharePoint farm this server is associated with." Nothing shows in the Diagram View or any other section.

    These servers are in a separate forest/domain and the domain has a one-way trust to the domain that's hosting the SCOM management group. I don't know if that makes any difference or not. We're running SCOM 2007 R2 CU2.

    Any help/insights would be appreciated!


  3. martit01 says:


    I'm unable to run the Configure SharePoint Managment Pack task.  It's failing saying my Management Server Action Account does not have sufficient permissions.  The MSAA is part of the local admins group on the SharePoint server but I thought this Task was supposed to use the "SharePoint Discovery/Monitoring Account"?  



    An exception was thrown while processing Connect for session id uuid:c7ae955f-c223-43d2-b94b-1a8aecb4cd53;id=26.

    Exception Message: The creator of this fault did not specify a Reason.

    Full Exception: System.ServiceModel.FaultException`1[Microsoft.EnterpriseManagement.Common.UnauthorizedAccessMonitoringException]: The creator of this fault did not specify a Reason. (Fault Detail is equal to Microsoft.EnterpriseManagement.Common.UnauthorizedAccessMonitoringException: The user domainManagementServerActionAccount does not have sufficient permission to perform the operation.).

  4. Anonymous says:


    Sorry – I should have mentioned that we do have a SCOM gateway server in the untrusted domain and are using a certificate for authentication back to the internal domain. We are able to successfully monitor other servers in this untrusted domain. We can even monitor the SP 2010 servers for things like CPU performance, etc., using the various Windows MPs. It's just that we can't get the SP 2010 MP to report back.

    Perhaps the SP MP doesn't want to play well in that situation.


  5. berryst says:

    Hi Martit01,

    Please make sure that your Run As account that you specify has the following requirements.

    Create a “SharePoint Discovery/Monitoring Account” Run As Account (pick the DisplayName for the account listed in this config file) that is associated with a user account that has SharePoint 2010 farm administrative privileges and access to the related databases and application programming interface (API). For example, the account used to setup SharePoint Foundation 2010 and run the SharePoint Products and Technologies Configuration Wizard should have the required privileges.

  6. Anonymous says:


    Do this configuration apply for SCOM 2012 SP1 as well.
    I need to monitor sharepoint 2010 using SCOM 2012 SP1
    Asked the sharepoint team to provide the access to SCOM service account itself on farms and database
    secondly we have 3-4 farms to monitor. Is it possible to monitor them using single Management group consisting of two MS.


  7. berryst says:

    Hi Fred,

    Based on the reference that i got SCOM 2007 requires two-way trusts.

    Please refer to the following link for further information on how to make it work with different forest and one-way trust

    Managing Gateway Servers in Operations Manager 2007…/cc540382.aspx…/building-a-sample-scom-management-pack-for-dynamically-building-virtual-machines-based-on-performance-of-physical-or-virtual-machines.aspx

  8. Anonymous says:


    I turns out that the "privileged" account I'd been given for the RunAs account had full access to everything except the SQL Server environment. Once I used a more privileged account – and waited for a while – the servers, services, etc., started reporting in.

    Thanks for your help!


  9. Anonymous says:


    Thanks for your document..

    i tried to configure SharePoint as given by you. my account has admin level access  on server and application (both SQL server and SharePoint farm). After i ran Configure SharePoint Monitoring pack, it shows as success state without any error. then i have waited for more than 1 hr to see whether SCOM is populating data of SharePoint servers  but no luck. Even Administration node shows as "Not Monitored"

    Then i have enabled debug mode and ran the configuration once again, then also same status as success but no data.In Task status i could see everything as success, wondering where the problem is !

    Any inputs on this please



  10. MondeoDave says:

    My Content databases are showing as unmonitored.  Is that normal?

  11. ConfusedAboutConfigDatabase says:


    Thank you for your document.  

    I followed it very closely and for the most part SCOM is properly monitoring my SharePoint farm; however, my Configuration Database still shows as "Not Monitored" even though the SQL cluster is properly being monitored as is the SQL virtual server (when viewed from the SQL group that is).

    Interestingly, I noticed in your Diagram View above, your Configuration Database also shows as "Not Monitored".  Is this an expected end state or is there some bug somewhere?

    Please let me know.



  12. Lorenzo Gonzalez says:

    Is it possible to monitor multiple SharePoint farms in different domain from one SCOM 2007 R2 installation?  If so, is the process the same as above?


  13. vijayh says:

    i want to create one group with 10 servers and configure email notifications for only sharepoint related alerts. How can i achieve this. Please help me to fix this..

  14. Robin says:

    Does anyone know how to NOT monitor a particular sharepoint 2010 server. Ie disable sharepoint 2010 discovery

  15. Tim says:

    You could create a group with the servers you wish to "NOT Monitor" and override the "Discovery for SharePoint Foundation Installed Machine", setting it to False.

  16. Ramesh says:


    So is it by design that Configuration and Content Databases will show as "Not Monitored"? We do have SQL MP and they are showing monitored under that view!

Skip to main content