Timeout during wmi connect

[rastislav_danis]

Hi,

customer has several remote winOS vms for remote wmi monitoring, that responds slowly. Wbemtest utility shows 15+ seconds until connection is made. Remote Windows Extension apparently doesn't wait so long so it treats such devices with "access denied" error message in log. What exactly is time limit of WMI data source in extension 2.0 that needs to be fulfilled? Is there an option to extend this limit?

Thanks

[Peter_Youssef]

Hello @rastislav_danis 

If possible to review the attached resources:

• data-sources/wmi-extensions 
• connecting-to-wmi-remotely 
• server-manager 
• allowing-users-access-to-a-specific-wmi-namespace 

Hoping it adds value.

KR,

Peter.

[rastislav_danis]

Hi Peter

thanks for sources, i was just wondering if wmi data source in ext 2.0 has some built in timeout limit. As i said wbemtest utility connects well (even from AG vm, that is used for this extension). Problem is probably in some network stuff, wbemtest wait for response, but extension probably not.

[Peter_Youssef]

Hi @rastislav_danis 

Might be network or FW settings, so kindly join a call with NW or FW team to pinpoint the RC.

• find a stable configuration and try to simulate and apply the same.

There is  solution should be applied on the target endpoints not on the AG: 

• https://checkmk.atlassian.net/wiki/spaces/KB/pages/9470631/How-to+increase+WMI+timeout
• https://help.pdq.com/hc/en-us/articles/220532387-WMI-operation-timed-out 

BR,

peter.

[rastislav_danis]

Sorry, but i was asking about capability (timeout value) of extensions 2.0 wmi data source. Endpoint is ok obviously. And also i'm not trying to solve customer's reasons of such slow responses.

[Peter_Youssef]

Hi @rastislav_danis 

• If it possible to check the configurations listed in the attached Activegates directories regarding WMI extension.
• Access denied : check the assigned permissions.
  Linux

Windows

BR,

Peter

[p_devulapalli]

Hi @rastislav_danis , I think the default timeout is 10 sec. Can you please try adding timeout attribute under wmiRemote and see if that helps ?

"wmiRemote": {
      "devices": [
        {
          "host": "x.x.x.x",
          "user": "DOMAIN\\Administrator",
          "password": "Pass",
          "timeout": 30
        }
      ]
    },

[rastislav_danis]

Hi, nice try but unfortunately it's not possible:

[Peter_Youssef]

Hi @rastislav_danis 

You can define the timeout in the schema, so when you perform check it won't fail.

BR,

[rastislav_danis]

When i add timeout parameter to schema will it actually work as overrride to default?

[Peter_Youssef]

Yes, it should.

[rastislav_danis · Accepted solution]

Timeout is probably 10s as @p_devulapalli suggested. I was not able to extend it and in the end it seems ok, that such slow reponsing devices are not included in monitoring.