MS-Opsmgr

Microsoft System Center Operations Manager

SCOM 2016 – Monitor Changes to the Domain Administrators Group

In this blog post I am going to take you thru the steps I took to monitor changes made to the Domain Administrators Group inside a Active Directory.

First step is to create a management pack where we store the WMI-Discovery, the Monitors and the Views. A manual on how to create a management pack using the system center operations manager console can be found here

  1. Start the “System Center Operations Manager Console” and navigate to “Authoring
  2. In the “System Center Operations Manager Console” in the “Authoring” section expand “Management Pack Object” and select “Attributes
  3. In the “System Center Operations Manager Console” in the “Attributes” section right click “Attributes” and click “Create a New AttributeAttribute01 
  4. In the “Create Attribute Wizard”in the “General Properties” section  give the attribute the name  “Running Domain Controller Service” and click “Next
    Attribute02
  5. In the “Create Attribute Wizard” in the “Discovery Method” section, change the following settings:
    • Change the "Discovery Type" to "WMI Query"
    • Change the "Target" to "Windows Server"
    • Change the "Management Pack" to "Group Member Changes"

    In the “Create Attribute Wizard” in the “Discovery Method” section click “Next”. The result should look something like this:
    Attribute03

  6. In the “Create Attribute Wizard” in the “WMI Configuration” section change the following settings:
    • Change the "WMI Namespace" to "root\cimv2"
    • Change the "Query" to "select * from Win32_OperatingSystem where (ProductType = "2""
    • Change the "Property Name" to "ProductType"
    • change the "Frequency" to "900"

    In the “Create Attribute Wizard” in the “WMI Configuration” section click “Finish”. The result should look something like this:
    Attribute04

Now that we created the attribute we need to create a Group.

  1. Start the “System Center Operations Manager Console” and navigate to “Authoring
  2. In the “System Center Operations Manager Console” in the “Authoring” section select “Groups
  3. In the “System Center Operations Manager Console” in the “Authoring” section right click “Groups” and click “Create a New Group
    Group01
  4. In the “Create Group Wizard” in the “General Properties” section change the following settings: 
    • Change the "Name" to "Servers Running Domain Controller Service"
    • Change the "Management Pack" to "Group Member Changes"

    In the “Create Group Wizard” in the “General Properties” section click "Next". The result should look something like this.
    Group02

  5. In the “Create Group Wizard” in the “Explicit Members” section click “Next
  6. In the “Create Group Wizard” in the “Dynamic Members” section click “Create/Edit Rules
  7. In the “Create Group Wizard -  Query Builder” wizard, set the following settings: 
    • Change the "Select the Desired class and click add button to begin building the formule" to "Windows Server_Extended" click "Add"
    • From the Pull down list select "Running Domain Controller Service"
    • Set the Operator to "Greater"
    • Change the Value to "2" and click "Ok"

    In the “Create Group Wizard” in the “Dynamic Members” section click "Next". The result should look something like this.:
    Group04

  8. In the “Create Group Wizard” in the “Subgroups” section click "Next".
  9. In the “Create Group Wizard” in the “Excluded Members” section click "Create".

When you look at which servers are managed by the above created groups

Group05

Now its time to create a custom rule to monitor the changes made to the Domain Admins Groups

  1. Start the "System Center Operations Manager Console" and navigate to “Authoring
  2. In the “System Center Operations Manager Console” in the “Authoring” section expand “Management Pack Object” and select “Rules
  3. In the “System Center Operations Manager Console” in the “Attributes” section right click “Attributes” and click “Create a New Rule
    Rule01
  4. In the “Create Rules Wizard” in the “Rule Type” section, set the following settings:
    • In the "Select the type of rule to create" expand "Alert Generating Rules", "Event Based" and select "NT Event Log (Alert)"
    • In the "Management pack" section select the "Group Member Changes" management pack

    In the “Create Rule Wizard” in the “Rule Type” section click "Next". The result should look something like this.:
    Rule02

  5. In the “Create Rule Wizard”, in the “General” section, set the following settings:
    • Enter the "Rule Name" "Security Group Alert – User Added to Group"
    • Change the "Rule Category" to "Alert"
    • Change the "Rule Target" to "Windows Server"
    • Uncheck "Rule is enabled"

    In the “Create Rule Wizard” in the “General” section click "Next". The result should look something like this.:
    Rule03

  6. In the “Create Rule Wizard” in the “Event Log Type” section change the log name to “Security” and click “Next
  7. In the “Create Rule Wizard” in the “Build event Expression” section., change Event-ID Value to “4782”, change the event source to “Parameter 3” whit the value “Domain Admins”. Click “Next” The result should look something like this:
    Rule04
  8. In the “Create Rule Wizard” in the “Configure Alerts” section. Click “Create.
    Rule05

When you now add a user to the Domain Admins group the following alert is generated.

Warning

I created a management pack which is also monitoring the “Domain Admins”, “Schema Admins”, “Enterprise Admins”. The only difference. is that a warning is generated and that the rules are enabled. You can download the management pack from here

Software Update: VSAE Supporting Visual Studio 2015

 

On 21-October-2016Microsoft released  an software update of the System Center Visual Studio Authoring Extensions (VSAE) to version: 1.2.0.1

Before installing this software update in your production environment make sure you test these software update in your test environment

SCOM 2016: Network Monitoring Management Pack generator Tool

On 12-October-2016 Microsoft released the System Center 2016 sweet. With the release of System Center Operations Manager 2016 Microsoft created the “Network Monitoring Management Pack generator tool” which provides you with extended monitoring for your SNMP-enabled devices by generating your own custom Management Pack.

The following features are included:

  • SNMP_MpGenerator tool has a inbuilt MIB Browser. Users can load MIB files, search through the Object Identifiers (OIDs) of the component they wish to add workflows for and create rules and monitors
  • Users can add monitors and rules for device components such Processors, Memory, Fan, Temperature Sensor, Power Supply, Voltage Sensor and Custom device components
  • This tool would also support custom devices in addition to already supported devices like switch, Router, Firewall and Load Balancer
  • Users can define monitors and rules for multiple devices in a single project file and generate a single Management Pack for all of their devices.
  • As mentioned above, this tool would also include the command line executive NetMonMPGenerator.exe for users who wish to generate MP through command line interface.

The best part of the tool is that it’s free and that it is well documented. You can download the Network Management Pack generator tool form here

Monitoring Office 365 with System Center Operations Manager 2012

In this blogpost I am going to take you true the steps that I took to implement the Office 365 Management pack for System Center Operations Manager. You can download the Office 365 management pack from here

I took the following steps to import and configure the management pack:

  • Configure a cloud user account
  • Install the Office 365 Management pack
  • Import the Office 365 Management pack
  • Configure the Office 365 Subscriptions

When you want to monitor the Office 365 we need to create a Office 365 user account with Global Administrator permissions. Take the following steps to create a Office 365 user

  1. Go to https://portal.microsoftonline.com 
  2. Login with a account that has the Global Administrator right.
  3. On the “Admin Center” page, in the “Users” block click “Add a user
    Create Monitoring Account in Office 365
  4. In the “Create User Screen” enter the following data:
    • First name: Office365Monitoring
    • Display name: Office365Monitoring
    • Expand “Roles” and select “Global Administrator
    • Expand “Product licenses” and select “Create user without product license
    • Click “Add
      Create Monitoring Account in Office 365
  5. In the “Create User Screen” enter the email address where you want to sent the user password to  and click “Send email and close

When you create the above account login to office365 management portal to change the password. If you don’t change the password you can get the following error:

Authorization Failed

Before we can import the management pack we need to install the management pack

  1. Click “System Center Management Pack for Office 365.msi
  2. In the “System Center Management Pack for Office 365 – Installer” wizard, on the “License Agreement” page, select “I accept” and click “Next
    System Center Management Pack for Office 365
  3. In the “System Center Management Pack for Office 365 – Installer” wizard, on the “Select Installation Folder” page, select “Everyone” and click “Next
    System Center Management Pack for Office 365
  4. In the “System Center Management Pack for Office 365 – Installer” wizard, on the “Confirm Installation” page, click “Install
  5. In the “System Center Management Pack for Office 365 – Installer” wizard, on the “Installation Completed” page, click “Close

After installing the Office 365 Management pack we need to import the management pack into System Center Operations Manager

  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 Microsoft Office 365 Management Pack
  4. The “Import Management pack wizard” opens. Click “Add”, and the click “Add from Disk
    Import Microsoft Office 365 Management Pack
  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.SystemCenter.O365.mpb 
      Import Microsoft Office 365 Management Pack 
  6. In the “Import Management Pack” wizard, Click “Install
  7. In the “Import Management Pack” wizard, Click “Close

Know that the Office 365 management pack is imported it is time configure the management pack

  1. Start the “Operations Manager Console
  2. In the “Operations Manager Console” click “Administration
  3. On the “Administration” page click “Office 365Configure Office 365 Management Pack 
  4. On the “Office 365” page, click “Add Subscription
    Configure Office 365 Management Pack
  5. In the “Add Subscription” wizard, on the “Subscription Configuration” page enter the following data “Subscription Name”, “User Name”, “Password” and click “Next
    Configure Office 365 Management Pack
  6. In the “Add Subscription” wizard, on the “Server Pool” page, select the “All Management Servers Resource Pools” and click “Add Subscription
    Configure Office 365 Management Pack
  7. In the “Add Subscription” wizard, on the “Completion" page, click “Finish

The end result should look something like this:

Configuration Completed

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.

Update MP: System Center 2012 Management Pack for UNIX and Linux Operating Systems (2016/08)

On 30-August-2016 Microsoft released update for the System Center 2012 Management Pack for UNIX and Linux Operating Systems (2016/08). The version is updated to 7.5.1060.0

  • System Center 2012 Management Pack for UNIX and Linux Operating Systems (2016/08) The features and fixes that are included in this update:
    • Feature: Provides monitoring of the AIX 5.3, AIX 6.1, and AIX 7 operating systems..
    • Feature: Provides monitoring of the HP-UX 11iv2 and HP-UX 11iv3 operating systems.
    • Feature: Provides monitoring of the Red Hat Enterprise Linux Server 4, Red Hat Enterprise Linux Server 5, Red Hat Enterprise Linux Server 6, and Red Hat Enterprise Linux 7 operating systems.
    • Feature: Provides monitoring of Solaris 9, Solaris 10, and Solaris 11 operating systems.
    • Feature: Provides monitoring of SUSE Linux Enterprise Server 9, SUSE Linux Enterprise Server 10 SP1, SUSE Linux Enterprise Server 11, and SUSE Linux Enterprise Server 12 operating systems.
    • Feature Provides monitoring of CentOS 5, CentOS 6, and CentOS 7 operating systems
    • Feature: Provides monitoring of Debian GNU/Linux 5, Debian GNU/Linux 6, Debian GNU/Linux 7, and Debian GNU/Linux 8 operating systems.
    • Feature: Provides monitoring of Oracle Linux 5, Oracle Linux 6, and Oracle Linux 7 operating systems
    • Feature: Provides monitoring of Ubuntu Linux Server 10.04 and Ubuntu Linux Server 12.04, and Ubuntu Linux Server 14.04 operating systems.
    • Feature: Enables the installation of the Audit Collection Services for UNIX/Linux Management Packs

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 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.

Older Posts »