Windows discovery takes a long time to complete or fails with errors like "PowershellProcessRunner was interrupted to complete in 600 seconds" in the classification phase or when the Windows Installed Software probe runs.
This is caused by multiple round trips between the MID Server and the target host, which is susceptible to network delays and MID Server load. This issue is seen in both WinRM and WMI protocols.
If discovery fails even if the target host has PowerShell installed on it, make sure the admin share is accessible from the MID server.
Steps to Reproduce
Any individual Windows server Discovery that takes in excess of 10 minutes. If you encounter this, you should consider an upgrade to the appropriate version.
This fix includes a number of Java code changes to offload work to the remote Windows server and improve performance significantly. Because of the scope of the changes, no workaround exists for this issue. Upgrade to Madrid Patch 3 OR to the New York release (any patch). Madrid Patch 4 and Patch 5 do not contain the fix at this time. Performance improvements can be dramatic for CPU and memory usage on the MID Server host.
Related Problem: PRB1308592