Issues with Windows server discovery "Active, couldn't classify: No WMI connec"

[ahmadadnan]

Hi,

I am facing issue while discovering windows server.

I am running discovery on a subnet in which few windows servers has been discovered but for few I am getting below errors.

When I checked in devices tab of Discovery status, I am getting error in completed activity "Active, couldn't classify: No WMI connec" and in the discovery log it is giving me message as "The result file \\10.12.70.20\admin$\temp\psscript_output_4778de1d-ec89-44cf-9745-ebcd9fa31706.txt can't be fetched because it doesn't exist". But in the server this file has been created, I have checked this.

Can anyone please suggest me how to troubleshoot this because few Servers has been discovered of the same subnet.

I have validated the credentials, and it is working fine.

Please find the ECC queue input message:

Regards,

Adnan

[Alexey7]

The only suggestion I have is to check if you can access this file with the credentials configured. Make sure you are using the same login/password.

[Uday Gonuguntla]

Hello @ahmadadnan ,

I have also faced this error in my environment.

Problem: Result file can't be fetched because it doesn't exist. 

Reason of this error: Discovery is trying to access target device admin$ folder but it couldn't access.

Solution: Ask your windows team to provide admin$ access to discovery account.

Mark it as correct answer if it resolves your issue.

Thank you......