CPU Count / Core Count Discovery Issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2017 11:23 AM
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';
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?
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2017 12:31 PM
Is this a VM or a physical server?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2017 12:34 PM
It's a virtual machine
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2017 01:57 PM
Check the ecc_queue input record for that probe.
Microsoft is creative with CPU counts at times.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2017 12:41 AM
Hi Ameer,
I have seen this before with discovery but it was found to be the following problem in Windows 2003:
If this is the issue, there is a hotfix that needs to be installed on the Windows 2003 servers.
Regards,
Dave