WMI Sensors monitoring

Posted by DmitrySemenov on Server Fault See other posts from Server Fault or by DmitrySemenov
Published on 2012-10-30T22:20:32Z Indexed on 2012/10/30 23:04 UTC
Read the original article Hit count: 293

Filed under:

Windows

|

windows-server-2008

|

monitoring

|

wmi

Monitoring tool Paessler stopped to monitor WMI Windows Sensors

Paessler is Updated to version 12.4.5.3165. (10/30/2012 1:44:11 PM)
Paessler windows sensors (against windows server 2008 R2 web edition) stopped to work (no changes have been made on server that we monitor) with the message

Connection could not be established (80070005: Access is denied - Host: 192.168.2.10, User: Administrator, Password: **, Domain: ntlmdomain:) (code: PE015)

However if I go to Virtual machine used to run Paessler and the following cscript runs successfully:

strComputer = "192.168.2.10"
Set objSWbemLocator = CreateObject("WbemScripting.SWbemLocator")
Set objSWbemServices = objSWbemLocator.ConnectServer _
    (strComputer, "root\cimv2", _
    "Administrator", "pass")
Set colProcessList = objSWbemServices.ExecQuery( _
    "Select * From Win32_Processor")
For Each objProcess in colProcessList
    Wscript.Echo "Process Name: " & objProcess.Name 
Next

I'm getting output

C:\>cscript test.vbs
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

Process Name: Intel(R) Xeon(R) CPU           X5680  @ 3.33GHz
Process Name: Intel(R) Xeon(R) CPU           X5680  @ 3.33GHz

So WMI works

a. I gave Administrator credentials for Device to monitor in Paessler setting, the same I used in the script above

b. I restarted windows server (broken sensors) - but this didn't help

c. I restarted Paessler probe service - no effect

any ideas?

Developer IT