Active Directory Monitors shows N/A

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 wmiadap.exe /f fromthe command line.  Microsoft have posted an article KB 820847 on thisissue regarding Exchange servers, it appears it also effects ADmonitors the same.After running this command, just wait 10 or 15minutes or so and you should see the monitors coming to life.
          • Related Articles

          • 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 ...
          • 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 ...
          • 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 ...
          • 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 ...
          • No Database listed while adding MSSQL Monitors

            Issue/Scenario: When I try to add MSSQL performance Monitors, I get to the stage to add databases but there were no databases listed .  This issue could occur if   32bit MSSQL is installed  on a 64bit Widows2008  R2. Solution/Workaround: Apparently ...