Skip to main content

How to determine the number of physical processors on a client in PowerShell.

There seems to be a bit of a debate on the internet about this one.  I executed the following PowerShell command on 2 different computers:

Get-WMIObject Win32_ComputerSystem | FL *

 

I executed it on a laptop with 1 physical processor with 4 logical processors and received the following results:

 

image

 

I then executed it again on a desktop with 1 physical processor and 8 logical processors:

 

image

 

From my testing, the NumberOfProcessors property seems to provide the correct number of physical processors.

 

I got curios and ran that PowerShell code on a virtual machine with 1 assigned processor:

 

image

 

I also ran it on a virtual machine with 4 processors assigned to it:

 

image

 

OK, so how do you know if you are looking at a virtual machine or a physical machine?  A couple of properties higher in the list you will see Model.  If this was a virtual machine, it would say Virtual Machine.

 

image

Comments

Brandon Ryan said…
To get the number of physical CPU sockets, you must count how many objects are returned by "get-wmiobject win32_processor"

---

$myArray = @()
$myArray += get-wmiobject win32_processor
$myArray.Count

Popular posts from this blog

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.