Testing the WMI connection with WBEMTEST
To check if the connection between OpManager server and the monitored device is clear, Please perform the below steps,
1. From OpManager server, click on "Start>Run--->wbemtest" and click on ok. This will launch WMI tester.
2. Click on "Connect" and in the top box type in \\<Device Name>\root\cimv2
3. In the Credentials type in User name and password used in OpManager and choose "Connect"
4. If all the query buttons in WMI tester are getting activated means there is no trouble with the connection and WMI.
If not check the username or password or firewall or the services. If you have any trouble, Send us the screenshot for further analysis.
1. From OpManager server, click on "Start>Run--->wbemtest" and click on ok. This will launch WMI tester.
2. Click on "Connect" and in the top box type in \\<Device Name>\root\cimv2
3. In the Credentials type in User name and password used in OpManager and choose "Connect"
4. If all the query buttons in WMI tester are getting activated means there is no trouble with the connection and WMI.
If not check the username or password or firewall or the services. If you have any trouble, Send us the screenshot for further analysis.
P.S : Replace the highlighted device name with problematic device name or IP address.
New to ADSelfService Plus?
Related Articles
Configuring a non-admin user for WMI monitoring (domain level)
For non-admin users to perform WMI monitoring in OpManager, the user profiles need to be configured accordingly in your network. This can be done: On a device level (configuring individual devices) - Link to KB On a domain level (configuring the ...WMI credentials does not pass with error "RPC Server Unavailable"
Steps to troubleshoot "RPC Server Unavailable Error" when adding Windows Server through WMI mode in OpManager. 1) Try to add the server using domain-name\username and with username alone. 2) Check whether you are able to ping the remote windows ...Rebuilding WMI repository
Description If your Windows device is having issues reading from the Windows Management Interface (WMI) repository, you may need to re-sync the repository as a troubleshooting step Misconfigured Monitoring Service gives the following error: "102 ...Configuring a non admin user for WMI monitoring
Configuring a non-admin user for WMI monitoring You can configure a regular Windows user to access WMI information by adding the necessary user account to the Distributed COM Users and the Performance Monitor Users group using lusrmgr.msc, and then ...Third party SSL certificate implementation in OpManager