Network Discovery not reporting scan issues when deep-scanning?

[MichaelArens]

Am i correct that when only using the Network Discovery sensor/hub we're not getting to see any possible scanning-issues on the cloud-site? Because obviously we can see that we're not getting the detailed information on the assets in the inventory, but on the other hand it's not very straightforward in troubleshooting where the issue lies (scanning-action added; credentials not selected/wrong;WMI-issues...)

[MichaelArens]

Hi David, not very clear of me, but I was referring specific to the deep-scans with credentials (discovery actions) where you at the moment get zero feedback if there are any credential or other config errors. (also some feedback in LS-site from what is actually scanning at the moment or in the scanning-que of het Network Discovery tools would be handy instead of having to log into the server itself to acces the hub/sensor there...)

Hopefully this will resolved soon and the NetworkDiscovery hub/sensor method don't feels so bèta anymore...

[DavidPK]

Hi Michael. 

 Thanks for your question! We're aware that the scanning action part can be a little confusing, and we're working on making it clearer.
Currently, if a scan runs without specific credentials, the chance of encountering errors is low. However, we know it's not ideal that there isn't a warning when this happens.

Rest assured, we do track which credentials were used and which ones were successful, and we're working on making that information more visible in LS Sites. We appreciate your feedback as it helps us improve the user experience.