MS-Opsmgr

Microsoft System Center Operations Manager

SCOM 2016 – Install System Center Operations Manager 2016 – Part 6

In this series off blog post I am going to take you true the steps I took to install System Center Operations Manager 2016. The Environment will be installed using the following software:

  • Microsoft Windows Server 2016 – Download from here
  • Microsoft SQL Server 2016 – Download from here
  • System Center Operations Manager 2016 – Download from here

My Test environment consist of the following servers,

  • DC01 – Domain Controller
  • SQL01 – Microsoft SQL 2016 server
  • DATA01 – Data Server
  • MS01 – Scom Management Server 01
  • MS02 – Scom Management Server 02
  • MS03 – Scom Management Server 03 | Audit Collection Service
  • SQLRPS01 – SQL Reporting Service 01
  • WEB01 – Scom Web Console Server,
  • WAP01 – Web Applications Proxy.

 

Here you can find the previous blogposts

In this part we are going to install System Center Operations Manager Audit Collections Services. I installed a third management server in my environment. On how to install a management server please have a look at Part 2.

When the management server is installed. Let’s start by installing audit collection service.

  1. On the “Operations Manager” page, click “Audit Collection Services
    acs01

  2. On the “Audit Collection Services Collector Setup” page, in the “Welcome to the audit collection Service setup Wizard” section click “Next
    acs02

  3. On the “Audit Collection Services Collector Setup” page,  in the “Microsoft Software License Terms” section click “I accept the license terms” and click “Next
    acs03

  4. On the “Audit Collection Services Collection Setup” page in the “Database Installation Options” section select “Create a new database” and click “Next
    acs04

  5. On the “Audit Collection Services Collection Setup” page, in the “Data Source” section click “Next
    acs05

  6. On the “Audit Collection Services Collector Setup” page, In the “Database” section select “Remote database Server” and enter the name of you SQL server. In my configuration it looks like this:
    acs06

  7. On the “Audit Collection Services Collector Setup” page, in the “Database Authentication” section select “Windows Authentication” and click “Next
    acs07

  8. On the “Audit Collection Services Collector Setup” page, in the “Database Creation” section select “Use SQL Servers default data and log file directories” and click “Next
    acs08

  9. On the “Audit Collection Services Collector Setup” page, in the “Event Retention Schedule” section click “Next
    acs09

  10. On the “Audit Collection Services Collector Setup” page, in the “ACS Stored Timestamp Format” section, select “Local” and click “Next
    acs10

  11. On the “Audit Collection Services Collector Setup” page, in the “Summary” section click “Next
  12. On the “Audit Collection Services Collector Setup” page, in the “Audit collection services has been successfully installed” click “Finish
    acs11

When you start the System Center Operations Manager Console and you expand Microsoft Audit Collection Services, Collector and click the state view you should see something like this:

acs12

Next we need to deploy the ACS reporting Services.

  1. On your reporting server in my case "SQLRP01" create a temporary folder "C:\ACS"
  2. On the Installation Media browse to “ReportModels\acs” and copy all the files and directories to the above created directory
  3. Open a command prompt window by using "Runs as Administrator" and change the directory to the "Acs" directory
    acs13
  4. Enter the following command “UploadAuditReports “SQLRP01\MSSQLSERVER” “http://sqlrp01/ReportServer$MSSQLSERVER” “D:\ACS”
    acs14

When finished the results should look something like this:

acs16

This completes this part off the series installing System Center Operations Manager 2016. In the next part we are going to install the Gateway

SCOM 2016 – Install System Center Operations Manager 2016 – Part 1

In this series off blog post I am going to take you true the steps I took to install System Center Operations Manager 2016. The Environment will be installed using the following software:

  • Microsoft Windows Server 2016 – Download from here
  • Microsoft SQL Server 2016 – Download from here
  • System Center Operations Manager 2016 – Download from here

My Test environment consist of the following servers,

  • DC01 – Domain Controller
  • SQL01 – Microsoft SQL 2016 server
  • DATA01 – Data Server
  • MS01 – Scom Management Server 01
  • MS02 – Scom Management Server 02
  • WEB01 – Scom Web Console Server,

Here you can find the rest of the blogposts.

Before we can deploy System Center Operations Manager 2016 we need to deploy a instance of Microsoft SQL Server 2016. This instance will be located on a separated computer.

Before we can install Microsoft SQL Server 2016 we need to create group managed service accounts. I used the following steps to create the managed service accounts:

  1. Start “Active Directory Users and Computers” and create a “Group” whit a Group Scope “Global” and the  Group type “Security”. Give the group a logical name In my case “SG- Sql2016Agents", and click “OK
    Install and Configure SQL for System Center Operations Manager 2016
  2. Open the properties off the above created group and add the domain member servers that will be hosting the SQL Server instances that will be using the group managed service accounts.
    Install and Configure SQL for System Center Operations Manager 2016
  3. On your “Domain Controller” run a “PowerShell” command prompt as administrator and run the following command:

    Install and Configure SQL for System Center Operations Manager 2016

     

  4. On your “Domain Controller” run a “PowerShell” command prompt as administrator and enter the following command: 

    Install and Configure SQL for System Center Operations Manager 2016

  5. Next we need to grand the created group managed service account the right to “Validated write to service principal name” permission:
    • In “Active Directory Users and Computers”, click “View” and check “Advanced Features”.Install and Configure SQL for System Center Operations Manager 2016
    • In “Active Directory Users and Computers”, right click on the domain and go to “Properties” and click on the “Security” tab.
    • On the “Security” tab click “Advanced
    • On the “Advanced Security settings for <Domain>”  page, on the “Permissions” tab click “Add
    • On the “Permission Entry for <Domain>” page, at the top, click the “Select a principal” link
    • On the “Select User, Computer, Service Account, or Group” page, click “Object Types
    • On the “Object Types” page, select “Service Accounts” and click “OK
    • On the “Select User, Computer, Service Account or Group” page, enter the name of de service you created above and press “Enter
    • On the “Permission Entry for <Domain>” in the “Applies to” section select “Descendant Computer Objects
    • On the “Permission Entry for <Domain>” page in the “Permissions” section select “Validated write to service principal name” and click “OKInstall and Configure SQL for System Center Operations Manager 2016
    • Click “OK” three times to close all dialogs

    After completing the the above steps the result should look something like this:

    Install and Configure SQL for System Center Operations Manager 2016

     

  6. On your “Domain Controller” run a “PowerShell” command prompt as administrator and enter the following command:

  7. Next we need to grand the created group managed service account the right to “Validated write to service principal name” permission. See "Step 5"
  8. On your “Domain Controller” run a “PowerShell” command prompt as administrator and enter the following command:

  9. Next we need to grand the created group managed service account the right to “Validated write to service principal name” permission. See "Step 5"
  10. On your “SQL Server” install the AD module for PowerShell.

    Install and Configure SQL for System Center Operations Manager 2016

  11. When rebooting the “SQL Server” the Group Managed Service accounts are configured on the Server. You can check if the Group managed Service accounts are installed using the following command:

    The result should look something like this:

    Install and Configure SQL for System Center Operations Manager 2016

     

Know that the Service accounts for SQL are created lets start by installing SQL Server 2016

  1. On the “SQL Server Installation Center” page click “Installation” and click “New SQL Server Stand-Alone installation or add features to an existing Installation

    Install and Configure SQL for System Center Operations Manager 2016

  2. On the “SQL Server 2016 Setup” page, in the “Product Key” section enter a Product key click “Next

    Install and Configure SQL for System Center Operations Manager 2016

  3. On the “SQL Server 2016 Setup” page,, in the “License Terms” section click “I Accept the license terms” and click “Next

    Install and Configure SQL for System Center Operations Manager 2016

  4. On the “SQL Server 2016 Setup” page, on the “Microsoft update” section click “Use Microsoft Update to check for Updates (Recommended)” and click “Next

    Install and Configure SQL for System Center Operations Manager 2016

  5. On the “SQL Server 2016 Setup” page, in the “Product Updates” section click “Next

    Install and Configure SQL for System Center Operations Manager 2016

  6. On the “SQL Server 2016 Setup” page, on the “Install Rules” section click “`Next

    Install and Configure SQL for System Center Operations Manager 2016

  7. On the “SQL Server 2016 Setup” page, in the “Feature Selection” select the following and click “Next”:
    • Database Engine Service
    • Full-Text Extraction for fast text search
    • Reporting Services – Native

    In my environment I changed the paths to where I wanted to install SQl. Install and Configure SQL for System Center Operations Manager 2016

  8. On the “SQL Server 2016 Setup” page, in the “Feature Rules” section click “NextInstall and Configure SQL for System Center Operations Manager 2016
  9. On the “Sql Server 2016 Setup” page, in the “Server Configuration” section on the “Service Accounts Tab” add the above created service accounts to wright service. The result should look something like this:Install and Configure SQL for System Center Operations Manager 2016
  10. On the “Sql Server 2016 Setup” page, in the “Server Configuration” section on the  “Collation” tab make sure that “SQL_Latin1_General_CP1_CI_AS” is selected and click “NextInstall and Configure SQL for System Center Operations Manager 2016
  11. On the “SQL Sever 2016 Setup” page, in the “Database Engine Configuration” section click “Next” In my environment I added a group off SQL Administrators which are allowed off managing the SQL Server.Install and Configure SQL for System Center Operations Manager 2016
  12. On the “SQL Server 2016 Setup” page, on the “Reporting Services Configuration” section make sure “Install and Configure” is selected and click “NextInstall and Configure SQL for System Center Operations Manager 2016
  13. On the “SQL Server 2016 Setup” page, on the “Ready to Install” section click “InstallInstall and Configure SQL for System Center Operations Manager 2016
  14. On the “SQL Server 2016 Setup” page, on the “Complete” section click “CloseInstall and Configure SQL for System Center Operations Manager 2016

This completes the first post in a series of post where we install System Center Operations Manager 2016. In the next post we are going the install all the prerequisites and create all the service accounts.

Update MP: System Center Management Pack for SQL Server and Dashboards

On 10-October-2016 Microsoft released update for the System Center Management Pack for SQL Server and Dashboards. The version is updated to 6.7.7.0

  • Microsoft System Center Management Pack for SQL Server 2016 The features and fixes that are included in this update:
    • Feature: Updated the visualization library
    • Fix: "Set DB offline" task does not work when the database is in Availability Group
    • Fix: Always On console task does not work
  • Microsoft System Center Management Pack for SQL Server 2014 Feature overview is the same as above
  • Microsoft System Center Management Pack for SQL Server The features and fixes that are included in this update:
    • Fix: SQL Server 2012 Always On discoveries fail after stopping WSFC service
    • Fix: “Set DB offline” task does not work when the database is in Availability Group
    • Fix: user policy discovery script fails with “Invalid namespace "ROOT\Microsoft\SqlServer\ComputerManagement12"’ error
    • Fix: Always On console task does not work
    • Feature:Updated the visualization library
  • Microsoft System Center Management Pack for SQL Server Dashboards The features and fixes that are included in this update:
    • Feature: Restored the correct group order in SQL Server Summary dashboard views
    • Fix: expanding “arrow” has low-contrast color when a health group is collapsed in Instance view (High-Contrast #2 color scheme)
    • Fix: In Web console, Dashboards continuously send requests to the database
    • Fix: not the first object gets selected in the object list after drill-down
    • Fix: on Web console, Dashboards crash when drilling down from Datacenter view to Instance view
    • Fix: horizontal scroll position resets after refreshing the Instance view
    • Fix: “No Data” message is displayed on some tiles after upgrading Dashboards management pack from version 6.7.2.0 to 6.7.4.0 or later version
    • Fix: on Web console, Dashboards crash when drilling down from Datacenter view to Instance view

Before installing in the updates in your production environment make sure that you test these updates in your test environment.

Building a Management pack using VSAE Part 1.

In this blog post I’m going to take you thru the steps I took to build a management pack using Microsoft Visual Studio Community 2015 in combination whit the Visual Studio Authoring Extensions.

You can download the Visual Studio Community 2015 from here. The Visual Studio Authoring Extensions can be downloaded from here

The application I am going to monitor is Commvault Simpana Version 10 r2. Commvault Simpana is backup application which I use for backing up my environment. More information on Commvault Simpana can be found here.

The application is consist of the following components:

  • CommServe: This component creates the SQL Database that communicates whit all clients and coordinates all operations whit in the CommCell   environments, such as backups, restores, copies and media management operations. Along whit the CommServe software, the following components are automatically installed.
    • CommCell Console: The console is a graphical user interface that allows you to control and manage CommCell operations.
    • Files System: The File system component enables the back-up and restore of files and folders residing on the CommServe computer.
    • Web Server and Web Console:  if the Internet Information Services (IIS) is enabled on the computer, the Web Server component is installed along whit the Web Console Component. The Web Console is a web based application that allows end-users manage their data.
    • Workflow:  Tool that allows you to automate business processes by putting together a set of tasks in a specific order.
  • MediaAgent: This component manages the transmission of data between clients and backup media. Install the MediaAgent component on a Windows or UNIX computer that is configured with the backup media. The backup media is a storage device where you want to store your backed up data.
  • Agent: The Simpana software provides a range of installable components that support the type of data that you want to protect. These components are referred to as agents.

Now that the we know how the application works its time to create a service model for the application. My service model look something like this:

CommVaultSimpanaManagementPackBasicComponent

Creating the Management Pack

  1. Start the “Visual Studio 2015
  2. In the “Microsoft Visual Studio” console in the “Menu” click “File”,”New” and click “Project
    Microsoft Visual Studio - File - New - Project
  3. In the “New Project” console, expand “templates”, “Management Pack”, “Operations Manager”. From the middle click “Operations Manager 2007 r2 Management Pack”. Enter the following data:
    • "Name:" Simpana.CommVault
    • "Location:" D:\Management Pack\Simpana CommVault\
    • "Solution Name" Simpana.CommVault

    Visual Studio - New ProjectClick “Ok” to create the management pack.

  4. In the “Microsoft Visual Studio” console in the “Solution Explorer” right click “Simpana.CommVault” and click “Properties
    Visual Studio - Solution Explorer - Properties
  5. In the “Microsoft Visual Studio” console, on the “Simpana.CommVault” tab click “Build” and select “Generate sealed and Signed Management Pack” Insert the following:
    • "Company Name:" Ms-opsmgr.eu
    • "Copyright:" Copyright (c) Ms-opsmgr.eu. All rights reserved.
    • "Key File:" Simpana.CommVault.snk. If you don’t know how to create a Key File for signing and sealing a management pack take a look at the following blogpost

    Visual Studio - Simpana.Commvault Properties - Build

  6. In the “Microsoft Visual Studio” Console, on the “Simpana.CommVault” tab click “Management Group”, click “Add
  7. In the “Add Management Server….” wizard, enter the “Server Name” and click “Add Server
  8. In the “Microsoft Visual Studio” Console, on the “Simpana.CommVault” tab the result should look something like this:
    Visual Studio - Simpana.CommVault - Management Group
  9. In the “Microsoft Visual Studio” console, on the “Simpana.CommVault” tab click “Deployment”. In the “Start action” select “Deploy projects to default management group only
    Visual Studio - Simpana.CommVault - Deployment
  10. In the “Microsoft Visual Studio” console, in the “Menu” click “File”, “Save

Create a Management Pack Fragment

In this part we are going to create a management pack fragment to give the management pack a friendly name and description when we look in the administration of System Center Operations Manager

  1. In the “Microsoft Visual Studio” console, in the “Solution Explorer” right click “Simpana.CommVault” and click “Add”, “New Item
    VisualStudioNewFragment1
  2. In the “Add New Item – Simpana.Commvault” wizard select “Empty Management Pack Fragment” Enter the following data and click “Add
    • "Name:" Simpana.CommVault.Project

    VisualStudioNewFragment2

  3. In the “Microsoft Visual Studio” console, on the “Simpana.CommVault.Project.mpx” tab enter the following code:
  4. In the “Microsoft Visual Studio” console, in the “Menu” click “File”, “Save
  5. In the “Microsoft Visual Studio” console, in the “Menu” click “Build”, “Build Solution

    Visual Studio - Build - Build Solution

  6. In the “Microsoft Visual Studio” console, on the “Standard” menu bar click “Start” to deploy the management pack.

    Visual Studio - Deploy

  7. Start the “System Center Operations Manager” console click “Administration” and click “Management Pack” and the result should look something like this:

    VisualStudioNewFragment5

Create the Classes whit the base class Windows Computer Roles.

In this part we are going to create the classes that are based on the Windows Computer Role Class. The following classes are going to be created:

  • Abstract Class: CommServe
    • CommCell Console
    • File System
    • Workflow
  • Abstract Class: Media Agents
    • Agent Exchange
    • Agent SharePoint
    • Agent SQL
    • Agent File System

Schematic it will look something like this:

Classes Based On Windows Computer Role

  1. In the “Microsoft Visual Studio” console, in the “Solution Explorer” right click “Simpana.CommVault” and click “Add”, “New Folder

    Visual Studio - Create New Folder

  2. In the “Microsoft Visual Studio” console. in the “Solution Explorer” name the new Folder “Service Model
  3. In the “Microsoft Visual Studio” console, in the “Solution Explorer” on the folder “Service Model” Right click the folder and click “Add”, “New Folder

    VisualStudioNewFolder2

  4. In the “Microsoft Visual Studio” console, in the “Solution Explorer” name the new folder “Classes
  5. In the “Microsoft Visual Studio” console, in the “Solution Explorer” on the folder “Classes”, right click the folder and click “Add”, “New Item
  6. In the “Microsoft Visual Studio” console, in the “Add New Item – Simpana.Commvault” screen select “Class”. Enter the following data and click “Add”:
    • "Name:" ComputerRoles.mpx

    Visual Studio - Create Class - ComputerRoles.mpx

  7. In the “Microsoft Visual Studio” console, on the “ComputerRoles.mpx” tab enter the following code:

  8. In the “Microsoft Visual Studio” console, in the “Solution Explorer” on the folder “Classes”, right click the folder and click “Add”, “New Item
  9. In the “Microsoft Visual Studio” console, in the “Add New Item – Simpana.Commvault” screen select “Class”. Enter the following data and click “Add”:
    • "Name:" Commserve.mpx

    Visual Studio - Create Class - CommServe.mpx

  10. In the “Microsoft Visual Studio” console, on the “CommServe.mpx” tab enter the following code:

  11. In the “Microsoft Visual Studio” console, in the “Solution Explorer” on the folder “Classes”, right click the folder and click “Add”, “New Item
  12. In the “Microsoft Visual Studio” console, in the “Add New Item – Simpana.Commvault” screen select “Class”. Enter the following data and click “Add”:
    • "Name:" MediaAgent.mpx
  13. In the “Microsoft Visual Studio” console, on the “MediaAgent.mpx” tab enter the following code:

  14. In the “Microsoft Visual Studio” console, in the “Menu” click “File”, “Save
  15. In the “Microsoft Visual Studio” console, in the “Menu” click “Build”, “Build Solution
  16. Start the “System Center Operations Manager” console click “Monitoring” and select “Discovered Inventory” and from the “Tasks” pane click “Change Target Type

    Operations Manager Console - Change Target Type

  17. In the “Select Items to target” screen, select “View all targerts” and in the “Look for” bar enter “Simpana”. The result should look something like this: 
    Select Items to Target - Simpana Commvault

Create the Rollups to create a Health service Rollup

In this part we are going to create the classes that are used to create the health service rollup and create the containment relations between the rollups. The following rollups are created: 
CommVault Simpana - Containments

  1. In the “Microsoft Visual Studio” console, in the “Solution Explorer” on the folder “Classes”, right click the folder and click “Add”, “New Item
  2. In the “Microsoft Visual Studio” console, in the “Add New Item – Simpana.Commvault” screen select “Class”. Enter the following data and click “Add”:
    • "Name:" Rollups.mpx

    VisualStudio - Rollups.mpx

  3. In the “Microsoft Visual Studio” console, on the “Rollups.mpx” tab enter the following code:

  4. In the “Microsoft Visual Studio” console, in the “Solution Explorer” on the folder “Classes”, right click the folder and click “Add”, “New Item
  5. In the “Microsoft Visual Studio” console, in the “Add New Item – Simpana.Commvault” screen select “Relationship”. Enter the following data and click “Add”:
    • "Name:" Containments.mpx

    VisualStudioContainments1

  6. In the “Microsoft Visual Studio” console, on the “Containments.mpx” tab enter the following code:

Create the Dependencies relationships

In this part we are going to create the depend relationships for webserver and Web console and SQL Server. The following rollups are created:

CommVault Simpana - Dependecies

  1. In the “Microsoft Visual Studio” console, in the “Solution Explorer” Right click “References” and click “Add Reference

    Visual Studio - Add Reference

  2. In the “Add Reference” screen, click on the “Browse” tab and go to the “C:\Program Files (x86)\System Center Visual Studio Authoring Extensions\References\OM2007R2” select “Microsoft.SystemCenter.InstanceGroup.Library.mp” and click “Ok

    VisualStudio - Add Reference

  3. In the “Microsoft Visual Studio” console, in the “Solution Explorer” select “Microsoft.SystemCenter.InstanceGroup.Library.mp” and in the properties screen change  the “Alias” to “InstanceGroup

    VisualStudio -Change Alias

  4. Repeat step 2 and 3 for the “Microsoft.SQLServer.Library.mp” and change the “Alias” to “SQL
  5. Repeat step 2 and 3 for the “Microsoft.Windows.InternetInformationServices.2012.mp” and change the “Alias” to “IIS2012r2
  6. In the “Microsoft Visual Studio” console, in the “Solution Explorer” on the folder “Classes”, right click the folder and click “Add”, “New Item
  7. In the “Microsoft Visual Studio” console, in the “Add New Item – Simpana.Commvault” screen select “Relationship”. Enter the following data and click “Add”:
    • "Name:" Dependecies.mpx

    Visual Studio - Dependecies

  8. In the “Microsoft Visual Studio” console, on the “Dependecies.mpx” tab enter the following code:

          

  9. In the “Microsoft Visual Studio” console, in the “Menu” click “File”, “Save
  10. In the “Microsoft Visual Studio” console, in the “Menu” click “Build”, “Build Solution

This concludes the first part of building a management pack using Visual studio authoring extensions. If you want to learn more I advise you to follow the training from Brain Wren on the Microsoft Virtual Academy

Update MP: Microsoft Azure SQL Database Management Pack for System Center 2012

On 6-June-2016 Microsoft released update for the Microsoft Azure SQL Database Management Pack for System Center 2012 . The version is updated to 1.6.1.0

  • Microsoft Azure SQL Database Management Pack for System Center 2012 The features and fixes that are included in this update:
    • Feature: Added a number of new monitors and rules, including the following:
      • CPU Usage (%)
      • Workers Usage (%)
      • Log write (%)
      • Data I/O (%)
      • Sessions (%)
      • Count Failed Connection
      • Count Successful Connection
      • Count Connection Blocked by Firewall
      • Count of Deadlock
      • Count Throttling long transaction
      • Count Connection Failed
      • XTP Storage (In-memory OLTP Storage, %)
    • Fix: Deprecated Collect Microsoft Azure SQL Database Internal/External Network Egress/Ingress performance rules
    • Fix: Deprecated Federation and Federation member workflows
    • Feature: Implemented rebranding: the management pack and some workflow names have been changed

Before installing in the updates in your production environment make sure that you test these updates in your test environment.

Install and Configure System Center Management Pack for SharePoint Server 2013

In this post I’m going to take you true the steps I took to install and configure the system center management pack for SharePoint server 2013. Before installing the system center management pack for SharePoint server 2013 let’s take a look ad the environment that I want to monitor

  • 2 SharePoint Web Front-End servers
  • 1 SharePoint Application server
  • 2 Microsoft SQL 2012 server

You can download the system center management pack for SharePoint server 2013 from here

Before you start installing the system center management pack for SharePoint 2013 make you sure you have installed and configured the following management pack’s:

  • System Center Management Pack for Windows Server Operating System which can be downloaded from here
  • Microsoft System Center Management Pack for SQL Server which can be downloaded from here
  • System Center 2012 Management Pack for Microsoft Windows Server 2012 Internet Information Service 8 which can be downloaded from here

I took the following steps

  1. Install the system center management pack for SharePoint 2013
  2. Import the system center management pack for SharePoint 2013
  3. Copy the configuration file
  4. Create a Run-As account
  5. Give the Run-As account full access to the SQL Servers 
  6. Give the Run-As account farm admin rights to your SharePoint environment
  7. Configure the SharePoint config file
  8. Configure the SharePoint management pack

1. Install the system center management pack for SharePoint 2013

  1. Click "Microsoft.Sharepoint.Server.ManagementPacks.msi"
  2. In the “Microsoft.SharePoint.Server.ManagementPacks – installer” wizard, on the “License Agreement” page, select “I accept” and click “Next
    Install SharePoint Server Management Pack
  3. In the “Microsoft.SharePoint.Server.ManagementPacks – installer” wizard, on the “Select Installation Folder” page, select “Everyone” and click “Next
    Install SharePoint Server Management Pack
  4. In the “Microsoft.SharePoint.Server.ManagementPacks – installer” wizard, on the “Confirm Installation” page, click “Install
    Install SharePoint Server Management Pack
  5. In the “Microsoft.SharePoint.Server.ManagementPacks – installer” wizard, on the “Installation Complete” page, click “Close
    InstallSharePointMP4

2. Import the system center management pack for SharePoint 2013

  1. Start the "Operations Manager Console"
  2. In the “Operations Manager Console” click “Administration
  3. Right click “Management Packs”, and the click “Import Management Packs
    Import Management Packs
  4. The “Import Management pack wizard” opens. Click “Add”, and the click “Add from Disk
    Import Management Packs
  5. The Select Management Packs to import dialog box appears. If necessary, change to the directory that holds your management pack file. Select the following files:
    • Microsoft.SharePoint.Foundation.Library.mp
    • Microsoft.SharePoint.Foundation.2013.Discovery.mp
    • Microsoft.SharePoint.Foundation.2013.Monitoring.mp
    • Microsoft.SharePoint.Server.Library.mp
    • Microsoft.SharePoint.Server.2013.Discovery.mp
    • Microsoft.SharePoint.Server.2013.Monitoring.mp
      Import Management Packs
  6. In the “Import Management Pack” wizard, Click “Install
  7. In the “Import Management Pack” wizard, Click “Close

3. Copy the configuration file

  1. Make a RDP connection to your “Management Server
  2. From the directory “C:\Program Files (x86)\System Center Management Packs\Microsoft.Sharepoint.Server.ManagementPacks” copy the file “microsoft.sharepoint.foundation.library.mp” with the type config to the directory “C:\Program Files\System Center Management Packs

4. Create a Run-As accounts

  1. Start the “Operations Manager Console
  2. In the "Administration" Workspace, in the Navigation pane, expand "Run As Configuration", right click "Accounts" and click "Create Run As Account"

    Create Run As Account

  3. In the “Create Run As Account Wizard”, on the “Introduction” page, click “Next
  4. In the “Create Run As Account Wizard”, on the “General Properties” page enter the following “Display Name” “SharePoint Discovery/Monitoring Account” and click “NextCreate Run As Account
  5. In the “Create Run As Account Wizard”, on the “Credentials” page enter the “Username”, “Password”, “Confirm password”, “Domain” and click “Next
    Create Run As Account
  6. In the “Create Run As Account Wizard”, on the “Distribution Security” page, select “More Secure” and click “Create
    Create Run As Account
  7. In the “Create Run As Account Wizard”, on the “Completion” page, click “Close
  8. Right click on the “SharePoint Discovery/Monitoring Account” and click “Properties
    Create Run As Account
  9. On the “Run As Account Properties – SharePoint Discovery/Monitoring Account” page open the tab “Distribution
    Create Run As Account
  10. On the “Run As Account Properties – SharePoint Discovery/ Monitoring Account” page on the “Distribution” tab, click  “Add”  to add all the SharePoint farm computers.
    Create Run As Account
  11. On the “Run As Account Properties – SharePoint Discovery/Monitoring Account” page, on the “Distribution” tab click “Apply” and the “OK

5. Give the Run-AS accounts full access to the SQL Servers 

  1. Make a RDP connection to your “SQL Server” hosting your SharePoint databases
  2. Start the “Server Manager
  3. In the “Server Manager” in the tools menu click “Computer Management
    SQL Computer Management Local User
  4. On the “Computer Management” page, expand “Local Users and Groups” and click “Groups
  5. On the “Computer Management” page, open the “Administrators” group
    SQL Computer Management Local User
  6. On the “Administrators Properties” page click “Add” and add the user you used to create your Run As account.
  7. On the “Administrators Properties” page click “Apply” and click “OK
  8. On the SQL server start the “Microsoft SQL Server Management Studio
    SQL Full Access Database
  9. In the “Connect tot server” page enter the “Server name” your “Authentication” and click “Connect
  10. In the “Object Explorer” expand “Security”, and right click “Logins” and click “New Login
    SQL Full Access Database
  11. On the “New Login” page, on the “General” page add the above created account
    SQL Full Access Database
  12. On the “New Login” page, on the “Server Roles” page, select “Sysadmin” and click “Ok
    SQLFullAccess6
  13. Repeat the above steps on all your SQL Servers.

6. Give the Run-As account farm admin rights to your SharePoint environment

I am not a SharePoint  administrator so I contacted my SharePoint Administrator to give the monitoring account farm admin right to the SharePoint farm.

7. Configure the SharePoint config file

  1. Open the “microsoft.sharepoint.foundation.library.mp.config” SharePoint configuration file from the following location: “C:\Program Files\System Center Management Packs
  2. In edit the following rule:
    <Association Account="SharePoint Discovery/Monitoring Account" Type="Agent">
        <Machine Name="" />
    </Association>
  3. add a “Machine Name” line for each server in your farm. I have 5 servers that are in my farm so my Config file looks something like this:
    <association type="Agent" account="SharePoint Discovery/Monitoring Account">
        <machine name="web01.ms-opsmgr.eu" />
        <machine name="web02.ms-opsmgr.eu" />
        <machine name="sql01.ms-opsmgr.eu" />
        <machine name="sql02.ms-opsmgr.eu" />
        <machine name="app01.ms-opsmgr.eu" />
    </association>
  4. Save and close the configuration file

8. Configure the SharePoint management pack

  1. Start the “Operations Manager Console
  2. In the “Monitoring” workspace expand “”Microsoft SharePoint” and select “Administration” and from the administration pane select “Microsoft SharePoint Farm Group

    SharePoint Configuration

  3. From the “Tasks” pane, click “Configure SharePoint Management Pack

    Sharepoint Configuration

  4. On the “Run Task – Configure SharePoint Management Pack” click “Run

    SharePoint Configuration

  5. The result should look something like this:

    Sharepoint Configuration

    When everything is finished the result should look something like this.

    Finished

    When you want more information of installing and configuring the SharePoint Management pack please take a look at:

    Update MP: Microsoft System Center Management Pack for SQL Server

    On 18-November-2015 Microsoft released update for the SQL Management Pack. The version is updated to 6.6.7.6.

    • Microsoft System Center Management Pack for SQL Server 2014 Analysis Services The features and fixes that are included in this update:
      • Feature: Added timeout support for every non-native workflow
      • Fix: the discoveries; now the last items can be undiscovered
      • Fix: module error collection on cluster instances to reduce the noise
      • Fix: bug when SSAS Monitoring Pack could not collect OS performance counters with localized names
      • Fix: CPU usage alert description
      • Fix: Blocking Session Monitor – in some situations it could calculate blocking sessions incorrectly
      • Fix: Win10 support: fixed OS version detection issue
      • Improvements: Updated discoveries to throw errors in case of some problems detected during the discovery
      • Improvements: Changed defaults for CPU Usage monitor, added sampling to Memory Usage on the server monitor
      • Improvements: Simplified the dashboard to make it quicker and more informative
      • Improvements: Reviewed and updated the Knowledge Bases
    • Microsoft System Center Management Pack for SQL Server 2012 Analysis Services The features and fixes that are included in this update are:
      • Feature: Added timeout support for every non-native workflow
      • Fix: the discoveries; now the last items can be undiscovered
      • Fix: module error collection on cluster instances to reduce the noise
      • Fix: bug when SSAS Monitoring Pack could not collect OS performance counters with localized names
      • Fix: CPU usage alert description
      • Fix: Blocking Session Monitor – in some situations it could calculate blocking sessions incorrectly
      • Fix: Win10 support: fixed OS version detection issue
      • Improvements: Updated discoveries to throw errors in case of some problems detected during the discovery
      • Improvements: Changed defaults for CPU Usage monitor, added sampling to Memory Usage on the server monitor
      • Improvements: Simplified the dashboard to make it quicker and more informative
    • Microsoft System Center Management Pack for SQL Server 2008 Analysis Services The features and fixes that are included in this update are:
      • Feature: Added timeout support for every non-native workflow
      • Fix: the discoveries; now the last items can be undiscovered
      • Fix: module error collection on cluster instances to reduce the noise
      • Fix: bug when SSAS Monitoring Pack could not collect OS performance counters with localized names
      • Fix: the discoveries, now the last items can be undiscovered
      • Fix: "Memory consumed by other processes (%)" rule having no Run As profile for DS; added SQL MP default Run As to the data source
      • Fix: "Failing replacement: $Data/Context/Property[@Name='<MonitorName>’]$" issue in OM log
      • Fix: Changed the performance rules write actions accounts to “Default Action account”
      • Improvements: Updated discoveries to throw errors in case of some problems detected during the discovery
      • Improvements: Changed defaults for CPU Usage monitor, added sampling to Memory Usage on the server monitor
      • Improvements: Simplified the dashboard to make it quicker and more informative
    • Microsoft System Center Management Pack for SQL Server 2014 Reporting Services (Native Mode) The features and fixes that are included in this update:
      • Feature: Added timeout support for every non-native workflow
      • Feature: Instance configuration monitor is introduced
      • Improvements: Implemented a better logging system
      • Improvements: Improved the Report Manager availability monitor: now it parses human readable message to get the real status of the Report Manager
      • Improvements: Improved the Report Manager and Web Service availability monitors: now the user can treat some status codes as healthy via the override.
      • Improvements: Reviewed and updated the Knowledge Base articles
      • Improvements: Updated the discoveries to throw errors in case of some problems detected during the discovery
      • Improvements: Simplified the dashboard to make it quicker and more informative
      • Improvements: Improved Run As mappings
      • Fix: Microsoft System Center Management Pack for SQL Server Reporting Services doesn’t discover SSRS instance when the instance name starts from some certain symbols (0-9, A-F)
      • Fix: the discoveries, now the last items can be undiscovered
      • Fix: "Memory consumed by other processes (%)" rule having no Run As profile for DS; added SQL MP default Run As to the data source
      • Fix: "Failing replacement: $Data/Context/Property[@Name='<MonitorName>’]$" issue in OM log
      • Fix: Changed the performance rules write actions accounts to “Default Action account”
    • Microsoft System Center Management Pack for SQL Server 2012 Reporting Services (Native Mode) The features and fixes that are included in this update:
      • Feature: Added timeout support for every non-native workflow
      • Feature: Instance configuration monitor is introduced
      • Improvements: Implemented a better logging system
      • Improvements: Improved the Report Manager availability monitor: now it parses human readable message to get the real status of the Report Manager
      • Improvements: Improved the Report Manager and Web Service availability monitors: now the user can treat some status codes as healthy via the override.
      • Improvements: Reviewed and updated the Knowledge Base articles
      • Improvements: Updated the discoveries to throw errors in case of some problems detected during the discovery
      • Improvements: Simplified the dashboard to make it quicker and more informative
      • Improvements: Improved Run As mappings
      • Fix: Microsoft System Center Management Pack for SQL Server Reporting Services doesn’t discover SSRS instance when the instance name starts from some certain symbols (0-9, A-F)
      • Fix: the discoveries, now the last items can be undiscovered
      • Fix: "Memory consumed by other processes (%)" rule having no Run As profile for DS; added SQL MP default Run As to the data source
      • Fix: "Failing replacement: $Data/Context/Property[@Name='<MonitorName>’]$" issue in OM log
      • Fix: Changed the performance rules write actions accounts to “Default Action account”
    • Microsoft System Center Management Pack for SQL Server 2008 Reporting Services (Native Mode) The features and fixes that are included in this update:
      • Feature: Added timeout support for every non-native workflow
      • Feature: Instance configuration monitor is introduced
      • Improvements: Implemented a better logging system
      • Improvements: Improved the Report Manager availability monitor: now it parses human readable message to get the real status of the Report Manager
      • Improvements: Improved the Report Manager and Web Service availability monitors: now the user can treat some status codes as healthy via the override.
      • Improvements: Reviewed and updated the Knowledge Base articles
      • Improvements: Updated the discoveries to throw errors in case of some problems detected during the discovery
      • Improvements: Simplified the dashboard to make it quicker and more informative
      • Improvements: Improved Run As mappings
      • Fix: Microsoft System Center Management Pack for SQL Server Reporting Services doesn’t discover SSRS instance when the instance name starts from some certain symbols (0-9, A-F)
      • Fix: the discoveries, now the last items can be undiscovered
      • Fix: "Memory consumed by other processes (%)" rule having no Run As profile for DS; added SQL MP default Run As to the data source
      • Fix: "Failing replacement: $Data/Context/Property[@Name='<MonitorName>’]$" issue in OM log
      • Fix: Changed the performance rules write actions accounts to “Default Action account”
    • Microsoft System Center Management Pack for SQL Server Dashboards

    Before installing in the updates in your production environment make sure that you test these updates in your test environment.

    Database Backup Failed To Complete

    In my System Center Operations Manager 2012 SP1 whit the System Center Management Pack for SQL Server and Replication (6.6.4.0) installed and configured in my environment I was running into the following error:

    AlertDatabaseBackupFailedToCompleteI took the following steps to resolve this issue.

    1. Check the backup application log for detailed messages.
    2. Manual backup the database using the SQL Management Studio

    1. Check the backup applications log for detailed messages

    When opening the “error.log” which is located at “C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG” I was seeing the error: “Error: 3041, Severity: 16, State: 1

    LogError3401Severity16State1 When seeing this error I took the time to use “SQL Management Studio” to backup the database. More information on this error can be found here

    2. Manual backup the database using the SQL Management Studio

    1. Start the “SQL Server Management Studio
    2. In the “Connect to Server” screen enter the needed information to logon to the SQL Server
    3. In the “Object Explorer” expand “databases”, and right click the database that you want to backup. Click “Tasks” and click “Back-Up”
      BackupDatabase1
    4. In the “Back Up Database – Database Name” screen in click “OK” (If you want to change the location where you want to store the backup. Change the settings in the destination section)
      BackupDatabase2  

    When running the backup manually I was getting the following error:

    BackupError

    I used the following Knowledgebase article to solve the issue: Error message when you perform a full backup of a database in SQL Server 2005: "Backup failed for Server ‘Computer Name\SQLInstanceName’ " or "The backup of the file or file group ‘sysft_FullTextCatalog’ is not permitted because it is not online"

    When finished running the steps from the above article my problem was solved and the System Center Operation Manager critical alert can be closed.

    Updated MP: Microsoft System Center Management Pack for SQL Server 6.6.4.0

    On 18-November-2015 Microsoft released update for the SQL Management Pack. The version is updated to 6.6.4.0.

    • Microsoft System Center Management Pack for SQL Server The features and fixes that are included in this update:
      • Feature: Added a support for disabled TCP/IP protocol
      • Fix: performance metrics error that may occur on some localized versions of Windows
      • Fix: bugs in monitor tiles on SQL Server Summary Dashboard
      • Fix: incorrect performance of Transaction log free space monitor
      • Feature: Added new type of events from failed discoveries; added a new rule that collects such events
      • Feature: Added overrides to prevent various scripts timeout failure
      • Feature: Removed some 1X1 tiles from Summary Dashboards
      • Feature: File stream file groups are excluded from discovery for now
      • Feature: 2008/2012 Summary Dashboards tiles were reorganized
      • Feature: Updated the visualization library
      • Fix: the error message in SQL DB discovery script
    • Microsoft System Center Management Pack for SQL Server 2014 The features and fixes that are included in this update are:
      • Fix: performance
      • Feature: added a support for disabled TCP/IP protocol
      • Fix: performance metrics error that may occur on some localized versions of Windows
      • Fix: incorrect performance of Transaction log free space monitor
      • Feature: Added new type of events from failed discoveries; added a new rule that collects such events
      • Feature: Added overrides to prevent various scripts timeout failure
      • Feature: Removed some 1X1 tiles from Summary Dashboards
      • Feature: File stream file groups are excluded from discovery for now
      • Feature: 2008/2012 Summary Dashboards tiles were reorganized
      • Feature: Added KB for Microsoft.SQLServer.2014.Mirroring.MirroringCommonGroupDiscovery
      • Feature: Summary Dashboard: added monitor/performance tiles to class "SQL Server 2014 Mirroring Groups"
      • Feature: Updated the visualization library
      • Fix: Some minor fixes
    • Microsoft System Center Management Pack for SQL Server 2008 Replication There are no new features or fixes included  in this update
    • Microsoft System Center Management Pack for SQL Server 2012 Replication There are no new features or fixes included in this update.
    • Microsoft System Center Management Pack for SQL Server 2014 Replication The features and fixes that are included in this update:

    Before installing in the updates in your production environment make sure that you test these updates in your test environment.

    Updated MP: Microsoft System Center Management Pack for SQL Server 6.6.3.0

    On 12-November-2015 Microsoft released updates for the SQL Management Pack’s. The version is updated to: 6.6.3.0.

    • Microsoft System Center Management Pack for SQL Server The features and fixes that are included in this Update:
      • Feature: Added a support for disabled TCP/IP protocol
      • Fix: Performance metrics error that may occur on some localized versions of Windows
      • Fix: bugs in monitor tiles on SQL Server Summary Dashboard
      • Fix: incorrect performance of Transaction log free space monitor
      • Feature:  Added new type of events from failed discoveries; added a new rule that collects such events
      • Feature: Added overrides to prevent various scripts timeout failure
      • Feature: Removed some 1X1 tiles from Summary Dashboards
      • Feature: File stream file groups are excluded from discovery for now
      • Feature: 2008/2012 Summary Dashboards tiles were reorganized
      • Feature: Updated the visualization library
      • Fix: the error message in SQL DB discovery script
    • Microsoft System Center Management Pack for SQL Server 2014 The features and fixes that are included in this Update:
      • Fix: performance
      • Feature: Added a support for disabled TCP/IP protocol
      • Fix: performance metrics error that may occur on some localized versions of Windows
      • Fix: incorrect performance of Transaction log free space monitor
      • Feature: Added new type of events from failed discoveries; added a new rule that collects such events
      • Feature: Added overrides to prevent various scripts timeout failure
      • Feature: Removed some 1X1 tiles from Summary Dashboards
      • Feature: File stream file groups are excluded from discovery for now
      • Feature: 2008/2012 Summary Dashboards tiles were reorganized
      • Feature: Added KB for Microsoft.SQLServer.2014.Mirroring.MirroringCommonGroupDiscovery
      • Feature: Summary Dashboard: added monitor/performance tiles to class "SQL Server 2014 Mirroring Groups"
      • Feature: Updated the visualization library
      • Fix: Some minor fixes
    • Microsoft System Center Management Pack for SQL Server 2008 Replication There are no new features or fixes described in the knowledge base article.
    • Microsoft System Center Management Pack for SQL Server 2014 Replication There are no new features or fixes described in the knowledge base article

    Before installing the updates in your production environment make sure that you test these updates in your test Environment.

    Older Posts »