Normally when you import a management pack of a product in SCOM, SCOM automatically starts monitoring that product. I was deploying and configuring SCOM to monitor several Microsoft products, when I imported SharePoint 2010 management, nothing appear under SharePoint 2010 management pack in monitoring, then I started studying SharePoint 2010 management pack configuration guide.
So in this blog post I will discuss about configuring management pack for Microsoft SharePoint 2010, 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 MP.
Following are some requirement that you need to fulfill before importing and configuring management pack.
– You must install the Microsoft SharePoint Foundation 2010 Management Pack before installing this Management Pack.
– Read the Microsoft SharePoint Foundation 2010 Management Pack guide before deploying this management pack.
– Download the Microsoft SharePoint 2010 Products Management Pack from the System Center Pack Catalog at (http://technet.microsoft.com/en-us/systemcenter/cc462790.aspx.
In this section step for setting up the environment, importing management packs, and configuring the system for monitoring using System Center Operation Manager 2007 SP1 will be discussed.
- Set up System Center Operation Manager 2007 SP1 servers. Follow the Operations Manager 2007 Deployment Guide at http://technet.microsoft.com/en-us/library/bb419281.aspx.
- Identify all servers that are 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. - Install the Operations Manager 2007 agent on the servers identified in step 2 by running the Operations Manager 2007 Discovery Wizard. We recommend that you install the agent by adding computers to agent managed through Operations Manager 2007 console. For more information about agent management, see the Operations Manager 2007 Deployment Guide at http://technet.microsoft.com/en-us/library/bb419281.aspx.
You can skip this step if the agent is already installed on agent computers.
- Configure Operations Manager 2007 alert notification. For more information, see the general guideline in Operations Manager 2007 guide.
- We recommend that you import and configure the Windows, SQL Server® and IIS Management Packs as described in the Management Pack guides. These Management Packs are available on the System Center Operations Manager 2007 Catalog at http://technet.microsoft.com/en-us/opsmgr/cc539535.aspx.
- Install the Microsoft SharePoint 2010 Products Management Pack.
Note: If the server where the Management Pack Windows Installation file is installed runs 64 bit Windows, the Management Pack will be installed in the %Program Files(x86)% folder by default.
- Copy the following files to the “%ProgramFiles%System Center Management Packs” folder on your Operations Manager 2007 management server:
- Microsoft SharePoint Foundation 2010 Management Pack
- Microsoft SharePoint Server 2010 Management Pack
- SharePointMP.Config
- In the Operations Manager 2007 console, import both the Microsoft SharePoint Foundation 2010 Management Pack and the Microsoft SharePoint 2010 Products Management Pack.
1) On the Operations Manager 2007 management server, open the Operation Console.
2) On the Administration Tab, expand the Administration node.
3) Right-click Management Packs and select Import Management Packs.
4) Navigate to “%ProgramFiles%System Center Management Packs” and select both the Microsoft SharePoint Foundation 2010 Management Pack and the Microsoft SharePoint Server 2010 Management Pack.
Note: The Microsoft SharePoint 2010 Products Management Pack depends upon the Microsoft SharePoint Foundation 2010 Management Pack. You cannot import it before the Microsoft SharePoint Foundation 2010 Management Pack. If you have already imported the Microsoft SharePoint Foundation 2010 Management Pack before this step, you can just select the Microsoft SharePoint Server 2010 Management Pack.
5) Click Import
- Create a Run As Account for the Microsoft SharePoint Foundation 2010 discovery and monitoring in Operations Manager 2007 console.
1) In the Operations Manager 2007 management server, open the Operations Console.
2) On the Administration tab, expand Administration , then Security , and then Run As Accounts.
3) Right-click Run As Accounts, and then select Create Run As Account.
4) Follow the wizard to create the Run As account, and record the account display name which is going to be used in the SharePointMP.config file as described in next step. You may choose to name your Run As Account “SharePoint Discovery/Monitoring Account” to avoid updating SharePointMP.config in next step.
Note: the Run As account must have sufficient privilege to allow discovery and monitoring to run. We recommend using the account which is a member of the Farm Administrator SharePoint group and is a member of the Administrators group on the database server hosting the SharePoint farm databases and access to all SharePoint databases. Usually the account used to run SharePoint 2010 Product Configuration Wizard has the required privileges.
Note: You can skip this step if you have already done this for the Microsoft SharePoint Foundation 2010 Management Pack.
- Run Admin task on the Operations Manager 2007 management server to configure discovery and monitoring.
a) Update the SharePointMP.config file with right information.
1) Open the SharePointMP.config file under “%ProgramFiles%System Center Management Packs”.
2) Find the section described below and update the account with the one you created in last step. Also add all of the servers in the farm for monitoring. For detailed information, follow the instructions in the SharePointMP.config file.
|
<Association Account=”DisplayName of Run As account” Type=”Agent”> <Computer Name=”agentComputerFilter1″ /> <Computer Name=”agentComputerFilter2″ /> … </Association>
|
b) Run Admin task to configure the discovery and monitoring.
1) In the Operations Manager 2007 management server, open the Operations Console.
2) In the Monitoring tab, navigate to the SharePoint 2010 Products folder.
3) Select the Administration node under the SharePoint 2010 Products folder.
4) In the Actions menu in the toolbar, click Microsoft SharePoint 2010 Farm Group Tasks, and then click Configure SharePoint Management Pack.
5) Make sure that the SharePointMP.config file is at the right location. Click Run.
Note: The task will take a few minutes to complete.
6) If there are no errors, close the dialog box.
If the task finishes with no errors, then proceed to next step. Otherwise, fix the problem and rerun the task until it finishes with no errors.
Note: If you have already completed this task for the Microsoft SharePoint Foundation 2010 Management Pack, then after you import the Microsoft SharePoint 2010 Products Management Pack, you have two choices. Either rerun the admin task, or wait for next cycle for discovery and monitoring for Microsoft SharePoint Server 2010 to start.
- After the previous step, discovery will start. Discovery may take a half hour or more to finish running.
- Verify discovery results.
1) In the Operations Manager 2007 management server, open the Operations Console.
2) In the Monitoring tab, navigate to the SharePoint 2010 Products folder.
3) Select the Administration node under the SharePoint 2010 Products folder.
4) Expand the diagram view and review with your SharePoint administrator to ensure that all the services that have been provisioned are discovered, if not, rerun discovery.
Monitor the SharePoint environment for alerts. Some alerts will need you to reset the monitor health status manually and close the alerts after its status changed to critical. Otherwise, the monitor will remain in critical states without sending out new alerts.
The following files are included in this Management Package.
- · Microsoft.SharePoint.Server.2010.mp
- · Microsoft.SharePoint.Foundation.2010.mp
- · Microsoft SharePoint Foundation 2010 Management Pack Guide.docx
- · Microsoft SharePoint Server 2010 Management Pack Guide.docx
- · Microsoft SharePoint Server 2010 Management Pack Readme.htm
- · SharePointMP.Config
- · EULA.rtf
To schedule SharePoint 2010 Products discoveries along with SharePoint Foundation 2010 discoveries, add the following nodes to the WorkflowCycle node in SharePointMP.config:
|
<Workflow Id=”MOSSInstallation.Discovery;WACInstallation.Discovery;SearchExpressInstallation.Discovery;SearchStandardInstallation.Discovery” management pack=”Microsoft.SharePoint.Server.2010″ Type=”Discovery” Times=”1″ /> <Workflow Id=”SPService.Discovery” management pack=”Microsoft.SharePoint.Server.2010″ Type=”Discovery” Times=”4″ /> <Workflow Id=”SPSharedService.Discovery” management pack=”Microsoft.SharePoint.Server.2010″ Type=”Discovery” Times=”4″ /> <Workflow Id=”SPSharedService.Discovery.WAC” management pack=”Microsoft.SharePoint.Server.2010″ Type=”Discovery” Times=”4″ />
|
As a result, the WorkflowCycle node may look like this:
|
<WorkflowCycle BaseStartTime=”+300″ Length=”28800″ Spacing=”60″> <Workflow Id=”WSSInstallation.Discovery” Type=”Discovery” Times=”1″ /> <Workflow Id=”MOSSInstallation.Discovery;WACInstallation.Discovery;SearchExpressInstallation.Discovery;SearchStandardInstallation.Discovery” management pack=”Microsoft.SharePoint.Server.2010″ Type=”Discovery” Times=”1″ /> <Workflow Id=”SPFarm.Discovery” Type=”Discovery” Times=”1″ /> <Workflow Id=”SPService.Discovery” Type=”Discovery” Times=”4″ /> <Workflow Id=”SPSharedService.Discovery” Type=”Discovery” Times=”4″ /> <Workflow Id=”SPService.Discovery” management pack=”Microsoft.SharePoint.Server.2010″ Type=”Discovery” Times=”4″ /> <Workflow Id=”SPSharedService.Discovery” management pack=”Microsoft.SharePoint.Server.2010″ Type=”Discovery” Times=”4″ /> <Workflow Id=”SPSharedService.Discovery.WAC” management pack=”Microsoft.SharePoint.Server.2010″ Type=”Discovery” Times=”4″ /> <Workflow Id=”SPHARule.Discovery” Type=”Discovery” Times=”1″ /> <Workflow Id=”SPHARuleMonitor.Availability;SPHARuleMonitor.Security;SPHARuleMonitor.Performance;SPHARuleMonitor.Configuration;SPHARuleMonitor.Custom” Type=”Monitor” Times=”8″ /> <Workflow Id=”SPHARuleMonitor.SPServer.Availability;SPHARuleMonitor.SPServer.Security;SPHARuleMonitor.SPServer.Performance;SPHARuleMonitor.SPServer.Configuration;SPHARuleMonitor.SPServer.Custom” Type=”Monitor” Times=”8″ /> </WorkflowCycle>
|
The SharePoint 2010 Products Management Pack discovers following service applications and features in addition to discoveries:
- · Access Services
- · Document Conversions Launcher Service
- · Document Conversions Load Balancer
- · Excel Calculation Services
- · InfoPath Forms Service
- · Managed Metadata Web Service
- · One Note Service
- · PerformancePoint Service
- · PowerPoint Web Service
- · Project Server Service
- · Project Server Events Service
- · Project Server Queuing Service
- · Secure Store Service
- · SharePoint Server Search
- · User Profile Service
- · Visio Graphics Service
- · Word Conversion Service
- · Word Viewing Service
Related posts:
Deleted SCOM Default Management Pack (http://blogs.technet.com/b/meamcs/archive/2011/08/21/deleted-scom-default-management-pack.aspx)
Removing SCOM Management Pack Dependencies (http://blogs.technet.com/b/meamcs/archive/2011/08/21/removing-scom-management-pack-dependencies.aspx)