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

[Anshu Anand2]

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.

[chuckm]

Are you using the MID Server Service Credential to discover these servers?

I suggest looking at the pattern log to determine if any of the steps are getting WMI authentication failures. In the example shown below, at first it appears that the Get OS address width was successful based on the green step Icon - but if you select the step - you will notice a WMI authentication failure and Access denied. This issue occurs for Pattern-based discovery when using the MID server service credential.

[Anshu_Anand_]

so what need to be done,

we use credential based discovery.

This is the error we get, before orlando upgrade it never happened.

could you please provide, what need to be done.

The ServiceNow WMI Collector service is used for ServiceMapping plugin to run WMI related queries.

This ServiceNow WMI Collector service is also not present under the mentioned file as per this KB article "https://hi.service-now.com/kb_view.do?sysparm_article=KB0758133"

the exe file servicenowwmi is also not there .

[chuckm]

anshu,

If the file wmi_collector.exe isn't found where your MID server files are located, you can re-download the ServiceNow MID server files and copy the wmi_collector.exe file from the newly downloaded files into where your MID server files are located.  Then open a command prompt and run the command per the KB article (with updated binPath where your MID server files are installed):

sc.exe create "ServiceNow WMI Collector" binPath= C:\servicenow\mid\agent\bin\sw_wmi\bin\wmi_collector.exe start= auto

Keep in mind that the location of wmi_collector.exe in the KB article may not be in the same path where you installed your MID server files. The first part of the path C:\servicenow\mid can be different depending where your team installed the MID server files. The remaining part of the path
agent\bin\sw_wmi\bin\ should be the same for all MID server file installations.

For example, in my AWS lab the MID server files are installed in C:\ServiceNow\AWS MID Server\agent\bin\sw_wmi\bin.

Before I run the command line, I update the path as follows (I added the quotes "" around the binPath because of the spaces in /AWS MID Server/):

sc.exe create "ServiceNow WMI Collector" binPath= "C:\ServiceNow\AWS MID Server\agent\bin\sw_wmi\bin\wmi_collector.exe" start= auto

Successfully running the command in the command prompt:

[Anshu_Anand_]

The main problem is that there is no "wmi_collector.exe" in mid server.

I downloaded it for 64 bit windows OS, but still there it is not 

madrid,orlando mid server i redownload the file by going through midserver->download,

but still the download "agent" file has no "wmi collecctor.exe". 

what need to be done now?

I read somewhere that its meant only for service mapping plugin and we dont use service mapping.

It's happening only after the orlando upgrade and pattern based discovery

[chuckm]

anshu,
I re-downloaded the MID server files from both New York and Madrid and the wmi_collector.exe was in both downloads.  The Madrid download has the Service Mapping plugin activated and the New York download does not.

Madrid

New York