Friday, 10 October 2014

Installing the SharePoint 2013 Management Packs to SCOM

    Installing the SharePoint Management Packs to SCOM
    Contents


    Introduction
    If you need to import a new vendor provided or heavily developed internal sealed Management Pack (i.e. one that contains a large number of rules that could impact the performance of the SCOM system or cause excessive reporting data to be written to the database), please follow these steps:

    Steps

    1. Raise a change!
    Include the following steps:
    2. Download the MP
    Including any documentation related to the MP and save it 
    3. Load the OpsMgr console
    Copy the .msi (Microsoft.Sharepoint.Server.ManagementPacks.msi) to the server and run the .msi




    Verify the following files have been created:












    4. Import the Management Packs
    Go to Administration / Management Packs and click on "Import Management Packs..." action
    Add the MP(s):
















    Click install, confirm it installs successfully:











    The Management Packs are now listed in the Management Packs node:


















    5. Edit the configuration file:
    1. This is called “microsoft.sharepoint.foundation.library.mp.config” and shipped with the management pack files:



    1. Copy and paste to the following location: (This MUST be placed in this specific location.  You might have to create the directory if it does not exist)

    C:\Program Files\System Center Management Packs

    1. Open the microsoft.sharepoint.foundation.library.mp.config file using NotePad, and find the section 


   
< /Association> 

    6. Create the Runas Account
    1. Need to create a RunAs account for the SharePoint 2013 MP to use.  This RunAs account display name MUST match the “Association Account” in the config file

















    à



    NOTE:

    1. Associated user account must have SharePoint 2013 farm administrative privileges and access to the related databases and application programming interface (API). For example, the account used to setup SharePoint Foundation 2013 and run the SharePoint Products and Technologies Configuration Wizard should have the required privileges
    2. UDS-EUR\bt-SPAdminPR-eur-so is the SharePoint Setup Account in Production. The Display name is “SharePoint Administrator Account – Production”
    3. Replace the value "SharePoint Discovery/Monitoring Account" in the config file with the value: “SharePoint Administrator Account – Production”
    1. Open the RunAs account just created – and on the distribution tab – add in the servers that are part of the farm, or SQL servers that host farm databases

    7. Add Server names to Config File
    Next – need to configure the SharePoint config file for the server names for the SharePoint 2013 and SQL servers.  If this file is not edited with specific Farm Server and Database Server names, then SCOM will try and discover SharePoint 2013 on EVERY server in the management group.  It is best to scope this down in advance. 

    1. Open the file in NotePad, and under "Association Account” add a “Machine Name" line for each server in your farm.


      


    < /Association>

    1. Save and close the config file


    8. Run the Configure the Management Pack Task
    1. In the monitoring view – Expand Microsoft SharePoint > Administration and select the “Microsoft SharePoint Farm Group”
    2. In the Tasks pane – run the task “Configure SharePoint Management Pack”
    Note – if the task fails – or throws an error – investigate and ensure you have the config file on your management server, and you are running the console on the management server when calling the task. 
    1. You should see output similar to this:



    Output 
    Load configuration file Microsoft.SharePoint.Foundation.Library.mp.config 
    Configure Microsoft.SharePoint.Foundation.Library version 15.0.4420.1017 
    Create override management pack Microsoft.SharePoint.Foundation.Library.Override 
    Account SharePoint Discovery/Monitoring Account is associated to DB1.opsmgr.net for Microsoft.SharePoint.AdminAccount 
    Account SharePoint Discovery/Monitoring Account is associated to SHPT2.opsmgr.net for Microsoft.SharePoint.AdminAccount 
    Allow DB1.opsmgr.net as a proxy 
    Allow SHPT2.opsmgr.net as a proxy 
    Create 'Enabled' property override with value true for Microsoft.SharePoint.2013.WSSInstallation.Discovery 
    Create 'SyncTime' configuration override with value 18:43 for Microsoft.SharePoint.2013.WSSInstallation.Discovery 
    Create 'IntervalSeconds' configuration override with value 28800 for Microsoft.SharePoint.2013.WSSInstallation.Discovery 
    Microsoft.SharePoint.2013.WSSInstallation.Discovery does not have configuration TimeoutSeconds 
    Create 'SyncTime' configuration override with value 18:45 for Microsoft.SharePoint.2013.SPFarm.Discovery 
    Create 'SyncTime' configuration override with value 18:51 for Microsoft.SharePoint.2013.SPService.Discovery 
    Create 'SyncTime' configuration override with value 18:57 for Microsoft.SharePoint.2013.SPSharedService.Discovery 
    Create 'SyncTime' configuration override with value 19:03 for Microsoft.SharePoint.2013.SPHARule.Discovery 
    Create 'SyncTime' configuration override with value 19:09 for Microsoft.SharePoint.2013.SPHARuleMonitor.Availability 
    Create 'SyncTime' configuration override with value 19:09 for Microsoft.SharePoint.2013.SPHARuleMonitor.Security 
    Create 'SyncTime' configuration override with value 19:09 for Microsoft.SharePoint.2013.SPHARuleMonitor.Performance 
    Create 'SyncTime' configuration override with value 19:09 for Microsoft.SharePoint.2013.SPHARuleMonitor.Configuration 
    Create 'SyncTime' configuration override with value 19:09 for Microsoft.SharePoint.2013.SPHARuleMonitor.Custom 
    Create 'SyncTime' configuration override with value 19:15 for Microsoft.SharePoint.2013.SPHARuleMonitor.SPServer.Availability 
    Create 'SyncTime' configuration override with value 19:15 for Microsoft.SharePoint.2013.SPHARuleMonitor.SPServer.Security 
    Create 'SyncTime' configuration override with value 19:15 for Microsoft.SharePoint.2013.SPHARuleMonitor.SPServer.Performance 
    Create 'SyncTime' configuration override with value 19:15 for Microsoft.SharePoint.2013.SPHARuleMonitor.SPServer.Configuration 
    Create 'SyncTime' configuration override with value 19:15 for Microsoft.SharePoint.2013.SPHARuleMonitor.SPServer.Custom 
    SharePoint management pack configuration completed successfully

    NOTE:

    This task is really a “discovery helper”.  It will create the necessary RunAs profile associations to the RunAs account for each server, and it will enable agent proxy for each server, and will create some overrides to space out all the discoveries so they run in order, and can discover all Farm components as quickly as possible.   From the time you run the task, to full Farm, Role, Server, and Service discovery, should be around 40 minutes

    After 40 minutes – check in the console and see if your Farm, Servers, and Services have all been discovered.  If not – check in the “Unidentified machines view”.  If your farm servers show up there, it is likely a permissions issue with your RunAs account, either on the Farm servers or on the SQL server.  On the SharePoint servers, make sure this account can log in and execute the SharePoint command shell without errors



    Backout

    To remove the MPs – delete from the console in following order:
    1. Overrides
    2. Microsoft SharePoint Server 2013 (Monitoring)
    3. Microsoft SharePoint Server 2013 (Discovery)
    4. Microsoft SharePoint Server Core Library
    5. Microsoft SharePoint Foundation (Monitoring)
    6. Microsoft SharePoint Foundation (Discovery)
    7. Microsoft SharePoint Foundation Core Library






No comments:

Post a Comment