SQL Agent Job Discovery in SCOM is empty

When implementing the SQL management pack the “SQL Agent Job state” is empty. Therefore there is no overview which jobs have ran successfully or have failed.

The SQL Server Management Pack includes an option to discover and monitor SQL Server Agent Jobs for SQL 2005/2008/2012.  The Discovery for this is disabled by default.

To use an override to change the setting for automatic discovery
1. In the Authoring pane, expand Management Pack Objects, and then click Object Discoveries.
2. On the Operations Manager toolbar, click Scope, and then filter the objects that appear in the details pane to include only SQL Server objects.
3. In the Operations Manager toolbar, use the Scope button to filter the list of objects, and then click SQL Server Agent Job.
4. On the Operations Manager toolbar, click Overrides, click Override the Object Discovery, and then click For all objects of class: SQL 20xx Agent

5. In the Override Properties dialog box, click the Override box for the Enabled parameter.
6. Under Management Pack, click New to create an unsealed version of the management pack or use an existing one, and then click OK, or select an unsealed management pack that you previously created in which to save this override. As a best practice, you should not save overrides to the Default Management Pack.

After you change the override setting, the object type is automatically discovered and appears in the Monitoring pane under SQL Server.

NOTE: The script runs every 14400 seconds so it can take up to 4 hours before the discovery takes place. You can shorten this by changing the discovery interval to for example 120 seconds. Don’t forget to change it back to default.

After the discovery the SQL Agent Job State





Why download management packs manually instead of from the catalog

When updating OpsMgr management packs the easiest way to do this is to show “Updates available for Installed Management Packs” in the console.

When doing this only the existing imported MP’s are updated.
If the MP is updated with new additional monitoring features it will not show up as needing an update. So if you use the console you will miss new ones.
Because of this I do not recommend using the console update feature but download the MSI from the catalog on the web at http://systemcenter.pinpoint.microsoft.com and extract them, if not you will end up missing MP’s you need.


Updating the Exchange 2010 Management Pack in OpsMgr 2007 and OpsMgr 2012

This is a step by step guide on how to update the Exchange Server 2010 management pack with System Center Operations Manager 2007 and 2012.

Installing a fresh installation of the Exchange 2010 MP see http://www.toolzz.com/?p=63

Operations Manager 2007 R2 requires a restart!
Operations Manager 2012 does not require a restart!
The Exchange Monitoring will have downtime during the upgrade of the correlation engine

This article is discusses how to update the Exchange 2010 management pack the proper way.

Step 1 – Checking the current version of the Exchange 2010 MP
1. Log on to the computer with an account that is a member of the Operations Manager Administrators role for the Operations Manager 2012 management group.
2. In the Operations console, click Administration.
3. Choose the Management Packs node,
4. Type Exchange in the search box and check if it is an older version and not already updated.

Step 2 – Updating the Exchange correlation Engine
The correlation update must run on from the server where it is successfully installed. Most likely (and recommended) the Correlation Engine will be installed and updated on the root management server (emulator).

Do the following steps on the RMS Emulator
1. Download the MP software from the Microsoft site http://www.microsoft.com/downloads/details.aspx?FamilyID=7150bfed-64a4-42a4-97a2-07048cca5d23&displaylang=en
2. Choose the proper version (X64)
3. Launch the MSI Package and run the installation and follow the installation

4. As mentioned before
Operations Manager 2007 R2 requires a restart after that you can continue to step 3
Operations Manager 2012 continue to step 3.

Step 3 – Import the Exchange 2010 Management Pack
1. Log on to the computer with an account that is a member of the Operations Manager Administrators role for the Operations Manager 2012 management group.
2. In the Operations console, click Administration.
3. Right-click the Management Packs node, and then click Import Management Packs.
4. The Import Management Packs wizard opens. Click Add, and then click Add from disk.
5. If prompted to connect to the online catalog, click No.
6. The Select Management Packs to import dialog box appears. Go to the directory where your management pack file is located as extracted in Step 1. By default, the location is C:\Program Files\System Center Management Packs.
7. Select both management pack files to import from that directory, and then click Open.
8. On the Select Management Packs page, the management packs that you selected for import are listed.

9. You will receive a prompt indicating that the management pack presents a security risk. This is due to the management pack’s use of agent proxying. Click Yes to allow the import.
10. The Import Management Packs page appears and shows the progress for each management pack. Each management pack is downloaded to a temporary directory, imported to Operations Manager, and then deleted from the temporary directory. If there is a problem at any stage of the import process, select the management pack in the list to view the status details. Click Close.
11. Check the C:\Program Files\Microsoft\Exchange Server\v14\Bin directory content if the update ran successfully

That’s all !
Because the configuration already took place during the initial installation of the MP the update does not require any adjustments.



Alerts from the HP management pack

Regarding my blog post on HP monitoring I get a lot of questions on errors which are generated by the HP management pack / SNMP hardware logs; these errors are displayed in the Computer State not in the Active Alerts.

The description is very poor but it suggests that there are issues in the HP Hardware logs.

Context: Date and Time: 11/11/2011 10:20:52 AM Property Name Property Value Processors_SNMP.HealthState HealthSuccess Cooling_SNMP. HealthState HealthSuccess RealtimeMonitors_SNMP.HealthState HealthSuccess TemperatureSensors_ SNMP.HealthState HealthSuccess Logs_SNMP.HealthState HealthError

Logs_SNMP.FailedComponent Integrated Management Log Server Others_SNMP.HealthState HealthSuccess Health explorer

The cause is in the computer’s local HP log which is in a bad state and has errors which are not resolved (cleared or fixed). Therefore it will stay in bad state.

The solution is most of the time very simple. Clearing the HP log on the local server and resetting the OpsMgr heath state will solve the issue. You can do this in the HP homepage on the local computer which is causing the issue.