Discovery issues for windows server

baba
Tera Expert

3 weeks ago

For a specific IP that belongs to Windows server i enabled the Servicenow discovery. But In the CMDB CI table It created 4 CI records are created with 4 different classes i,e. VMware Network Adapter, Website, Website, Vmware virtual Machines instance. But it is not created with Windows Server class. What could be the possible issue?

0 Helpfuls
  • 379 Views
2 REPLIES 2

k_lutz
Giga Sage

3 weeks ago

Hi @baba 

 

You will need to check the ECC queue for what may be occurring. It most likely relates to one of the following:

  • Missing or Invalid Windows Credentials
  • WMI/Port Connectivity Issues
  • Issue with the Windows Pattern
  • Issue(s) with Classification/Identification Rules

praveenkshanmu
Tera Contributor

3 weeks ago

Hi Baba,


Based on the CI classes you’ve shared, it looks like infrastructure discovery succeeded (VMware/vCenter), the IP is reachable, and application probes ran. However, Discovery was unable to access the Windows OS on the host. This is typically due to missing or failing Windows credentials, network or firewall restrictions, or OS classification being skipped. I recommend reviewing the Discovery logs for errors such as "No valid Windows credentials found" or "Skipping Windows classification."

 

Thank you,

Praveen