MS-Opsmgr

Microsoft System Center Operations Manager

Building a Management pack using VSAE Part 2

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.

In the first part I have created the base management pack and I created the classes I need to create the management pack. In this part I am going tot talk about how to use create the Discovery’s.

Creating the Seed Class and Discovery.

I am going to create a seed class to check if the  Simpana Commvault applications is installed on the servers. To check if the application is installed take a look at the following registry key: “HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems

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

    Visual Studio - Seed Class

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

  5. In the “Microsoft Visual Studio” console, in the “Solution Explorer” on the folder “Service Model” Right click the folder and click “Add”, “New Folder
  6. In the “Microsoft Visual Studio” console, in the “Solution Explorer” name the new folder “Discoveries
  7. In the “Microsoft Visual Studio” console, in the “Solution Explorer” on the folder “Discoveries”, right click the folder and click “Add”, “New Item
  8. In the “Microsoft Visual Studio” console, in the “Add New Item – Simpana.Commvault” screen select “Class”. Enter the following data and click “Add”:
    • "Name:" Discoveries.mptg

    Visual Studio - Discoveries.mptg

  9. In the “Microsoft Visual Studio” console, on the “Discoveries.mptg” tab select “NewDiscovery” and see the properties screen.

    Visual Studio - Discoveries Properties

  10. On the “Properties” page change the following settings:
    • "Display Name:" Discover Simpana CommVault Seed
    • "ID" Discovery.Seed
    • Description:” Discover Simpana CommVault Seed 
    • In the “Discovery Classes” properties click “” in the “Discovery Classes Collection Editor” click “Add”. IN the Properties select the class “Simpana.CommVault.Seed” and click “OK

      Visual Studio - Create Discoveries

    • In the “Target” properties click “” and in the “Choose a Class…” screen select the “Microsoft.Windows.Server.Computer” class and click “OK

      Visual Studio - Target Class Microsoft.Windows.Server.Computer

    • In the “Data Source Type ID” properties click “” and in the “Choose a Data Source Module Type…” screen select “Microsoft.Windows.FilteredRegistryDiscoveryProvider” data source module and click “OK

      VisualStudioDiscoveries4

    • In the “Data Source Configuration..” properties click “” and enter the following code and click “OK”:

    • The end result should look something like this

      Visual Studio - Properties Discover Seed Completed

  11. In the “Microsoft Visual Studio” console, in the “Solution Explorer” right click “Simpana.CommVault” and click “Add”, “New Folder
  12. In the “Microsoft Visual Studio” console. in the “Solution Explorer” name the new Folder “Presentation
  13. In the “Microsoft Visual Studio” console, in the “Solution Explorer” on the folder “Presentation”, right click the folder and click “Add”, “New Item” 
  14. In the “Microsoft Visual Studio” console, in the “Add New Item – Simpana.Commvault” screen select “Folder & Folder Item”. Enter the following data and click “Add”:
    • "Name:" Folders.mpx

    Visual Studio - Add Folders

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

  16. In the “Microsoft Visual Studio” console, in the “Solution Explorer” on the folder “Presentation”, right click the folder and click “Add”, “New Item
  17. In the “Microsoft Visual Studio” console, in the “Add New Item – Simpana.Commvault” screen select “View(Custom)”. Enter the following data and click “Add”:
    • "Name:" Views.mptg

    Visual Studio - View

  18. In the “Microsoft Visual Studio” console, on the “Views.mptg” tab select “NewView” and see the properties screen.

    Visual Studio - Views

  19. On the “Properties” page change the following settings:
    • "Description:" Seed
    • Display Name:” Seed
    • ID:” View.State.Seed
    • In the “Target” properties click “” and in the “Choose a Class…” screen select the “Simpana.CommVault.Seed” class and click “OK

      Visual Studio - Simpana.CommVault.Seed

    • In the “View Folder” properties click “” and in the “Choose a Folder…” screen select the “Simpana.CommVault.Folder” folder and click “OK

      VisualStudioViews4

    • In the “View Type” properties click “” and in the “Choose a View Type…” screen select the “Microsoft.SystemCenter.StateViewType” folder and click “OK

      Visual Studio - Create View Type

    • The end result should look something like this

      Visual Studio - View Completed
  20. In the “Microsoft Visual Studio” console, in the “Menu” click “File”, “Save
  21. In the “Microsoft Visual Studio” console, in the “Menu” click “Build”, “Build Solution
  22. The result should look something like this:

    System Center Operations Manager Console - Seed

Create a Discovery for the MediaAgent

To check if the MediaAgent software is installed on a server we need check if the registry key “HKEY_LOCAL_MACHINE\SOFTWARE\CommVault System\Galaxy\Instance001\InstalledPackages\51” whit the string key value “Pkgname” whit the data “MediaAgent” Exist

Before I can create the registry discovery I need to modify the class “MediaAgent.mpx

  1. Start “Microsoft Visual Studio” and open the project
  2. In the “Microsoft Visual Studio” console, in the “Solution Explorer” expand the folder “Service Model”, “Classes” and double click “MediaAgent.mpx
  3. In the “Microsoft Visual Studio” console, on the “MediaAgent.mpx” tab add the following code to the ClassType “Simpana.CommVault.ComputerRole.MediaAgent”:

  4. In the “Microsoft Visual Studio” console, in the “Menu” click “File”, “Save

Now that the class is modified I can create the Discovery for the Media Agents

  1. Start “Microsoft Visual Studio” and open the project
  2. In the “Microsoft Visual Studio” console, in the “Solution Explorer” expand the folder “Service Model”, “Discoveries” and double click “Discoveries.mptg
  3. In the “Microsoft Visual Studio” console, on the “Discoveries.mptg” tab select the “Discovery Seed” and copy and paste the discovery. The result should look something like this:

    Visual Studio - Copy Discovery

  4. In the “Microsoft Visual Studio” console, on the “Discoveries.mptg” tab select one “Discovery seed” right click and click “Properties Window

    Visual Studio - Properties Window

  5. Change the following settings:
    • Display Name:” Discover Simpana CommVault MediaAgent
    • Description:” Discover Simpana Commvault MediaAgent
    • In the “Target” properties click “” and in the “Choose a Class…” screen select the “Simpana.CommVault.Seed” class and click “OK
    • ID:” Discover.MediaAgent
    • In the “Data Source Configuration..” properties click “” and enter the following code and click “OK”:

  6. In the “Microsoft Visual Studio” console, in the “Solution Explorer” expand the folder  “Presentation” and double click “Views.mptg
  7. In the “Microsoft Visual Studio” console, on the “Views.mptg” tab select the “View.State.Seed” and copy and paste the View. The result should look something like this:

    Visual Studio - Copy View.State.Seed

  8. In the “Microsoft Visual Studio” console, on the “Views.mptg” tab select one “View.State.Seed” right click and click “Properties Window

    VisualStudioViews9

  9. Change the following settings:
    • Display Name:” MediaAgents
    • Description:”  State View MediaAgent
    • ID” State.View.MediaAgent
    • In the “Target” properties click “” and in the “Choose a Class…” screen select the “Simpana.CommVault.ComputerRole.MediaAgent” class and click “OK
  10. The result should look something like this 
    System Center Operations Manager Console - MediaAgent Discovery 

Create a Discovery for the IdataAgent ‘SharePoint’, ‘SQL’, ‘File System’, ‘Exchange’

Now need to make the discoveries for the IdataAgents. The following IdataAgents are we going to check:

  • To check if the IdataAgent for SharePoint is installed on a server we need check if the registry key “HKEY_LOCAL_MACHINE\SOFTWARE\CommVault System\Galaxy\Instance001\InstalledPackages\101” whit the string key value “Pkgname” whit the data “SharePoint iDataAgent” Exist.
  • To check if the IdataAgent for SQL is installed on a server we need check if the registry key “HKEY_LOCAL_MACHINE\SOFTWARE\CommVault System\Galaxy\Instance001\InstalledPackages\353” whit the string key value “Pkgname” whit the data “iDA for MSSQL Server” Exist
  • To check if the IdataAgent for File System is installed on a server we need check if the registry key “HKEY_LOCAL_MACHINE\SOFTWARE\CommVault System\Galaxy\Instance001\InstalledPackages\702” whit the string key value “Pkgname” whit the data “File System” Exist
  • To check if the IdataAgent for Exchange  is installed on a server we need check if the registry key “HKEY_LOCAL_MACHINE\SOFTWARE\CommVault System\Galaxy\Instance001\InstalledPackages\151” whit the string key value “Pkgname” whit the data “iDA for Exchange Database” Exist
  1. Start “Microsoft Visual Studio” and open the project
  2. In the “Microsoft Visual Studio” console, in the “Solution Explorer” expand the folder “Service Model”, “Classes” and double click “MediaAgent.mpx
  3. In the “Microsoft Visual Studio” console, on the “MediaAgent.mpx” tab add the following code:

Now that the class is modified I can create the Discovery for the IdataAgents

  1. Start “Microsoft Visual Studio” and open the project
  2. In the “Microsoft Visual Studio” console, in the “Solution Explorer” expand the folder “Service Model”, “Discoveries” and double click “Discoveries.mptg
  3. In the “Microsoft Visual Studio” console, on the “Discoveries.mptg” tab select the “Discovery Seed” and copy and paste the discovery.
  4. In the “Microsoft Visual Studio” console, on the “Discoveries.mptg” tab select one “Discovery seed” right click and click “Properties Window
  5. Change the following settings:
    • Display Name:” Discover Simpana CommVault IdataAgent SharePoint
    • Description:” Discover Simpana CommVault IdataAgent SharePoint
    • ID:” Discover.IdataAgent.SharePoint
    • In the “Data Source Configuration..” properties click “” and enter the following code and click “OK”:

  6. In the “Microsoft Visual Studio” console, in the “Solution Explorer” open the “Folders.mpx” file and enter the following code:

  7. In the “Microsoft Visual Studio” console, in the “Solution Explorer” expand the folder  “Presentation” and double click “Views.mptg
  8. In the “Microsoft Visual Studio” console, on the “Views.mptg” tab select the “View.State.Seed” and copy and paste the View.
  9. In the “Microsoft Visual Studio” console, on the “Views.mptg” tab select one “View.State.Seed” right click and click “Properties Window
  10. Change the following settings:
    • Display Name:” SharePoint
    • Description:”  State View IdataAgents SharePoint
    • ID” State.View.IdataAgent.SharePoint
    • In the “Target” properties click “” and in the “Choose a Class…” screen select the “Simpana.CommVault.ComputerRole.IdataAgentSharePoint” class and click “OK”  
    • View Folder:” Simpana.CommVault.Folder.IdataAgents
  11. In the “Microsoft Visual Studio” console, on the “Discoveries.mptg” tab select the “Discover.IdataAgent.SharePoint” and copy and paste the discovery.
  12. In the “Microsoft Visual Studio” console, on the “Discoveries.mptg” tab select one “Discover.IdataAgent.SharePoint” right click and click “Properties Window
  13. Change the following settings:
    • Display Name:” Discover Simpana CommVault IdataAgent SQL
    • Description:” Discover Simpana CommVault IdataAgent SQL
    • ID:” Discover.IdataAgent.SQL
    • In the “Data Source Configuration..” properties click “” and enter the following code and click “OK”:

  14. In the “Microsoft Visual Studio” console, in the “Solution Explorer” expand the folder  “Presentation” and double click “Views.mptg
  15. In the “Microsoft Visual Studio” console, on the “Views.mptg” tab select the “View.State.IdataAgent.SharePoint” and copy and paste the View.
  16. In the “Microsoft Visual Studio” console, on the “Views.mptg” tab select one “View.State.IdataAgent.SharePoint” right click and click “Properties Window
  17. Change the following settings:
    • Display Name:” SQL
    • Description:”  State View IdataAgents SQL
    • ID” State.View.IdataAgent.SQL
    • In the “Target” properties click “” and in the “Choose a Class…” screen select the “Simpana.CommVault.ComputerRole.IdataAgentSQL” class and click “OK”  
    • View Folder:” Simpana.CommVault.Folder.IdataAgents
  18. In the “Microsoft Visual Studio” console, on the “Discoveries.mptg” tab select the “Discover.IdataAgent.SharePoint” and copy and paste the discovery.
  19. In the “Microsoft Visual Studio” console, on the “Discoveries.mptg” tab select one “Discover.IdataAgent.SharePoint” right click and click “Properties Window
  20. Change the following settings:
    • Display Name:” Discover Simpana CommVault IdataAgent File System
    • Description:” Discover Simpana CommVault IdataAgent File System
    • ID:” Discover.IdataAgent.FileSystem
    • In the “Data Source Configuration..” properties click “” and enter the following code and click “OK”:

  21. In the “Microsoft Visual Studio” console, in the “Solution Explorer” expand the folder  “Presentation” and double click “Views.mptg
  22. In the “Microsoft Visual Studio” console, on the “Views.mptg” tab select the “View.State.IdataAgent.SharePoint” and copy and paste the View.
  23. In the “Microsoft Visual Studio” console, on the “Views.mptg” tab select one “View.State.IdataAgent.SharePoint” right click and click “Properties Window
  24. Change the following settings:
    • Display Name:” File System
    • Description:”  State View IdataAgents File System
    • ID” State.View.IdataAgent.FileSystem
    • In the “Target” properties click “” and in the “Choose a Class…” screen select the “Simpana.CommVault.ComputerRole.IdataAgentFileSystem” class and click “OK”  
    • View Folder:” Simpana.CommVault.Folder.IdataAgents
  25. In the “Microsoft Visual Studio” console, on the “Discoveries.mptg” tab select the “Discover.IdataAgent.SharePoint” and copy and paste the discovery.
  26. In the “Microsoft Visual Studio” console, on the “Discoveries.mptg” tab select one “Discover.IdataAgent.Exchange” right click and click “Properties Window
  27. Change the following settings:
    • Display Name:” Discover Simpana CommVault IdataAgent Exchange
    • Description:” Discover Simpana CommVault IdataAgent Exchange
    • ID:” Discover.IdataAgent.Exchange
    • In the “Data Source Configuration..” properties click “” and enter the following code and click “OK”:

    1. In the “Microsoft Visual Studio” console, in the “Solution Explorer” expand the folder  “Presentation” and double click “Views.mptg
    2. In the “Microsoft Visual Studio” console, on the “Views.mptg” tab select the “View.State.IdataAgent.SharePoint” and copy and paste the View.
    3. In the “Microsoft Visual Studio” console, on the “Views.mptg” tab select one “View.State.IdataAgent.SharePoint” right click and click “Properties Window
    4. Change the following settings:
      • Display Name:” Exchange
      • Description:”  State View IdataAgents Exchange
      • ID” State.View.IdataAgent.Excahnge
      • In the “Target” properties click “” and in the “Choose a Class…” screen select the “Simpana.CommVault.ComputerRole.IdataAgentExchange” class and click “OK”  
      • View Folder:” Simpana.CommVault.Folder.IdataAgents

When completed the above steps, the result should look something like this.

Discovery Finished

When looking at part 1 we completed the discoveries for the MediaAgents and the IdataAgents. In the next Part we are going to discover the CommServe components.

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: System Center Monitoring Pack for System Center Configuration Manager

On 29-July-2016 Microsoft released update for the System Center Monitoring Pack for System Center Configuration Manager. The version is updated to 5.00.8239.1009

  • System Center Monitoring Pack for System Center Configuration Manager The features and fixes that are included in this update:
    • Feature: Monitors availability status of the Intune connector.
      • SMS_DMP_DOWNLOADER – SMS_Executive component
      • SMS_DMP_UPLOADER – SMS_Executive component
      • SMS_CLOUD_USERSYNC – SMS_Executive component
      • SMS_OUTGOING_CONTENT_MANAGER – SMS_Executive component
    • Feature: Monitors hman.box for backlogs that exceed the threshold.
      • Monitor inbox – hman.box performance counter
    • Feature: Monitors availability status of the Microsoft Intune service
      • Microsoft Intune service offline
      • Local network issue prevents DMP connector from reaching Intune service
      • DMP connector doesn’t sync with the Intune service
    • Fix: a bug that was preventing complete system discovery when distribution points are set to HPPPS mode has been fixed.

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

Update MP: System Center Management Pack for Windows Server Operating System

On 28-July-2016 Microsoft released update for the System Center Management Pack for Windows Server Operating System. The version is updated to 6.0.7316.0

  • System Center Management Pack for Windows Server Operating System The features and fixes that are included in this update:
    • Fix: predisk free space monitoring issue on Quorum disks in failover clusters; the monitor was displayed as healthy, but actually it did not work and no performance data was collected.
    • Fix: logical disk discovery did not discover logical disk on non-clustered server with Failover Cluster Feature enabled
    • Fix: Clustered Shared Volumes were being discovered twice – as a Clustered Shared Volume and as a logical disk; now they are discovered as Clustered Shared Volumes only
    • Fix: mount points were being discovered twice for cluster disks mounted to a folder – as a cluster disk and as a logical disk
    • Fix: Cluster Shared Volume objects were being discovered incorrectly when they had more than one partition (applied to discovery and monitoring): only one partition was discovered, while the monitoring data was discovered for all partitions available. The key field is changed, and now partitions are discovered correctly
    • Fix: Cluster Shared Volume objects were being discovered incorrectly when they had more than one partition (applied to discovery and monitoring): only one partition was discovered, while the monitoring data was discovered for all partitions available. The key field is changed, and now partitions are discovered correctly
    • Fix: Fix: physical CPUs are now discovered on Windows Server 2008 R2 platforms; logical CPUs are no longer discovered
    • Fix: Windows Server 2008 Max Concurrent API Monitor did not work on Windows Server 2008 platform. Now, it is supported on Windows Server platforms starting from Windows Server 2008 R2.
    • Fix: when network resource name contained more than 15 symbols, the last symbols of the name were cut off, which was resulting in cluster disks and Cluster Shared Volume discovery issues.

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

VSAE: Seal a Management Pack

Just a quick post on how to create a sealed management pack when building a management pack using Visual Studio Authoring Extensions.

I am currently studying  on how to create management pack’s using Visual Studio Authoring Extensions. When creating a sealed management pack I use the following default settings:

  1. Start Visual Studio 2015 Visual Studio 2015
  2. In the Visual Studio 2015 tool click “File”. “New”, “Project
    Create New Project
  3. In the New project screen, expand “Templates”, “Management Pack”, “Operations Manager”. From the New Project screen, select “Operations Manager 2007 R2 Management Pack” and give the Management Pack a logical Name and click “OK” 
    New Project
  4. In Visual Studio in the “Solution Explorer” right click the “ms.opsmgr.management.pack” and click “Properties
    Properties Management Pack
  5. On the properties page click “Build” en select “Generate a sealed and signed Management Pack” and change the “Company Name
    Generate Sealed and Signed Management pack
  6. From the Start menu Start the “Developer Command Prompt for VS2015
    Developer Command Prompt
  7. On the Developers command prompt enter the following command: “sn –k “C:\Users\Roel\Documents\Visual Studio 2015\Projects\ms.opsmgr.management.pack\msopsmgr.snk”” and press “Enter
    Developer Command Prompt
  8. Switch back to Visual Studio
  9. In Visual Studio on the build page, click “Browse”. Browse to the location where you have save your key pair and click “Open” The result should look something like this:
    Select Generated Key Pair

Now every time when we do a build off the Management pack the management pack will be sealed whit the generated key pair.

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:

    Log file Monitoring with the FREE NiCE Management Pack

    In this blogpost I am going to take you true the steps I took to install and configure the Nice Log File Management Pack. You can download the management pack from here and the best thing is that is for FREE!!

    NiCE Log File Monitoring

    Scenario:

    I have an device which generates a log file entry when a registration is received. The registration is processed by an application. I going measure the performance of the application by calculating the time between registration and the processing the information in the application.

    1. Install the Management Pack
    2. Import the Management Pack
    3. PowerShell script to calculate the time between registration and processing
    4. Create a Management Pack.
    5. Create a performance rule using the NiCE Management Pack
    6. Create a performance view

    1. Install the Management Pack

    1. Run the "NiCE_LogfileMP_0130.msi"
    2. In the "NiCE Log File MP – InstallShield Wizard" on the "Welcome to the InstallShield Wizard for NiCE Log File MP" page, click "Next"
      NiCE Log File MP - InstallShield Wizard
    3. In the “NiCE Log File MP – InstallShield Wizard” on the “License Agreement” page, check “I accept the terms and in the license agreement” and click “Next
      NiCE Log File MP - InstallShield Wizard
    4. In the “NiCE Log File MP – InstallShield Wizard” on the “Destination Folder” page, click “Next
      NiCE Log File MP - InstallShield Wizard
    5. In the “NiCE Log File MP – InstallShield Wizard”, on the “InstallShield Wizard Completed” page, click “Finish
      NiCE Log File MP - InstallShield Wizard

    2. Import the Management Pack

    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
      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. Click one or more management packs to import from that directory, and then click Open.
      Select Managemetn Packs to Import
    6. In the “Import Management Pack” wizard, Click “Install
    7. In the “Import Management Pack” wizard, Click “Close

    3. PowerShell script to calculate the time between registration and processing

    I’ve create the following PowerShell script:

    The new created log file looks like this

    Powershell Script Result

    4. Create a Management Pack

    1. Start the “Operations Manager Console
    2. In the "Administration" Workspace, in the Navigation pane, right click "Management Pack" and click "Create Management Pack"

      Create Management Pack

    3. In the “Create a Management Pack” wizard, on the “General properties” page, give the management pack a name and click “Next
    4. In the “Create a Management Pack” wizard, on the “Knowledge Article” page, click “Create

    5. Create a Performance Rule Using NiCE Management Pack

    1. Start the “Operations Manager Console
    2. In the “Authoring” Workspace, in the navigation pane, right click “Rules” and select “Create a new Rule

      Create Performance Rule

    3. In the “Create Rule Wizard”, on the “Rule Type” page, expand “NiCE Log Files”, expand “Performance Rules”, expand “Advanced”, expand “Expression filtered” and then click “Performance Rules (Advanced)

      Create Perfomance Rule

    4. In the “Create Rule Wizard”, on the “Rule Type” page, select the Management pack created in step 4
    5. In the “Create Rule Wizard”, on the “Rule Type” page, Click “Next
    6. In the “Create Rule Wizard”, on the “General” page, In the “Rule name” page enter a “Name”, In the “Rule Category” select “Performance Collection”. Next to “Rule Target” click “Select” and the select the target “Windows Server 2012 R2 Computer”, click “Next

      Create Performance Rule

    7. In the “Create Rule Wizard” on the “Pre-processing Settings” page, click “Next

    8. In the “Create Rule Wizard” on the “Log file Source Settings” page, In the “Log file Path” enter the locations off the log file, In the “Log file Name” click enter the log file name you want to monitor and click “Next

      Create Performance Rule

    9. In the “Create Rule Wizard” on the “Regular Expression Settings (Optional)”, start the “Regex Testing tool
    10. In the “Regex Testing Tool” in the “Log file Line” enter a line of the log file and create a Regex. Mine looked something like this:

      CreatePerformanceRule5

    11. In the “Regex Testing Tool” click “OK
    12. In the “Create Rule Wizard” on the “Regular Expression Settings (Optional)” page, click “Next

      Create Performance Rule

    13. In the “Create Rule Wizard” on the “Performance Mapper” page, In the “Object” field enter “$Target/Property[Type="MicrosoftWindowsLibrary7585010!Microsoft.Windows.Computer"]/HostServerName$”, In the ”Counter” field enter “Time”, In the “Instance” field enter “Val”, In the “Value” field enter “$Date/RegexMatch/Val$

      Create Perfomance Rule

    14. In the “Create Rule Wizard” on the “Performance Mapper” page click “Create

    6. Create Performance View

    1. Start the “Operations Manager Console
    2. In the  “Operations Console”, select “Monitoring” and expand the management pack that you created.
    3. Right click “Management Pack” and click “New” and click “Performance View

      Create Performance View

    4. On the “Properties Name” page, Enter a “Name” check “Collected by Specific rules” and in the Criteria description select the above created “Performance Rule” It should look something like this:

      Create Performance View

    5. The result should look something like this:

      Create Performance View

    This Management Pack will provide capabilities which are missing in System Center Operations manager and the best part off it it’s free. I advice you to check there website and try there management pack.

    I would like to thank Thando Chasakara and his support team for answering all the questions that I had when started working whit the management pack

    Update MP: Microsoft Exchange Server 2013 Management Pack

    On 28-April-2015 Microsoft released update for the Microsoft Exchange Server 2013 Management Pack. The version is updated to 15.0.066.20

    • Microsoft Exchange Server 2013 Management Pack The features and fixes that are included in this update:
      • Fix: preventing Exchange 2013 Mailbox Properties collection when the contents of Email Addresses field exceed the total length of more than 1024 characters.
      • Fix: alerts generated by the previous version of the Management Pack for Exchange Server 2013 have unreadable name. After upgrading of the Management Pack to version 15.0.620.19, alerts generated before the upgrade had the following name: {2}

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

    Log File MP webinar with MVP – Kevin Greene

    This live demo session will be focused on illustrating how you can use the NiCE Log File Management Pack to effectively monitor your log files in SCOM. You will leave the session with a clear understanding of how the solution can help you in your own environment + pick up a few tips & tricks that you may not already know if you are already using the solution.

    logfileWebinar

    Kevin Greene will run through some real-life scenarios in the session to illustrate how to work with the solution to solve problems, and NiCE Product Director, Christian Heitkamp will give you a sneak preview on a future product release.

    Webinar agenda and take outs

    • Learn new best-practices on how our customer use the NiCE Log File MP
    • Popular use cases explained and demonstrated by MVP Kevin Greene
    • Download of the free solution + free examples after Webinar
    • Sneak preview of new features and road map
    • Chance to ask NiCE experts questions

    To find out more about this insightful NiCE Webinar, sign-up today!

    Webinar date: Thursday April 21st, 2016

    Webinar Location: Microsoft ‘Skype for Business’ – Online Webinar (invitation to be sent upon registration)

    Webinar Time:

    16:00-16:45 – Central Europe Time Zone

    10:00-10:45 – North American Eastern Time Zone

    14:00-14:45 –  UTC/GMT

    Older Posts »