CPU Count / Core Count Discovery Issue

ameertalha
Kilo Explorer

Discovery of a Windows 2003 Enterprise server returned incorrect CPU Count (4) and did not return the CPU Core Count, even though I got the results shown below when I ran a Custom probe on the same server with the command :

Get-CimInstance -ClassName 'Win32_Processor' `

      | Select-Object -Property 'DeviceID', 'Name', 'NumberOfCores';

Screen Shot 2017-09-27 at 2.10.17 PM.png

I get the same result when i run a WMI command instead of the CIM command.

Why is Discovery populating the CI form with CPU Count 4 when the server actually contains 2 processors?

4 REPLIES 4

Dave Mau
ServiceNow Employee
ServiceNow Employee

Is this a VM or a physical server?


It's a virtual machine


tim_broberg
ServiceNow Employee
ServiceNow Employee

Check the ecc_queue input record for that probe.



Microsoft is creative with CPU counts at times.


Dave Ainsworth
ServiceNow Employee
ServiceNow Employee

Hi Ameer,



I have seen this before with discovery but it was found to be the following problem in Windows 2003:



https://support.microsoft.com/en-gb/help/932370/the-number-of-physical-hyperthreading-enabled-proces...



If this is the issue, there is a hotfix that needs to be installed on the Windows 2003 servers.



Regards,



Dave