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

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.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Error icon when creating a GPO Preference drive map

You may not have an error at all.  Take a look at the drive mapping below. The red triangle is what threw us off.  It is not an error.  It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle.  This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the mapped drive. If the