Probe "Windows - Active Connections" error result file can't be fetched because it doesn't exist - Known Error

Probe "Windows - Active Connections" error result file can't be fetched because it doesn't exist Description Probe "Windows - Active Connections" error result file can't be fetched because it doesn't exist.

The "Windows - Active Connections" probe is triggered even if there is no access to the admin$ or Powershell.

The following error is logged in the discovery: The result file \\ \admin$\temp\psscript_output_64789e32-63de-4db3-9520-b18d4e9c6267.txt can't be fetched because it doesn't existHRESULT

Powershell and admin$ access are required for this probe and therefore the error is expected. However, instead of getting an error the probe should be skipped and a message should be logged in the discovery log like: "Probe cannot be launched because remote Powershell probes require admin share access and PowerShell on the target" "Probe cannot be launched because the target's admin share is not accessible from the MID server"

Steps to Reproduce

1. Discover a windows server that does not have admin$ access 2. See message like following in the discovery log: The result file \\ \admin$\temp\psscript_output_64789e32-63de-4db3-9520-b18d4e9c6267.txt can't be fetched because it doesn't existHRESULT: [-2146233087] 3. Click on the "ECC Queue Input" from the message and confirm this message came from the "Windows - Active Connections" probe

Workaround Powershell and admin$ access are required so that the "Windows - Active Connections" probe can run successfully.