Return
-
Title
Long time to run windows Server Discovery -
Description
We have a Computer discovery running against 3200 Servers, There are two nodes in the cluster. The collections is for "Accounts" only with everything else de-selected. It is taking 1.5 days for the discovery to run. We are seeing timeouts where task time for individual servers is a long time. -
Resolution
There is a default timeout of 1 hour for each computer being collected. It is a configurable parameter. To change it - stop windows service for all ER nodes. Then on each node machine, typically under "Program Files\Quest\Enterprise Reporter\Node" there should be a file "ReporterNode.exe.config". Backup the file and edit it to add the following line inside <appSettings> section :-
<add key="MaxComputerDiscoveryTimeInMS" value="900000" />
The value above is in milliseconds and I have set it to 15 minutes (15 * 60 * 1000). You can set it to the desired value. Then start node service on all machines for the timeout to take effect.