Configuring SharePoint 2010 Monitoring in OM 2007 R2
=======================================

A 4-point strategy will ensure you get this MP configured correctly the first time:

1.  Configure Run As Accounts for each farm you wish to monitor
2. Make sure your Run As Account has the necessary permissions for the discovery and monitoring
3. Update the SharePointMP.config with farm-specific info (That file contains a section called Associations.  It is this section that should be adjusted for multiple farm support). You can also control SPS components monitored from this file - see the SharePoint 2010 MP Guide for instructions
4. Make sure the configured version of this file is present on your RMS (both active and passive nodes if RMS is clustered) before you attempt discovery.

Based on from "SharePoint MP config less than clear"

Config Walkthrough
http://www.systemcentercentral.com/BlogDetails/tabid/143/IndexID/82994/Default.aspx

Tips for Using the SharePoint 2010 MP.

http://blogs.technet.com/b/operationsmgr/archive/2011/03/10/tips-on-using-the-sharepoint-2010-management-pack-for-opsmgr-2007.aspx

Service Monitoring
http://blogs.technet.com/b/berryst/archive/2011/03/26/configuring-scom-r2-management-pack-for-sharepoint-server-2010-monitoring.aspx

SharePoint 2010 Products Management Pack for System Center Operations Manager 2007
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=5c73415d-97ba-4bdc-8e92-2c4ea4507f91&displaylang=en
 
Sharepoint databases are not getting monitored including config database
http://social.technet.microsoft.com/Forums/en/operationsmanagermgmtpacks/thread/d04c8faa-7511-47f8-88d7-2c127d984d61

Supporting multiple farms with SharePoint 2010 management pack

"how can I monitor multiple farms with the SharePoint 2010 management pack" comes up.  The guide says that the MP only supports one farm - but there is a

straightforward way to help the MP manage multiple farms.
 
A file named SharePointMP.config is used to configure the behavior of the SharePoint 2010 management pack.  This file should be on all RMS roles in the given

management group Icluster case).
 
The challenge with monitoring multiple farms is due to the need to have farm administrator permission to do the discovery and monitoring that is used to monitor

SharePoint 2010.  The typical configuration for a single farm has the SCOM admin assuming that the run-as profile is involved and directly manipulating this is a

complex operation for multiple farms.
 
The config file and configuration task included in the MP comes to the rescue here.

That file contains a section called Associations.  It is this section that should be adjusted for multiple farm support.
 
Example:

 
<Association Account="Contoso - SharePoint Farm administrator -3" Type="Agent">
 
    <Machine Name="NT10" />
 
    <Machine Name="NT11" />
 
    <Machine Name="NT12" />
 
    <Machine Name="NT13" />
 
    <Machine Name="NT14" />
 
    <Machine Name="NT15" />
 
  </Association>
 
 
 
  <Association Account="Contoso - SharePoint 2010 Farm Administrator 2" Type="Agent">
 
    <Machine Name="NT64" />
 
    <Machine Name="NT65" />
 
    <Machine Name="NT66" />
 
  </Association>
 
 
 
  <Association Account="Contoso - SharePoint 2010 Farm Administrator" Type="Agent">
 
    <Machine Name="NT77" />
 
    <Machine Name="NT75" />
 
    <Machine Name="NT76" />
 
  </Association>
 
After adjusting the SharePoint configuration file, run the configuration task that is included in the management pack per the instructions found in the guide.

Integration between Orchestrator 2012 and other System Center 2012 Products
http://www.systemcentercentral.com/Forums/tabid/60/indexid/88551/Default.aspx?tag=Forums+Opalis

Problems with PowerShell on 64-bit Action Server

http://www.systemcentercentral.com/Forums/tabid/60/indexid/88448/Default.aspx?tag=Forums+Opalis

Are you looking to integrate with one of the other System Center products that use the 64 bit PShell snap-in (while Opalis uses the 32 bit). Also some more info here:

THe Hard Way
http://blogs.technet.com/b/opalis/archive/2010/11/29/opalis-6-3-running-powershell-scripts-on-64-bit-operating-systems.aspx

http://blogs.technet.com/b/opalis/archive/2010/11/22/opalis-6-3-automating-hyper-v-cluster-patching-using-the-configuration-manager-ip-part-1.aspx

The Easy Way
OIS - Integration Pack for PowerShell Script Execution 1.00

http://opalis.codeplex.com/releases/view/65652

Opalis / Orchestrator Fundamentals

You can read the articles in the series at the link below

·         Opalis Runbook Automation Fundamentals (Part 1) (basics)

·         Opalis Runbook Automation Fundamentals (Part 2) (advanced concepts)

·         Opalis Runbook Automation Fundamentals (Part 3) ( advanced concepts, bridging gaps and extending capabilities )

In this episode we discuss a common issue, that of Console Latency and Database Queueing within Operations Manager. Pete Zerger discusses the most common causes and how to mitigate.

Go to http://systemcenterpodcast.com/shows/inside-central for more information and show notes.

Pete Zerger joins me to discuss the various options that are available for creating custom Reports in Operations Manager. Everything from the developer to the beginner, there is something in this for everyone.

Don't forget to pre-order your copy of Opalis Integration Server 6.5 Unleashed and the new PowerShell 2.0 Bible, both of which Pete is a contributing author.

Stay tuned next week for details on how you can win your own copy of both books.

More information and show notes at http://systemcenterpodcast.com/shows/inside-central