CPU core count, CPU count, Disk space (GB),OS Domain is empty by discovery

Anshu Anand2
Kilo Contributor

Dear All,

 

In our new Orlando pattern based discovery , the windows 2019 servers specially and some other windows/linux servers

these fields are getting empty by discovery itself:-

  1. CPU core count
  2. CPU count
  3. Disk space (GB)
  4. OS Domain
  5. description

I have checked the input xml payload.there its also making empty on return.

what can go wrong? previously it was not,happened just after pattern based discovery migration in our new orlando.

 

1 ACCEPTED SOLUTION

chuckm
Giga Guru

For the Windows 2019 servers, is the server being discovered with the credential applied on the ServiceNow MID Server service? If so, there is an issue in Pattern-based discovery for Windows patterns where not all of the fields are populated.

A work around to resolve the fields not populating is to apply the same Windows Credential to both ServiceNow MID Server service and the ServiceNow WMI Collector service.

find_real_file.png

View solution in original post

13 REPLIES 13

rahulyamgar
Tera Guru

It would use the WMI to retrieve the data from the Windows Machine. Can you execute the same WMI command  (you could look for the respective output ECC Queue message)  and execute the same from the Orchestration through MID server and see if you get the something back. 

If it does not retrieve the data, you could reach out to Windows Admin for this.

Thanks,
Rahul

Its happening for all the windows servers now. in some all are empty and in some all 3 fields are empty just after pattern based discovery

the discovery payload shows empty returned.why its happening for all windows servers now regardless of 2019 in new pattern based discovery

chuckm
Giga Guru

For the Windows 2019 servers, is the server being discovered with the credential applied on the ServiceNow MID Server service? If so, there is an issue in Pattern-based discovery for Windows patterns where not all of the fields are populated.

A work around to resolve the fields not populating is to apply the same Windows Credential to both ServiceNow MID Server service and the ServiceNow WMI Collector service.

find_real_file.png

Its happening for all the windows servers now. in some all are empty and in some all 3 fields are empty just after pattern based discovery