$property = “systemname”,”maxclockspeed”,”addressWidth”, To avoid typing the properties twice (once for the Get-WmiObject cmdlet and once for the Select-Object cmdlet), I store the array of properties in the $property variable. The reason for this is to remove the system properties that are automatically included with the returned WMI object. I then pipe the returned object to the Select-Object cmdlet. To do this, I am going to choose which properties I need. What I do need is a good way to select only the information you require. But RS, for your requirements, I do not need that article. The Win32_Processor WMI class is documented on MSDN, and the article describes what all of the properties and coded values mean. In the following figure, I illustrate using the Get-WmiObject command and the default output from the command. The syntax of a command to query WMI and return CPU information is shown here:Īnd I can shorten that command by using the gwmi alias: In Windows PowerShell, a single line of code that uses the Get-WmiObject cmdlet to do the heavy lifting is all that is required. RS, to find out information about the CPU, I use the Windows Management Instrumentation (WMI) class Win32_Processor.

I really enjoy the opportunity to meet with people who are using Windows PowerShell to solve real world problems. I fly back to Charlotte, and then I head north to Canada for a couple of weeks. Later in the week, I will be talking to Windows PowerShell writers on campus at our Microsoft Office in Redmond. This week I am in Seattle, Washington, talking to customers about Windows PowerShell.

I feel like I should be able to use Windows PowerShell to do this, but I am not certain. I need the processor speed, number of cores, and number of logical processors. Specifically, I am tasked with obtaining CPU information. Hey, Scripting Guy! I need to perform an audit of computers on our network. Summary: Learn how to get the number of processor cores via WMI and Windows PowerShell.

Mac cpu info generations