AD Monitors Shows N/A in OpManager

AD Monitors Shows N/A in OpManager

This problem could due to the following reasons:

1)WMI is not configured properly in OpManager (OpManager uses WMI credential to monitor AD servers).
2)Required Monitors are not associated to the device  in OpManager.
3)WMI might not be responding to the OpManager WMI request
4)WMI is not working properly on the device itself.

1)WMI is not configured properly in OpManager (OpManager uses WMI credential to monitor AD servers).

Solution: Configuring WMI for multiple devices at a time :

1.Go to Admin --> Credential Settings
2.Click New
3.Configure the following parameters and click Add to add the credentials:

Credential Type: Windows

Name: Configure a name for the credential and also provide the description.

configure the Domain Name\Userd ID  and the password  (Example:- TestDomain\TestUser  Testpassword) > Click on "Add".

Associate the above credential using Quick Configuration Wizard to multiple devices:-

   1. From the Admin tab, select Quick Configuration Wizard.
   2. Select the option Associate a credential to several devices and click Next.
   3. All the available Credentials are listed. Select the Credential (the one you created above ).
   4. Select the devices to which you want to assign the credential from the left column  and move them to the right.
   5. Click Finish. The Credential is associated to the selected devices.

Configuring WMI credential using device snap shot page(Single device):

Go to device snap shot page > Click on "Click here to change" option besides Passwords >select "Use the below credential for the device" option >Type in the username (Ex:domainname\username)  and Password > Click on Test credential (make sure its gets passed) and then Ok to save it.

In case  OpManager itself is going to be AD server then leave the username and password blank and click OK as we do not require credential for the local host.

2)Required Monitors are not associated to the device  in OpManager.

Solution: Adding monitors for AD Monitors:-

Make sure the Category is selected as Domain controller  to have the AD monitors associated automatically to the device.

In case if the monitors are absent go to spacer Active Directory Monitors  section of the device snapshot page  and add the required AD monitors (Network Monitors ,Database Monitors  NTFRS Process Monitors , System Monitors, Performance Counters Monitors and LSASS Process Monitors ).

 
3)WMI might not be responding to the OpManager WMI request

Solution:Use the wmiadap utility to update the WMI performance classes from the performance libraries. Running wmiadap updates all the performance classes. The /f switch in the below command  forces an update of the WMI classes from the performance libraries.

Step 1:

1. Go to the monitored device.
2. Click Start-->Run,
    For Windows 2000 winmgmt /resyncperf' command.
    For Windows XP and 2003 'wmiadap /f' command.
3. After running this command about 4 times, wait for an hour and check whether  AD monitors shows data.

Step: 2

1. Go to the monitored device.
2. Click Start-->Run-->services.msc
3. Restart WMI service

4)WMI is not working properly on the device itself.

Solution: Still if you do not see the counter values, verify  whether OpManager server is able to pull up AD counters information  by executing the following queries.If you are able to pull the information for the following queries OpManager should be able to show the information in the dashboard.

If some of the below query gets the output and some of them not then the respective counters information associated with the non working classes will not be shown on the dash board.

1. From OpManager command prompt go to <OpManager\conf\application\scripts>
2. Execute the following commands and make sure we get the output from the device.

cscript wmiget.vbs devicename domainname\username password "ROOT\CIMV2" "SELECT * from Win32_PerfRawData_PerfNet_Server"
cscript wmiget.vbs devicename domainname\username password "ROOT\CIMV2" "SELECT * from Win32_Processor"
cscript wmiget.vbs devicename domainname\username password "ROOT\CIMV2" "SELECT * from Win32_PerfRawData_PerfOS_System"
cscript wmiget.vbs devicename domainname\username password "ROOT\CIMV2" "SELECT * from Win32_PerfRawData_PerfOS_Memory"
cscript wmiget.vbs devicename domainname\username password "ROOT\CIMV2" "SELECT * from Win32_PerfRawData_NTDS_NTDS"
cscript wmiget.vbs devicename domainname\username password "ROOT\CIMV2" "SELECT * from Win32_PerfRawData_PerfProc_Process"
cscript wmiget.vbs devicename domainname\username password "ROOT\CIMV2" "SELECT * from Win32_OperatingSystem"
cscript wmiget.vbs devicename domainname\username password "ROOT\CIMV2" "SELECT * from Win32_LogicalDisk"
cscript wmiget.vbs devicename domainname\username password "ROOT\CIMV2" "SELECT * from Win32_PerfRawData_PerfOS_Processor"

If you are getting "Invalid class" error message for the above queries then either the corresponding wmi classes are absent or corrupted on the AD server.

Please refer the link below to re-register or rebuild the WMI classes.

http://windowsxp.mvps.org/repairwmi.htm

For any further assistance please  contact support@opmanager.com.
          • Related Articles

          • MSSQL Monitors not working - Shows N/A in OpManager

            This problem could due to the following reasons: 1)WMI is not configured properly in OpManager (OpManager uses WMI credential to monitor MSSQL servers). 2)Required Monitors are not associated to the device  in OpManager. 3)WMI might not be responding ...
          • Active Directory Monitors shows N/A

            Issue: Active Directory monitor shows N/A Reason: If the Active Directory services are not started whenthe WMI ADAP process is started, the performance counters are not transferred to WMI. Resolution: Go to the DC being monitored and run the command ...
          • Pre-Requisites For OpManager Implementation

            Here are some of the pre-requisites for OpManager implementation : ​ 1. Server (Physical\Virtual) to install OpManager application (One server for a standalone and multiple servers for Enterprise edition) according to the hardware requirement below, ...
          • Alarms for "Data Not Collected" monitors

            1.Please edit the NmsProcessesBE.conf file in OpManager\conf folder and search for the text CLEAN_DATA_INTERVAL 999999 . 2.Paste GENERATE_DATACOLL_EVENT true right after that. For example : CLEAN_DATA_INTERVAL 999999 GENERATE_DATACOLL_EVENT true ...
          • Difference between SNMP monitors and Traps

            S.No SNMP Monitors Traps 1 Pull Model: OpManager sends SNMP request to the SNMP agent running on the monitored device and receives the response. Push Model: Monitored device(SNMP agent) sends messages in the form of traps to the trap ...