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:

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

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:

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

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.

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

January 20, 2012 at 10:40 AM

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.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Jason Yoder, MCT

Search This Blog