Disable Discovery of a SQL Server.

Standard

In my environment I have a couple of SQL severs that are being discovered by the System Center Management Pack for SQL Server where I don’t want to monitor the SQL Server application.

I took the following steps to complete this option:

  1. Create a Group with the client computers you don’t want to monitor
  2. Apply Overrides to Object Discoveries
  3. Run "Remove-SCOMDisabledClassInstance"

1. Create a Group with client Computers  you don’t want to monitor

  1. Start the "System Center Operations Manager Console"
  2. In the System Center Operations Manager console, click "Authoring"
  3. Right-click "Groups", and then click "Create a new Group" to start the Create Group Wizard.
  4. On the "General Properties" page, Enter a "Name", "Description" and select the management pack you want to use. Click "Next" General Properties Group
  5. On the "Explicit Members" page, click "Add/ Remove Objects" Add/ Remove Objects
  6. On the "Create Group Wizard – Object Selection" page, enter the computer name you don’t want to monitor in the "Filter by part or name(Optional)" box. In the "Available Items" box select the computer object and click "Add" and click "Ok"Create Group Wizard - Object Selection
  7. On the "Explicit Members" page, click "Next"
  8. On the "Dynamic Members" page, click "Next"
  9. On the "Sub Groups" page, click "Next"
  10. On the "Excluded Members" page, click "Create"

2. Apply Overrides to Object Discoveries

  1. Start the "System Center Operations Manager Console"
  2. In the System Center Operations Manager console, click "Authoring"
  3. On the "Authoring" page, expand "Management Packs" and select "Object Discovery"
  4. Click the "Scope" button on the Operations Manager toolbar
  5. On the "Scope Management Pack Objects" page, in the look for bar type "SQL " and select the target "SQL Server 2005 DB Engine", “SQL Server 2008 DB Engine”, “SQL Server 2012 DB Engine” and click "OKScope Management Pack Objects
  6. Click “Find Now
  7. Right click on "Discover SQL Server 2005 Database Engines (Windows Server)" and click "Overrides", "Override the Object Discovery", "For a group" Override the Object Discovery
  8. On the "Select Object" page, select the group that you created above
  9. On the "Override Properties" page, check "Enabled" and change the "Override Value" from “True", to "False" and select the "Management Pack" where you want to store the overrides. Click "Apply" and "OK" Override Properties
  10. Repeat the above steps for "Discover SQL Server 2008 Database Engines (Windows Server)" and the "Discover SQL Server 2012 Database Engines (Windows Server)"

3. Run "Remove-SCOMDisabledClassInstance"

  1. Start the "Operations Manager Shell"
  2. At the command prompt Type "Remove-SCOMDisabledClassInstance" and press "Enter"
  3. Answer the Question by pressing "Y" and press "Enter"

    Operations Manager Shell

Now the SQL Servers that were discovered will not be discovered and be removed from the computers state view in the SQL Management Pack

Installing Update Rollup 9 SCOM 2012 Sp1

Standard

In this blog post I will take you true the steps of installing System Center Operations Manager 2012 Sp1 update Rollup 8 to Update Rollup 9

The following issues are fixed in this Update

  • Operational Insight through Operations Manager
  • Support for “SUSE Linux Enterprise Server systems

You can download the Update Rollup 9 form here
The downloaded files consist of an update for the “System Center Operations Manager Console” and the “System Center Operations Manager Server. 

Microsoft Update Catalog

The following steps outline the process of installing the Update

  1. Backup the operations Manager Databases and unsealed Management Pack’s
  2. Install Update to the Management server
  3. Install update to the secondary Management Servers
  4. Install Update to the Operations Manager Console
  5. Run the SQL scripts
  6. Import Management Pack’s
  7. Deploy the update to the agents

1. Backup the operations Manager Databases and unsealed Management Pack’s

I did a manual backup from my databases using the SQL Console

  1. Start the "SQL Server Management Studio"
  2. Connect to the Database server
  3. Right click on the database that you want to backup, select "Tasks" and click "Backup

    Backup Database

  4. On the "Backup Database Select the setting that you want to use and click "Ok

    BackupRunning

  5. When the Backup is completed click "Ok
  6. Repeat the steps Above for all the databases

You can backup your management pack’s using the powershell Operations Manager shell and type the following command:

Get-SCManagementPack | Export-SCManagementPack -path D:\Backup\MP

backupMP

2. Install Update to the Management server

  1. Extract the cabinet file
  2. Start a "elevated powershell command prompt"
  3. Run the "KB3023167-AMD64-Server.msp"

    ManagementServerUpdate

  4. Installation is running. This can take some time.

    ManagementServerUpdate1

  5. On the Dialog Screen "System Center Operations Manager 2012" klik "Yes" to restart the server

    ManagementServerUpdate2

3. Install update to the secondary Management Servers

I installed the update the same way is installed it on the Management Server. So follow Step 2

4. Install Update to the Operations Manager Console

  1. If you don’t want to reopen the System Center Operations Manager Console close the
  2. Extract the cabinet file
  3. Start a "elevated Powershell command prompt"
  4. Run the "KB3023167-AMD64-ENU-Console.msp"

    UpdateConsole1

  5. Installation is running. This can take some time.

    UpdateConsole2

 

5. Run the SQL scripts

  1. Start the "SQL Server Management Studio"
  2. Connect to the Database server and select the “OperationsManagerDW" Database

    SelectOperationManagerDW

  3. On the File menu, click Open, browse to D:\Program Files\System Center 2012\Operations Manager\Server\SQL Script for Update Roll ups , select the "UR_Datawarehouse.SQL" file and then click Open.
  4. When the file is loaded, click "Execute" in the SQL Editor tool bar
  5. Your Result should look something like:

    RowsAffected

Next we need to run the following script against the OperationsManager database

  1. Start the "SQL Server Management Studio"
  2. Connect to the Database server and select the “OperationsManager" Database

    SelectOperationManager

  3. On the File menu, click Open, browse to D:\Program Files\System Center 2012\Operations Manager\Server\SQL Script for Update Roll ups , select the "update_rollup_mom_db" file and then click Open.
  4. When the file is loaded, click "Execute" in the SQL Editor tool bar
  5. Your Result should look something like:

    RowsAffected3

6. Import the management Pack

  1. Start the System Center Operations Manager Console and select the "Administration pane"
  2. Right click "Management Pack" and click "Import Management Packs…"
  3. In the "Import Management Packs" and click "Add" and click "Add from Disk…"
  4. Browse to "D:\Program Files\System Center 2012\Operations Manager\Server\Management Packs for Update Rollups" and select the management Pack’s in that folder
    • Microsoft.SystemCenter.AlertAttachment.mpb
    • Microsoft.SystemCenter.IntelliTraceProfiling.mpb
      • Microsoft.SystemCenter.IntelliTraceCollectorInstallation.mpb which should be installed from SCOM 2012 SP1
      • MediaMicrosoft.Windows.InternetInformationServices.Common.mpb which should be installed from the online catalog
    • Microsoft.SystemCenter.Visualization.Library.mpb
    • Microsoft.SystemCenter.Image.Library.mp
    • Microsoft.SystemCenter.Advisor.Internal.mpb
    • Microsoft.SystemCenter.Apm.Infrastructure.Monitoring.mp
    • Microsoft.SystemCenter.Apm.Infrastructure.mpb
    • Microsoft.SystemCenter.Apm.Library.mpb
    • Microsoft.SystemCenter.DataWarehouse.Report.Library.mp p
    • Microsoft.SystemCenter.DataWarehouse.Reports.mp
    • Microsoft.SystemCenter.DataWarehouse.ServiceLevel.Report.Library.mp
    • Microsoft.SystemCenter.TFSWISynchronization.mpb
  5. Click "Install"

    ImportManagmentPacks

  6. Click "Close"

7. Deploy the update to the agents

  1. Start the System Center Operations Manager Console and select the "Administration pane"
  2. Select " Device Management" and then "Pending Management"
  3. Select the a "Agent" and click "Approve"

    Aprove

  4. On the "Agent Update" page click "Update"

    Update

  5. when you open de the "Agent by Version" view you should see something like this:

    Ready

More information on installing Update Rollup 9 for System Center Operations Manager 2012 sp1 can be found here. To install this Update Rollup 8 I used the deployment plan from Kevin Holman

Remove Attribute in System Center Operations Manager.

Standard

In this blog post I am going to take you true the steps of removing a created Attribute from a Management Pack. This is not possible using the System Center Operation Manager Console. I am going to use the free authoring tool MPAuthor from select Software. After registration you can download the software from here

  1. Start the "System Center Operations Manager Console"
  2. In the "System Center Operations Manager Console" click "Administration
  3. On the "Administration" page, click "Management Packs" and select management pack where you want to remove the Attribute
  4. In the "System Center Operations Manager Console", in the "Tasks" pane click "Export Management Pack…"

    ExportManagementPack

  5. On the "Browse for Folder" page, select where you want to export the folder and click "OK"
  6. Start the "MP Author Console", click "Open" and open the management Pack that you just exported

    MPauthor

  7. In the "MP Author Console ", on the "MP Component" pane, select "Discoveries"

    Discoveries

  8. In the "Mp Author Console" select, the "Attribute Discovery" that you want to remove and click "Delete"

    DeleteAttribute

  9. On the "Delete Selected Discoveries" popup click "Yes"
  10. In the "MP Author Console", on the "Mp Component" click "Language Pack"
  11. Select the name of the Attribute that you created and click "Delete"

    DeleteLanguagePacKReference

  12. On the "Delete selected Language Packs", click "Yes"
  13. In the "MP Author Console", click "Save" and close MP Author
  14. Start the "System Center Operations Manager Console"
  15. In the "System Center operations Manager Console", click "Administration"
  16. On the "Administration" page, click "Management Packs" and from the "Tasks" pan, click "Import Management Pack…"
  17. On the "Import Management Packs" wizard click "Add" and click "Add from disk…"

    ImportManagementPack

  18. On the "Online Catalog Connection" popup, click "No"
  19. Select the Management pack where removed the attribute and click "Install"

When you are going to look for the created attribute it is removed.

Create A Unit Monitor based on a EventID

Standard

In this blog post I am going to take you true the steps that I took to create a Unit Monitor.

A Unit Monitor measures aspects of an application. The monitor can be checking a performance counter tot determine the performance of an application, running a a script to perform a Synthetic transaction, or watch for an event that indicates an error or warning.

I’m going to create a unit monitor using the SMS-Passcode event log based on Unhealthy Event 150 (SMS-Passcode: Modem has been blacklisted and will not restart automatically anymore) and the Healthy Event 202 (SMS-Passcode: Modem Initialization successful (COM 3))

  1. Start the "System Center Operations Manager Console"
  2. In the "System Center Operations Manager Console", click the "Authoring"

    SelectAuthoring

  3. On the "Authoring" pane, expand "Authoring", expand "Management Pack Objects", and the select "Monitors"

    SelectMonitors

  4. In the "System Center Operations Manager console", in the "Tasks" pane click "Create a Monitor"

    CreateMonitor

  5. Select the "Unit Monitor"

    UnitMonitor

  6. On the "Create a unit Monitor" wizard, on the "Monitor Type" page in the section "Select the type of monitor to create", expand "Windows Events", "Simple Event Detection" and select "Windows Event Reset". On the section "Management Pack" on the page "Select a Monitor Type" click "New"

    NewManagementPack

  7. On the "Create a Management Pack" wizard, on the "General Properties" page in the section "Management Pack General Properties", give the management pack a "Name" and click "Next"
  8. On the "Create a Management Pack" wizard, on the "Knowledge" page click "Create"
  9. On the "Create a Unit Monitor" wizard, on the "Monitor Type" page click "Next"

    MonitorType

  10. On the "Create a Unit Monitor" wizard, on the "General" page, in the "General Properties" section, give the monitor a "Name" and on the "Monitor Target" line click "Select
  11. In the "Select Items to Target" wizard, select "Window Computer" and click "OK"

    WindowComputer

  12. On the "Create a Unit Monitor" wizard, on the "General" page, in the "General Properties" section, under "Parent monitor" select "Availability", uncheck "Monitor is enabled" and click "Next"

    GeneralMonitorProperties

  13. On the "Create a Unit Monitor" wizard, on the "Event Log (Unhealthy Event(" page, in the "Specify the event log to read the events from" section, click ""
  14. On the "Select Event Log" wizard in the section "Browse or enter computer name", select the computer you want to read the event log from
  15. On the "Select Event Log" wizard in the section "Available event logs", select "SMS Trans" and click "OK

    SelectEventLog

  16. On the "Create a Unit Monitor" wizard, on the "Event Log (Unhealthy Event(" page, click "Next"
  17. On the "Create a Unit Monitor" wizard, on the "Event Expression (Unhealthy Event)" page in the "Filter one or more events" section, behind the "Event ID" enter "150" and behind the "Event Source" enter "SMS Dispatcher and click "Next"

    EventExpressionUnhealthy

  18. On the "Create a Unit Monitor" wizard, on the "Event Log (Healthy Event(" page, in the "Specify the event log to read the events from" section, click ""
  19. On the "Select Event Log" wizard in the section "Browse or enter computer name", select the computer you want to read the event log from
  20. On the "Select Event Log" wizard in the section "Available event logs", select "SMS Trans" and click "OK

    SelectEventLog

  21. On the "Create a Unit Monitor" wizard, on the "Event Log (Healthy Event(" page, click "Next"
  22. On the "Create a Unit Monitor" wizard, on the "Event Expression (Healthy Event)" page in the "Filter one or more events" section, behind the "Event ID" enter "202" and behind the "Event Source" enter "SMS Dispatcher and click "Next"

    EventExpressionHealthy

  23. On the "Create a Unit Monitor" wizard, on the "Configure Health" page on the section "Map monitor conditions to health states" change the "First Event Raised" to "Critical" and click "Next"

    ConfigureHealth

  24. On the "Create a Unit Monitor" wizard, on the "Configure Alerts" page on the section "Alert Settings" and select "Generate alerts for this Monitor" and click "Create"

    ConfigureAlerts

Now that we have created the monitor it’s time to enable the Monitor.

  1. Start the "System Center Operations Manager Console"
  2. In the "System Center Operations Manager Console", click the "Authoring"
  3. On the "Authoring" pane, expand "Authoring", expand "Management Pack Objects", and the select "Monitors"
  4. On the "Monitors" pane, in the "Look for" input box type "sms"

    LookForSMSPasscode

  5. Select the "SMS PASSCODE Transmission" monitor, and from the "Tasks" pane click "Overrides", "Override the Monitor" and click "For al specific object of class: System Center Managed Computer (Server OS)"

    OverrideForSpecificObjectOfClass

  6. On the "Select Object" wizard, search for the computer that you have have SMS-Passcode installed on and click "OK"
  7. On the "Override Properties" wizard, in the "Override-controlled parameters" section, select "Enable" and change the "Override Value" to "True". Then click "OK".

    OverrideProperties

When the event 150 is raised You will get a warning in the Event-log on the client and in System Center Operations Manager an Alert is generated

AlertProperties

When the issue is resolved and event-id 202 is logged in the Event-Log in the the client. The generated Alert in System Center Operations Manager is Automaticaly closed.

Installing Update Rollup 8 SCOM 2012 Sp1

Standard

In this blog post I will take you true the steps of installing System Center Operations Manager 2012 Sp1 update Rollup 7 to Update Rollup 8

The following issues are fixed in this Update

  • The Health Service bouncing that is caused by high memory usage in the MonitoringHost process.
  • This update includes a fix to prevent resynchronization of all managed entities from the Operations Manager to the Operations Manager Data Warehouse (OMDW) database and to prevent the failure to sync that this causes because of duplicate entries.
  • The import of Visualization.component.library and Visualization.library binary files (.mpb) fails. The import succeeds on a successive try.
  • System Center Operations Manager agents randomly time out when authenticating to the Gateway or Management Server because of domain controller or network performance issues. The time-out value was set to 1 second earlier. A fix was made to increase server time out to-20 seconds and client time out to 5 minutes.

You can download the Update Rollup 8 form here

The following steps outline the process of installing the Update

  1. Backup the operations Manager Databases and unsealed Management Pack’s
  2. Install Update to the Management server
  3. Install update to the secondary Management Servers
  4. Install update to the gateway servers
  5. Install update to the ACS servers
  6. Install Update to the Web Console
  7. Install Update to the Operations Manager Console
  8. Run the SQL scripts
  9. Import Management Pack’s
  10. Deploy the update to the agents

1. Backup the operations Manager Databases and unsealed Management Pack’s

I did a manual backup from my databases using the SQL Console

  1. Start the "SQL Server Management Studio"
  2. Connect to the Database server
  3. Right click on the database that you want to backup, select "Tasks" and click "Backup

    BackupDatabase

  4. On the "Backup Database Select the setting that you want to use and click "Ok

    BackupRunning

  5. When the Backup is completed click "Ok
  6. Repeat the steps Above for all the databases

You can backup your management pack’s using the powershell Operations Manager shell and type the following command:

Get-SCManagementPack | Export-SCManagementPack -path D:\Backup\MP

backupMP

2. Install Update to the Management server

  1. Extract the cabinet file
  2. Start a "elevated powershell command prompt"
  3. Run the "KB2991997-AMD64-Server.msp"

    UpdateManagementServer

  4. Installation is running. This can take some time.

    UpdateManagementServerRunning

  5. On the Dialog Screen "System Center Operations Manager 2012" klik "Yes" to restart the server

    UpdateManagementServerRestart

3. Install update to the secondary Management Servers

I installed the update the same way is installed it on the Management Server. So follow Step 2

4. Install update to the gateway servers

  1. Extract the cabinet file
  2. Start a "elevated powershell command prompt"
  3. Run the "KB2991997-AMD64-Gateway.msp"

    UpdateGatewayServer

  4. The update doesn’t give any feedback. Check the application event-viewer if the setup is finished.

5. Install update to the ACS servers

  1. Extract the cabinet file
  2. Start a "elevated powershell command prompt"
  3. Run the "KB2991997-AMD64-ENU-ACS.msp"

    UpdateACS

  4. The update doesn’t give any feedback. Check the application event-viewer if the setup is finished.

6. Install Update to the Web Console

  1. Extract the cabinet file
  2. Start a "elevated powershell command prompt"
  3. Run the "KB2991997-AMD64-ENU-WebConsole.msp"

    UpdateConsole

  4. Installation is running. This can take some time.

    UpdateWebConsoleRunning

  5. The update doesn’t give any feedback. Check the application event-viewer if the setup is finished.

7. Install Update to the Operations Manager Console

  1. If you don’t want to reopen the System Center Operations Manager Console close the
  2. Extract the cabinet file
  3. Start a "elevated Powershell command prompt"
  4. Run the "KB2991997-AMD64-ENU-Console.msp"

    UpdateConsole

  5. Installation is running. This can take some time.

    UpdateConsoleRunning

 

8. Run the SQL scripts

  1. Start the "SQL Server Management Studio"
  2. Connect to the Database server and select the “OperationsManagerDW" Database

    SelectOperationManagerDW

  3. On the File menu, click Open, browse to D:\Program Files\System Center 2012\Operations Manager\Server\SQL Script for Update Roll ups , select the "UR_Datawarehouse.SQL" file and then click Open.
  4. When the file is loaded, click "Execute" in the SQL Editor tool bar
  5. Your Result should look something like:

    RowsAffected

Next we need to run the following script against the OperationsManager database

  1. Start the "SQL Server Management Studio"
  2. Connect to the Database server and select the “OperationsManager" Database

    SelectOperationManager

  3. On the File menu, click Open, browse to D:\Program Files\System Center 2012\Operations Manager\Server\SQL Script for Update Roll ups , select the "update_rollup_mom_db" file and then click Open.
  4. When the file is loaded, click "Execute" in the SQL Editor tool bar
  5. Your Result should look something like:

    RowsAffected3

9. Import the management Pack

  1. Start the System Center Operations Manager Console and select the "Administration pane"
  2. Right click "Management Pack" and click "Import Management Packs…"
  3. In the "Import Management Packs" and click "Add" and click "Add from Disk…"
  4. Browse to "D:\Program Files\System Center 2012\Operations Manager\Server\Management Packs for Update Rollups" and select the management Pack’s in that folder
    • Microsoft.SystemCenter.AlertAttachment.mpb
    • Microsoft.SystemCenter.IntelliTraceProfiling.mpb
      • Microsoft.SystemCenter.IntelliTraceCollectorInstallation.mpb which should be installed from SCOM 2012 SP1
      • MediaMicrosoft.Windows.InternetInformationServices.Common.mpb which should be installed from the online catalog
    • Microsoft.SystemCenter.Visualization.Library.mpb
    • Microsoft.SystemCenter.Image.Library.mp
    • Microsoft.SystemCenter.Advisor.Internal.mpb
    • Microsoft.SystemCenter.Apm.Infrastructure.Monitoring.mp
    • Microsoft.SystemCenter.Apm.Infrastructure.mpb
    • Microsoft.SystemCenter.Apm.Library.mpb
    • Microsoft.SystemCenter.DataWarehouse.Report.Library.mp p
    • Microsoft.SystemCenter.DataWarehouse.Reports.mp
    • Microsoft.SystemCenter.DataWarehouse.ServiceLevel.Report.Library.mp
    • Microsoft.SystemCenter.TFSWISynchronization.mpb
    • Microsoft.SystemCenter.Visualization.Component.Library.mpb
  5. Click "Install"

    UpdateManagementPacks

  6. Click "Close"

10. Deploy the update to the agents

  1. Start the System Center Operations Manager Console and select the "Administration pane"
  2. Select " Device Management" and then "Pending Management"
  3. Select the a "Agent" and click "Approve"

    Aprove

  4. On the "Agent Update" page click "Update"

    Update

  5. when you open de the "Agent by Version" you should see something like this:

    Ready

More information on installing Update Rollup 8 for System Center Operations Manager 2012 sp1 can be found here. To install this Update Rollup 8 I used the deployment plan from Kevin Holman

Alert Description in Different Language

Standard

I was running into the issue that my alert description was in my native language Dutch. Nice feature to have but I prefer the alert description to be in English.

I Took the following steps to resolve the issue

  1. Go to the server that is generated the Alert or Warning
  2. Open the Registry Editor. "Windows-Key + R" and type "regedit"

    WindowsRRegedit

  3. Browse to the following Registry Key: "[HKEY_USERS\.DEFAULT\Control Panel\International]
  4. Right Click the String Value "Locale" and click "Modify"

    ModifyStringValue

  5. Change the "Value Data" to "00000409"

    EditString

  6. Browse to the following Registry key: "[HKEY_USERS\S-1-5-19\Control Panel\International]
  7. Repeat step "4" and step "5"
  8. Browse to the following Registry key: "[HKEY_USERS\S-1-5-20\Control Panel\International]
  9. Repeat step "4" and step "5"

When the server Generates an Alert the Alert Description should be in English