System Center Essentials Team Blog

News and support on Microsoft SCE

Essentials 2010 – Improving Default Monitoring

Essentials 2010 – Improving Default Monitoring

  • Comments 2
  • Likes

The monitoring capability within Essentials comes from Management Packs, and the majority Management Packs that work with Operations Manager also work with Essentials. This is great, because it means there is a wealth of deep monitoring that is available for Essentials.

During the Beta and RC period we’ve had lots of great feedback (please keep it coming), and some of this feedback has focused on the monitoring capabilities provided by Management Packs. This post covers the common feedback, and configuration changes to improve the monitoring experience for the following management packs:

Windows Client Operating System Management Pack

Alerts

There is an issue with the Windows 7 Client OS MP that will generate errors after the initial import of the management pack. You are likely to see 4 alerts that are very similar. You can dismiss the alerts and they should not reappear. The 4 alerts you are likely to see will all start with:

OleDb Module encountered a failure 0x80040e37 during execution and will post it as output data item. : Invalid object name

and then have one of the following:

  • 'Win7.vWin7MemoryHealthAggregationRAM'.
  • 'Win7.vWin7ShellPerfAggregationComputer'.
  • 'Win7.vWin7DiskFailureAggregationDisk'.
  • 'Win7.vWin7DiskFailureAggregationComputer'.

These issues may be fixed in a future release of the Windows 7 Client Operating System Management Pack. When an updated version of a management pack is available you will see a yellow notification bar at the top of the Computers workspace in the Essentials console.

Performance Collection

By default, if you attempt to view CPU Performance, Processor Queue Length or Memory in the Computers workspace for computers running XP, Vista or Windows 7 the graphs will be empty.

To show information for Client Computers you will need to enable the following rules for each OS:

  • Memory Available Megabytes
  • Processor % Processor Time Total
  • System Processor Queue Length

To enable collection of these performance counters:

  1. Go to the Authoring Workspace
  2. Expand Management Pack Objects and select Rules
  3. In the Look For box (press Ctrl-F if it is not visible) enter Memory Available and click Find Now
  4. Select Memory Available Megabytes for each client operating system to enable
  5. Select Overrides -> Override this Rule -> For all objects of class
  6. Check the box next to Enabled, change the Override Value to True and click OK
  7. Repeat steps 3 to 6, searching for:
    • Processor % Processor
    • Processor Queue

More information is in the Management Pack Guide.

Exchange 2007 Management Pack

By default, the Microsoft Exchange 2007 Management Pack will not automatically discover any Exchange 2007 Server roles, and no monitoring is distributed to Exchange 2007 servers.

Initially, the only discovery that runs automatically is called the Exchange 2007 Discovery Helper Discovery. It is a lightweight registry discovery that runs on all Windows servers. Its only purpose is to discover Exchange 2007 servers in your environment without actually starting monitoring.

To verify that Discovery Helper has discovered your Exchange 2007 servers

  1. Ensure that you have not scoped your views.
  2. Go to the Discovered Inventory view in the Monitoring section of the Operations console.
  3. Right-click and choose Select Target Type.
  4. In the Look for field, type Exchange 2007 Discovery Helper, select it, and then click OK. A list of Exchange 2007 servers appears with a status of “Not Monitored.”

If no Exchange 2007 servers are discovered, you might want to make the discovery run more frequently than the default. You can change the frequency of the Exchange 2007 Discovery Helper Discovery in Object Discoveries located under Authoring in the Operations console.

To enable Exchange 2007 Server Role Discovery

  1. Go to the Object Discoveries node located under Authoring in the Operations console.
  2. In the Look for field, type Exchange 2007 Server Role and click Enter. A list of Exchange 2007 Server Role Discoveries appears. You need to enable Server Role Discoveries of the following discoveries:

Discovery Name

Description

Exchange 2007 CCR Clustered Mailbox Server Role Discovery

Discovers CCR and SCC clustered Mailbox servers

Exchange 2007 CCR Node Role Discovery

Discovers CCR node servers in a CCR cluster (the physical nodes)

Exchange 2007 Standalone CCR Node Discovery

Discovers standalone CCR node roles (nodes that are participating in log shipping but are not part of an active Mailbox server) and standalone mailbox roles

Exchange 2007 CAS Role Discovery

Discovers Client Access server roles

Exchange 2007 Hub Transport Role Discovery

Discovers Hub Transport server roles

Exchange 2007 Edge Role Discovery

Discovers Edge Transport server roles

Exchange 2007 UM Role Discovery

Discovers Unified Messaging (UM) roles

For example, to enable discovery of all Hub Transport servers, right-click the Exchange 2007 Hub Transport Role Discovery and select Overrides\Enable the Object Discovery\for all objects of type Exchange 2007 Discovery Helper. If you want, you can choose to discover servers using a group (containing Exchange 2007 Discovery Helper instances) or a single instance of Exchange 2007 Discovery Helper. It is also possible to use a group containing the computer objects of the Exchange servers.

More information is in the Management Pack Guide and also on the Operations Manager blog.

Exchange 2010 Management Pack

Importing the Exchange 2010 Management Pack on the Release Candidate of Essentials 2010 will cause the following alert to be generated:

Critical hotfixes required for reliable operation of the Exchange Server 2010 and other management packs are not installed on this server. Please see the appropriate KB article for more information, and to download the required hotfix.

The hotfixes referred to by this alert are included in the released version of Essentials 2010.

These updates resolve issues affecting state rollup using dependency monitors. These updates allow the Exchange Server 2010 Management Pack to accurately monitor whether Exchange databases are mounted. Without these updates you are also likely to see inaccurate availability reporting.

If desired, you can disable this alert:

  1. Go to the Authoring workspace
  2. Expand Management Pack Objects and select Rules
  3. In the Look For box (press Ctrl-F if it is not visible) enter SCOM and click Find Now
  4. Select The required SCOM hotfixes for Exchange MP are not installed.
  5. Select Overrides -> Disable the Rule -> For all objects of class

This is only a temporary workaround for use with the RC and should be reverted when upgrading to the RTM version of Essentials 2010.

More information is in the Management Pack Guide

SQL Server 2008 Management Pack

Monitoring SQL 2008

A number of workflows in the SQL Server 2008 Management Pack run scripts, which rely on SQL Data Management Objects (SQL-DMO) to query information from the SQL Server. SQL-DMO is now deprecated and is not shipped as a part of SQL Server 2008. Every system with SQL Server 2008 that will be monitored must have SQL-DMO installed from the Microsoft SQL Server 2005 Backward Compatibility Components.

To install SQL-DMO on computers running SQL Server 2008:

  1. On the Microsoft SQL Server 2008 Feature Pack, August 2008 download page, in the Microsoft SQL Server 2005 Backward Compatibility Components section, download the package that is appropriate for the version of SQL Server.
  2. Run the .msi file on the computers running SQL Server 2008 that the SQL Server 2008 Management Pack will monitor.
  3. On the Feature Selection screen, ensure that the SQL Distributed Management Objects (SQL-DMO) feature is set to This feature will be installed on local hard drive. None of the other features are required for the SQL Server 2008 Management Pack.
  4. Complete the installation wizard to install the SQL-DMO backward compatibility components.

These issues may be fixed in a future release of the SQL Server 2008 Management Pack. When an updated version of a management pack is available you will see a yellow notification bar at the top of the Computers workspace in the Essentials console.

Alerts

If you are using the Express edition of SQL (installed by Essentials) you will see the following errors:

Warning Service Check Data Source Module Failed Execution

Warning Service Check Probe Module Failed Execution

Both errors will mention the following workflow:

Workflow name: Microsoft.SQLServer.2008.DBEngine.FullTextSearchServiceMonitor or

Workflow name: Microsoft.SQLServer.2005.DBEngine.FullTextSearchServiceMonitor

This will happen on any system that has SQL installed without the Full Text Search Engine. You can apply an override on that monitor to disable it for the systems that don't have that service installed.

To disable these monitors, perform the following steps:

  1. Go to the Authoring workspace
  2. Expand Management Pack Objects and select Monitors
  3. In the Look For box (press Ctrl-F if it is not visible) enter Full Text and click Find Now
  4. In turn, select each of the SQL Server Full Text Search Service Monitor (one for SQL 2005, and the other for SQL 2008)
  5. Select Overrides -> Disable the Monitor -> For all objects of class

More information is in the Management Pack Guide.

      Comments
      • This is a great post,

        is it still applicable to RTM?

      • The following guidance is no longer valid with RTM:

        * Exchange 2010 Management Pack (the Essentials RTM includes the required fixes)

        The following guidance is still valid for RTM:

        * Client Operating System

        * Exchange 2007

        * SQL Server

        Thanks!

      Your comment has been posted.   Close
      Thank you, your comment requires moderation so it may take a while to appear.   Close
      Leave a Comment