Configuring the SharePoint MP is like installing Certs on a Gateway server…..easy when you know how!
So where to start? Well you need Operations Manager or System Center Essentials and a SharePoint 2010 Solution!
To use this management pack, you must:
· Download the management pack from the System Center Pack Catalog (http://technet.microsoft.com/en-us/systemcenter/cc462790.aspx).
· Have System Center Operations Manager 2007 SP1 deployed in at least one Management Group. A Management Group consists of an Operations Manager 2007 SP1 database, at least one Operations Manager 2007 SP1 Management Server, the Operations Manager 2007 SP1 Operator Console, and managed computers.
· Have the Operations Manager 2007 SP1 agent deployed on all computers that you want to monitor.
· If an agent computer in a SharePoint deployment is running Windows Server 2008, ensure that all the hotfixes mentioned in the Microsoft Support article (http://support.microsoft.com/kb/953141/en-us) are installed on these computers.
For information about deploying Operations Manager 2007 SP1, see the Operations Manager 2007 SP1 Deployment Guide at http://technet.microsoft.com/en-us/library/bb419281.aspx.
For information about how to deploy the Operations Manager 2007 SP1 agent, see “How to Deploy the Operations Manager 2007 SP1 Agent for Agent-Management of Computers” in the Operations Manager 2007 SP1 Online Help at http://technet.microsoft.com/en-us/library/bb309622.aspx.
This section covers security considerations for the management pack. To use this management pack correctly, you must know:
· How to configure the SharePoint Discovery/Monitoring Account Run As profile with Run As accounts that have the correct privileges.
· Whether the management pack provides support for agentless monitoring.
The rules, monitors, tasks and discoveries that are defined in the management pack require credentials to run on a computer. By default, these credentials come from the Default Action Account on each server that has the Operations Manager 2007 SP1 agent installed on it.
The agent is an Operations Manager 2007 SP1 service that runs on each computer that you want to monitor. It captures information from the computer on which it is running, applies rules to the captured data, and performs actions as defined by the rules.
The Default Action Account runs activities such as monitoring and collecting Windows event log data and performance data.
Because the Default Action Account may not have the necessary privileges to accomplish the monitoring activities of the management pack, Operations Manager 2007 SP1 allows you to use Run As profiles and Run As accounts to provide the needed credentials.
When a management pack is created, its discoveries, rules, monitors, and tasks are associated with Run As profiles; the management pack discoveries, rules, monitors and tasks are associated with the SharePoint Discovery/Monitoring Account Run As profile.
Run As accounts allow you to specify the necessary privileges to run the management pack discoveries, rules, monitors, and tasks on specific computers. As an administrator, you can associate Run As accounts with Run As profiles to provide the necessary credentials to run the management pack discoveries, rules, monitors, and tasks.
In order for the management pack to have the necessary credentials to run its rules, monitors, and tasks, you must make the following configuration:
Configuring the management pack
Create a “SharePoint Discovery/Monitoring Account” Run As Account (pick the Display Name 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.
Import the SharePoint MP’s
SharePoint Product Server MP and SharePoint Foundation Server. You can import them via the MP Import wizard.
You can verify this by looking into the Management Pack in the Administration Pane
So in the Monitoring Pane now our newly installed SharePoint 2010 Products MP shows up like this, note they is no SharePoint Foundations, this is merged into the SharePoint 2010 Products MP. But does create two separate entries into the Reporting. I will come back to the Reporting at a later stage.
So now the SharePoint 2010 Products MP is installed we have to configure the MP. It is easy and I believe the really challenges are ahead of us… So lets have a look at getting this MP into working order.
First we need to address some background work in SharePoint and the AD
First let’s create an account just for the purpose of monitoring the SharePoint solution
I am not sure that this next step will be best practice for all companies but I would set the account so a user can’t change the password nor does it expire.
Now with our new account create with only Domain User rights we can go to the SharePoint 2010 Central Administration Site
Select Security from the menu on the right hand side and go into the ‘Manage the farm administrators group’
Select ‘Add Users’
Then click the account to add into the ‘Manage the farm administrators group’ group
Oh nice it will also send a Personal Message if required.
The account is now added into the ‘Manage the farm administrators group’ group so we have our Ops Mgr SharePoint account configured into SharePoint.
That has finished of the work in SharePoint so our focus is back onto Ops Mgr, the reason I created this new and dedicated account is due a error that may pop up with the SPHA rules when you use a administrator account for other services.
We need to add this account into Ops Mgr RunAs Accounts for the next stage in the configuration of the SharePoint MP. I have given it this display name because it is the default name that Microsoft use in the next phase.
Add the username, password and domain.
Restrict the Distribution of this RunAs Account ( I like this feature )
Now navigate to C:\Program Files (x86)\System Center Management Packs\Microsoft SharePoint 2010 Products OpsMgr 2007 MP en-us
Move the SharePointMP.config file from “C:\Program Files (x86)\System Center Management Packs\Microsoft SharePoint 2010 Products OpsMgr 2007 MP en-us” and move it to “ C:\Program Files\System Center Management Packs”
Then we need we need to add our SharePoint detail into the SharePointMP.config file, I left the Association Account the same but under the Machine Name I have added the, in my case 2 SharePoint Server Names into the list. When you have entered the SharePoint Server Names then close and save the changes.
How do I schedule running discovery for SharePoint Foundation 2010 and SharePoint 2010 Products?
Workflow Cycle element specifies the schedule of list workflows. You can have 0, 1, or many Workflow Cycle elements. But if you have multiple Workflow Cycle elements, you should avoid listing the same workflow in different Workflow Cycle elements.
– The BaseStartTime attribute can have value in the form of “HH:mm” or integer. “HH:mm” format works as the start time alignment based on which the cycle repeats. Integer format functions as setting the alignment start time to be the current time plus that many seconds. Be aware that if you set integer value, every time you rerun the admin task, the cycle start time is recalculated.
· The Length attribute specifies the length (in seconds) of each cycle.
· The Spacing attribute specifies the spacing time (in seconds) between one workflow’s timeout time and the next workflow’s start time.
For example, SPFarm.Discovery has timeout 300 and base start time at “14:00”. If the Spacing is 60, the base start time of SPService.Discovery is set to 14:00 + Ceiling[(300 + 60) / 60] = 14:06. If you set negative Spacing, workflows may overlap and cause performance and out of memory problems.
· The WorkflowTimeout attribute (optional) if defined applies to each workflow in the cycle unless being overridden in the Script node.
· If not set, current timeout values are respected.
· The Id attribute of Workflow node is a list of the discovery/monitor Id(s) separated by ‘;’ (for the workflow).
· The MP attribute (optional) of Workflow node is for workflow not defined in the SharePoint Foundation MP.
· The Type attribute of Workflow node indicates the workflow type. Only “Discovery” and “Monitor” are supported.
· The Times attribute of Workflow node specifies how many times the workflow needs to run within a cycle. If you set it to 0 or negative, the workflow is disabled.
· The Timeout attribute (optional) of Workflow node if defined overrides the timeout of the workflow.
In the final stages to configuring the SharePoint we did to run the ‘Configure SharePoint Management Pack”, without completing the above work is will fail.
So expand the SharePoint 2010 Products MP and click “Administration”
Over on the Right you will see the “Actions”
Click on the “Configure SharePoint Management Pack”
These Task will run.
Wait I want to show you this screen shot as this is what you will see if you have a failure. This would mean going back on your config to check each step.
In fact this is the screen shot we are looking for. Success!
Just so you know, nothing is going to happen quickly so be patient for the SharePoint 2010 Products MP pack to propagate.
I will be adding further post to this series, this is just the tip of the iceberg on SharePoint 2010 monitoring.
Simon Skinner MVP