Probe timeouts - Discovery

[Jason Stephens]

We are seeing a lot of WMI probe timeouts when we run discovery - mostly the "Installed Software" probe. I have messed with the "wmi_timeout" parameter (both more and less timeout), and I can't seem to get rid of these warnings.

As always thanks for the help!

Jason

[aleck_lin]

If you're on Berlin Patch 1, the default timeout was a bit short (3 min), especially for installed software. To adjust the timeout, use "process_timeout" instead. Starting Berlin Patch 2, the timeout has been readjusted to 5 min and the installed software probe has a timeout of 15 minutes.

The use of "wmi_timeout" will be preferred in the future, but that applies for Patch 2 and later.

I've recently updated the wiki. http://wiki.servicenow.com/index.php?title=WMIRunner_Probe

[dvientos]

I have had the same issue with installed software not populating during a discovery. I am new to Discovery so I am not sure where i need to edit the "process_timeout" setting.

Thanks

Domenic

[aleck_lin]

My memory really fails me these days...

It turns out that you need to adjust both the "wmi_timeout" and "process_timeout" before Berlin Patch 1. I have simplified it by choosing just adjusting the wmi_timeout starting with Patch 1. Sorry about that.

[dan_sherwin]

Hi Domenic,

Here is what happened when the probe ran exide:

Script execution time was exceeded on script "C:\SErvice Now\Milton\agent\lib\WMIRunner.js".
Script execution was terminated.

I would adjust the parameters mentioned above.

-Dan