Windows 2022

[jmarchand52]

Hi,

I am very happy with aiowmi code since many years to monitor our WIndows 2019 servers. Thanks a lof for this tool !

I try to use it to monitor a new Windows 2022 server.

Since a Windows 2019 server, I success with this PowerShell command to request the Windows 2022 server :
Get-WmiObject -query "SELECT * FROM Win32_UTCTime" -ComputerName vm8-rdp
Note that the delay for the response is more longer to ask the W2022 server than to ask W2019 servers.

But since the Linux VM where aiowmi is installed, I don't success with
/usr/local/aiowmi/contrib/wmic_server/wmic_client.sh -i shinken -t 'xxxxx' -u http://172.25.6.242:2313/wmic -h vm8-rdp -q 'SELECT * FROM Win32_UTCTime' .

I get

HTTP/1.1 200 OK
Server: gunicorn/19.9.0
Date: Mon, 11 Nov 2024 08:52:19 GMT
Connection: close
Content-Type: text/html; charset=utf-8
Content-Length: 64

Problem with the wmi query on the target host. ACCESS_DENIED (5)root@flexlm:/usr/local/aiowmi#

The same command is ok to request a Windows 2019 server
Into the Windows 2022, I see that the logon of the "shinken" account is OK. So I think that it is not a firewall or authentification problem

Have you any idea ? Is it possible to configure aiowmi to use a more longer timeout ?

Best regards,

Joel

[joente]

The wmic_server.py is using a Connection instance and makes the call to connect(). This function accepts a timeout argument which will be used for practically all following requests. The default timeout is 10 seconds.

[jmarchand52]

Thanks for your response. I do many checks without success. Are you sure that your code can connect to a Windows 2022 server ?

[joente]

Maybe the issue is related to the configuration of Windows 2022? Did you check this WMI troubleshooting page? https://docs.infrasonar.com/collectors/probes/wmi/wmi-troubleshooting/#access-denied

[jmarchand52]

Sorry for this ticket : on another Windows 2022 server, your tool works good with an local account member of Administrators group. I search now the reason why it does not work on the first Windows 2022 server, but clearly the problem is on my side.