Windows Discovery failure

[venkataramac]

Hi,

While running the Discovery on Windows Server facing the below error. Help me to fix the issue.

[M Iftikhar]

Hi @venkataramac,

Based on the screenshot, the discovery log shows "Failed Exploring CI Pattern, Pattern name: Windows OS - Servers."

To troubleshoot this issue, please follow these steps:

1. Check the Pattern Log: Click on the "To Check Pattern Log Press Here" link in the discovery log. This will provide granular details on which specific step within the pattern is failing.

2. Verify MID Server and Credentials: Ensure the MID Server has a valid connection to the target Windows server. Also, verify that the credentials being used have the necessary permissions (e.g., administrative rights) to execute WMI and PowerShell commands.

3. Validate Firewall Rules: Confirm that there are no firewall rules blocking the required communication ports (e.g., ports for WMI and PowerShell remoting) between the MID Server and the target machine.

4. Review MID Server Health: Confirm that your MID Server is running correctly and has no issues in its logs.

The pattern log is the most important first step, as it will likely provide the specific error message needed to resolve the issue.

Thanks & Regards, 
Muhammad Iftikhar 
If my response helped, please mark it as the accepted solution so others can benefit as well. 

[Mannapuram]

@venkataramac  As per the screen shots, pattern is not able to get the log from name space "Root\MSCluster". This should not exactly stop the whole CI Identification (Classification was successful). Please find attached the screenshot showing the same step (1 Get Data Set By Windows - Classify) is with errors (yellow colour) but the overall discovery is in green.

Thus, not getting cluster information should not block you. Please check the credentials, as they have access only to classify but not identiy/explore the CI?

[venkataramac]

Hi @Mannapuram ,

Thanks for the reply,

The difference is in your case the error is "Invalid Namespace" and Discovery is not treating this as Failure.

But in my case:  

Error is Invalid Class and Discovery is not treating as error