Discovery - Powershell Warnings & Long Discovery Times

[Frederico Lacer]

I've been attempting to figure out why we're getting 14-24 hour long discovery times. Looked into the discovery log to see a dozen different PowerShell commands timing out at either 120 or 300 seconds. These warnings are seen on mostly every schedule's discovery log, totaling to hundreds. I'm going to assume this is having a negative impact on our discovery times. 

For more context, I've looked into the Windows - ADM Multiprobe and set the Windows - Active Processes probe to "false". I also set-up a PowerShell timeout property for our discovery MID servers to timeout at 30 seconds instead of 300 (Default value). Even with this attempt, I'm still seeing those 120 and 300 second time outs in the discovery log. 

Here are a few of those errors, the bold ones are the two most common errors.

Failed to initialize PowerConsole, caused by: Remove-Module -Name PSReadLine timed out after 120 seconds.

Failed to initialize PowerConsole, caused by: mode con lines=1 cols=9999 timed out after 120 seconds.

Command: $cred = getCredential; $SNC_session = CreateNewCimSession timed out after 300 seconds.

Command: $context = startImpersonation timed out after 300 seconds.

Command: snc-decode-command | invoke-expression timed out after 300 seconds.

Command: Get-ChildItem "Drive:\Mid Server Name\agent\scripts\PowerShell\WMIFetch.psm1" -Filter *.psm1 | ForEach-Object { If (-Not (Get-Module -Name $_.BaseName)) { Import-Module -Name $_.FullName -Verbose -NoClobber } } timed out after 300 seconds.

[Doci1]

Hi, I have to confess that what is mentioned in the KB article is not working for me, we are still facing the same errors. I requested the access to MID server, if I will find out something, I will post it here...

[ctdemato]

I cannot see the kb and am having the same issue. Any advice?