Advertisement
Advertisement
HPE IMC APM
WMI Configuration Examples
Part number: 5200-1358
Software version: IMC APM 7.2 (E0401)
Document version: 1
The information in this document is subject to change without notice.
© Copyright 2016 Hewlett Packard Enterprise Development LP
Contents
Introduction ····················································································· 1
Prerequisites ··················································································· 1
Configuration restrictions and guidelines ··············································· 1
Example: Using WMI to monitor application indexes ································ 1
i
Introduction
This document provides an example for using WMI to monitor application indexes.
Windows management instrumentation (WMI) provides a standard and a basic infrastructure for accessing, configuring, managing, and monitoring Windows resources.
WMI provides multiple interfaces to access Windows-based services and resources. To monitor indexes for applications like Windows, IIS server, Office SharePoint, and Exchange, you can use WMI for data collection.
Prerequisites
Before you use WMI to monitor application indexes, perform the following configurations on the target application server (computer):
•
Start Windows services that are essential to WMI.
•
Configure COM.
•
Configure WMI security.
•
Configure user permissions.
•
Configure local security.
•
Configure the firewall.
Configuration restrictions and guidelines
When you use WMI to monitor application indexes, follow these restrictions and guidelines:
•
If the target computer is installed with Windows XP SP2, use the netsh firewall set service
RemoteAdmin command to configure the Windows firewall to allow remote control.
•
If the target computer joins a domain, access the remote host by entering the username in the format domain name \ username . If the computer does not join any domain, you can enter the username or use the format host name \ username or IP \ username .
•
If the target computer runs Windows XP, make sure the remote login does not require the guest account to be used.
Example: Using WMI to monitor application indexes
Configuring the application server
Starting Windows services that are essential to WMI
1. Select Start > Run , and then enter services.msc
.
The Services page appears.
2. Select part or all of the following services.
3. Right-click the selected services and select Start .
1
COM+ Event System
Remote Access Auto Connection Manager
Remote Access Connection Manager
Remote Procedure Call (RPC)
Remote Procedure Call (RPC) Locator
Remote Registry
Server
Windows Management Instrumentation
Windows Management Instrumentation Driver Extensions
WMI Performance Adapter
Workstation
Configuring COM
1. Select Start > Run , and enter dcomcnfg .
The Component Services page appears.
2. From the left navigation tree, select Component Services > Computers > My Computer .
3. Right-click My Computer and select Properties .
The My Computer Properties page appears.
4. On the Default Properties tab, perform the following operations:
Select Enable Distributed COM on this computer .
Select Connect for Default Authentication Level .
Select Identify or Impersonate for Default Impersonation Level .
5. Click OK .
Configuring WMI security
1. Select Start > Run , and enter wmimgmt.msc
.
The wmimgmt page appears.
2. From the left navigation tree, right-click WMI Control (Local) and select Properties .
The WMI Control (Local) Properties page appears.
3. On the Security tab, click Security at the lower right corner.
The Security for Root page appears.
4. Verify that the group to which the user belongs has all the required permissions. If not, add permissions in the Permissions for Administrators area.
5. Click OK .
Configuring user permissions
1. Select Start > Run , and enter gpedit.msc
.
The Local Group Policy Editor page appears.
2. From the left navigation tree, select Computer Configuration > Windows Settings > Security
Settings > Local Policies > User Rights Assignment .
3. From the policy list on the right, double-click or right-click Impersonate a client after authentication , and select Properties .
The Impersonate a client after authentication Properties page appears.
2
4. Add the user on the Local Security Setting tab.
5. Click OK .
NOTE:
Add the server after the user is added. The user must have administrator permissions.
Configuring local security
1. Select Start > Run , and enter secpol.msc
.
The Local Security Policy page appears.
2. From the left navigation tree, select Local Policies > Security Options .
3. From the policy list on the right, double-click or right-click Network access: Sharing and security model for local accounts , and select Properties .
The Network access: Sharing and security model for local accounts Properties page appears.
4. On the Local Security Setting tab, select Classic-local users authenticate as themselves .
5. Click OK , and reboot the operating system.
Configuring the firewall
Configure the firewall to make sure the computer is accessible remotely or through port 135.
Adding the application to APM
1. Log in to IMC, and click the Resource tab.
2. From the left navigation tree, select Application Manager > Add Application .
The Add Application page displays all application types that IMC can monitor.
3. Click Windows , and enter the IP address , username and password .
The username can be in the format host name \ username or IP \ username
, as shown in Figure 1 and Figure 2 .
3
Figure 1 Username in IP\username format
Figure 2 Username in host name\username format
4
4. Click OK .
A success message appears, as shown in Figure 3 .
Figure 3 Success message
Viewing Windows monitor reports in APM
1. Click the Resource tab.
2. From the navigation tree, select Application Manager > Application Monitor .
The application monitor list appears.
3. Click Windows_192.168.40.77
.
The monitor report appears, as shown in Figure 4 .
Figure 4 Viewing the Windows monitor report
5
6
Download
Advertisement