SolutionPack for Microsoft SCOM Summary Sheet – Service Assurance Suite 9.4

Table of Contents

Overview

Learn how to install and configure the SolutionPack for Microsoft System Center Operation Manager (SCOM). This SolutionPack provides an integrated experience for the management of Microsoft Windows systems and the discovery of their workloads across platforms in the data center.

The SolutionPack for Microsoft SCOM helps you:
  • Manage Windows servers and their performance
  • Manage key performance indicators (KPIs)
  • Manage application-related metrics
  • Report on Microsoft applications and services, including Microsoft Operations Manager (MOM), server and agents, Active Directory, DNS, SQL, and Internet Information Services (IIS)
  • Report on the main management packs of MOM
  • Easily expand on new report sets per management pack
Back to Top

Technical specifications

SolutionPack version

1.0

Compatible Watch4net versions

6.3u1 and later

Data collection method

SQL collector

Supported versions

System Center 2012 Operations Manager

System Center 2012 R2 Operations Manager

Supported Microsoft applications and services

Operations Manager

Server and agents

Active Directory

DNS

SQL 2012

IIS

User privilege requirements

An SQL or Windows user must have SELECT and CONNECT privileges on the SCOM Operations Manager Data Warehouse Database called OperationsManagerDW.

Main reports

Microsoft Products/Microsoft System Center
Displays the health (%) of the agents with an alert meter, data access and NT service statistics, and general information about the agents per management server
Microsoft Products/Microsoft Windows Operating System
Provides the OS distribution, top 10 processor consuming servers, and a complete list of servers.
Microsoft Products/Microsoft Active Directory
Provides the established TCP connections and the LDAP client sessions per server.
Microsoft Products/Microsoft SQL
Shows user connections per database and the databases with the lowest amount of free space.
Microsoft Products
Displays the product names, number of product instances, and the DNS and IIS data.
Managed Windows Server
Provides CPU usage %, free memory, and free page memory.
Per Operating System
Displays the server types and the number of servers.

Back to Top

Where to find the latest SolutionPack software

Install the latest core software update for your product suite. SolutionPacks distributed with core software have a 30-day free evaluation period. If you plan to use the software longer than 30 days, you must install a SolutionPack license before the trial period ends.

This 30-day free evaluation only applies to new installations and is not available for upgraded installations. If you upgrade the core software and want to try a new SolutionPack, you must request a license for that SolutionPack by completing a Support Request (SR) form, which is available on the EMC Online Support website at http://support.emc.com.

Back to Top

Installing the SolutionPack

Before you begin

  • Determine whether you need a SolutionPack license file by checking the feature names and expiration dates listed in Centralized Management > License Management. If the license is not listed, obtain one by completing a Support Request (SR) form, which you can find on the EMC support website http://support.emc.com.

  • Make sure the core modules, such as the Module-Manager, are up-to-date on all servers since not all module dependencies are validated during the SolutionPack installation. See the Watch4net Installation and Configuration Guide provides for more information.

Procedure

  1. Log in to Centralized Management.
  2. Select SOLUTIONPACK CENTER.
  3. Select the SolutionPack for SCOM in the Browse and Install SolutionPacks screen.
  4. Read the summary information and click Install.
    You can select either Simple or Advanced as the configuration mode. Simple mode lets you select Windows authentication for database access. Advanced mode is typically for the user who is configuring the SQL server connection using the JDBC driver.
  5. When you select Simple as the configuration mode for the OperationsManagerDW (SCOM Operations Manager Data Warehouse) database, set these values:
    • Hostname or IP address of the database server
    • Database port
    • Instance name
    • Choose if you want to use Windows authentication
    • Username
    • Password
  6. When you select Advanced as the configuration mode for the OperationsManagerDW database, set these values:
    • Connection string
    • Username
    • Password

After you finish

After the installation is complete, select Centralized Management > SolutionPack to verify the installed SolutionPack.

Back to Top

Confirming report creation

After you install a SolutionPack, you can view its reports.

To view the reports:

Procedure

  1. Go to User Interface > Report Library.
  2. Click the SolutionPack to view its reports.

Results

It may take up to an hour to display all relevant information in these reports.

Back to Top

Troubleshooting

Report display problems

Back to Top

What to do if data does not appear in any reports

Procedure

  1. After the completion of at least three collection cycles, verify if data is populating into the reports. If there is still no data in the reports, continue to the next step.
  2. Run the scheduled task to import data into reports. If there is still no data in the reports, continue to the next step.
  3. To view the log files for errors, go to Centralized Management and click Collecting > Collector-Manager::<instance name> > Log Files.
Back to Top

Running a scheduled task to import data into reports

After you push a new configuration into a collector, a scheduled task runs and populates the reports with new data. You can manually run the scheduled task to import the data more quickly.

Before you begin

Allow at least three polling cycles to pass before manually running the scheduled task.

Procedure

  1. Click Administration.
  2. Click Centralized Management.
  3. Expand Scheduled Tasks.
  4. Click Database.
  5. Select the import-properties-Default task.
  6. Click Run Now.
  7. Confirm success in running the task in the Last Result and Last Result Time columns.
Back to Top

What to do if data does not appear in some reports

Procedure

  1. Run the scheduled task to import data into reports. If there is still no data in the reports, continue to step 2.
  2. Search for the metric in the database.
  3. To view the log files for errors, go to Centralized Management and click Collecting > Collector-Manager::<instance name> > Log Files.
Back to Top

Searching for metrics in the database

You can verify that a metric is being collected and used for reporting when you search and find the metric in the database.

Procedure

  1. Go to the Administration page.
  2. Under Modules, click Management of Database Modules.
  3. On the Metric Selection page, create the filter, type the number of results, and select the properties to display for the metric.
    For example, to list up to 100 results of the SignalWait Time metric with the properties of device and IP, type name=='SignalWaitTime' in the Filter field, 100 in the Maximum results field, and select device and IP for the Properties to show.
  4. Click Query.
    A list of the metric results appears. If nothing displays, the metric is not being collected.
Back to Top

What to do when raw data continues to appear on reports

If the SQL collector continues to collect unprocessed data, which appears as zeros on reports, after three polling cycles, follow these instructions.

Procedure

  1. Log in into the SQL server.
  2. Execute the SELECT MAX(vPR.DateTime) AS LatestDateTime FROM Perf.vPerfRaw AS vPR query to display the last date and time in which data was written to the database.
  3. If this is not a realtime value, check the Microsoft System Center Operation Manager for issues.

Example

Back to Top

Viewing collector errors in the Collector-Manager log files

Review the Collector-Manager log files to troubleshoot problems with data collection.

Procedure

  1. Click Administration.
  2. Click Centralized Management.
  3. Expand Collecting.
  4. Click the Collector-Manager for your collector instance.
    Collector-Manager::<Collector-Manager instance> - <physical_host_ID>
  5. Expand Log Files and click the View File icon to review the configuration error messages.
Back to Top