In the event that ipMonitor is not finding any resources on a system using WMI, the following steps are recommended to verify connectivity and authentication:
1. The first thing you need to do is gather the account information being used by ipMonitor. This would be the Windows account being used by the ipMonitorSrv service and the Windows Credential being assigned to the Wizard/Monitor you are using.
??a. Logon to the ipMonitor system
??b. Run the ipMonitor Configuration Utility (\ipm9config.exe)
??c. Click "Service Settings"
??d. Note the account assigned to the service.
2. The next thing is to replicate ipMonitor???s environment before performing testing WMI connectivity.
??a. Logon to the ipMonitor system as the Windows account assigned to the ipMonitorSrv service (noted on step 1.d.). Note: If this account is ???LocalSystem???, simply login as the system???s local Administrator.
??b. Open a CMD prompt
??c. Type the following command:
Runas /user:[Domain\Account] wbemtest.exe
***where [Domain\Account] is the account information that was provided to the Credential being used by the Wizard/Monitor***
??d. Enter the password when prompted.
3. At this point, you should be running the WMI Tester in the same environment as ipMonitor and you are ready to send a query.
??a. Click "Connect"
??b. Within the top text box, enter the following:
***where [remote_sys] is the system you are attempting to scan.
??c. Do not enter any additional information and click "Connect"
??d. Once connected, click "Enum Classes"
??e. Within the "Superclass Info" dialogue box, select "Recursive" and click "Ok".
You should be presented with a long list of WMI Classes on that remote system. If no errors occurred, ipMonitor should successfully query the system. If any errors occurred, please refer to the article on Verifying WMI settings on the system being monitored.