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.
    Note:     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 http://technet.microsoft.com/en-us/library/bb419281.aspx.

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 http://www.microsoft.com/technet/prodtechnol/scp/catalog.aspx. 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 Microsoft.SharePoint.Foundation.2010.mp
  • 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

Events

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.