{"id":12571,"date":"2011-09-27T00:01:00","date_gmt":"2011-09-27T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2011\/09\/27\/create-a-custom-object-from-wmi-by-using-powershell\/"},"modified":"2011-09-27T00:01:00","modified_gmt":"2011-09-27T00:01:00","slug":"create-a-custom-object-from-wmi-by-using-powershell","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/create-a-custom-object-from-wmi-by-using-powershell\/","title":{"rendered":"Create a Custom Object from WMI by Using PowerShell"},"content":{"rendered":"

Summary<\/strong>: Create a custom object from WMI to display processor and operating system information using Windows PowerShell.<\/p>\n

 <\/p>\n

\"Hey,Hey, Scripting Guy! Your script yesterday<\/a> was pretty cool. However, in addition to obtaining information about the processor, I also need to know operating system is 32-bit or 64-bit, the version of Windows that is installed, and the service pack that is installed. I hate to be picky, but this is the information I need in order to plan for our upgrade project.<\/p>\n

—BB<\/p>\n

 <\/p>\n

\"Hey,Hello BB,<\/p>\n

Microsoft Scripting Guy Ed Wilson here. First, I need to apologize to the Scripting Wife. Yesterday was her birthday, and I did not mention it in the Hey, Scripting Guy! Blog. Sorry!<\/p>\n

Beyond the disappointed Scripting Wife, BB, I am glad you enjoyed yesterday’s article. It is one of those things that sort of gets out of control. I begin working on a script and keep adding to it. So I will simply continue adding to it for today.<\/p>\n

First, make sure you have the script from yesterday’s Hey Scripting Guy! Article. The script, as it stood at the end of yesterday, is shown here:<\/p>\n

Import-Module ActiveDirectory<\/p>\n

$pingConfig = @{<\/p>\n

    “count” = 1<\/p>\n

    “bufferSize” = 15<\/p>\n

    “delay” = 1<\/p>\n

    “EA” = 0 }<\/p>\n

$computer = $cn = $null<\/p>\n

$cred = Get-Credential<\/p>\n

 Get-ADComputer -filter * -Credential $cred |<\/p>\n

 ForEach-Object {<\/p>\n

                 if(Test-Connection -ComputerName $_.dnshostname @pingconfig)<\/p>\n

                   { $computer += $_.dnshostname + “`r`n”} }<\/p>\n

$computer = $computer -split “`r`n”<\/p>\n

$property = “systemname”,”maxclockspeed”,”addressWidth”,<\/p>\n

            “numberOfCores”, “NumberOfLogicalProcessors”<\/p>\n

foreach($cn in $computer)<\/p>\n

{<\/p>\n

 if($cn -match $env:COMPUTERNAME)<\/p>\n

   {<\/p>\n

   Get-WmiObject -class win32_processor -Property  $property |<\/p>\n

   Select-Object -Property $property }<\/p>\n

 elseif($cn.Length -gt 0)<\/p>\n

  {<\/p>\n

   Get-WmiObject -class win32_processor -Property $property -cn $cn -cred $cred |<\/p>\n

   Select-Object -Property $property } }<\/p>\n

 <\/p>\n

Now, let’s see if I can find the additional information you need for your upgrade project. Actually, it is pretty simple because everything you need is in the Win32_OperatingSystem<\/b> WMI class. The Win32_OperatingSystem WMI class is documented on MSDN<\/a>, but the properties needed for today’s script are rather straightforward and do not need extensive documentation. A quick check of the Win32_Operatingsystem<\/b> WMI class reveals everything I need. The command I use to perform this check is shown here (gwmi<\/b> is an alias for Get-WmiObject<\/b> and fl<\/b> is alias for Format-List<\/b>):<\/p>\n

gwmi win32_operatingsystem | fl *<\/p>\n

The command and associated output are shown in the following figure.<\/p>\n

\"Image<\/a><\/p>\n

The revised script is named GetADComputersAndWMiProcessorAndOSInfo.ps1.<\/p>\n

GetADComputersAndWMiProcessorAndOSInfo<\/p>\n

Import-Module ActiveDirectory<\/p>\n

$pingConfig = @{<\/p>\n

    “count” = 1<\/p>\n

    “bufferSize” = 15<\/p>\n

    “delay” = 1<\/p>\n

    “EA” = 0 }<\/p>\n

$computer = $cn = $null<\/p>\n

$cred = Get-Credential<\/p>\n

 Get-ADComputer -filter * -Credential $cred |<\/p>\n

 ForEach-Object {<\/p>\n

                 if(Test-Connection -ComputerName $_.dnshostname @pingconfig)<\/p>\n

                   { $computer += $_.dnshostname + “`r`n”} }<\/p>\n

$computer = $computer -split “`r`n”<\/p>\n

$property = “systemname”,”maxclockspeed”,”addressWidth”,<\/p>\n

            “numberOfCores”, “NumberOfLogicalProcessors”<\/p>\n

$osProperty = “Caption”, “OSArchitecture”,”ServicePackMajorVersion”<\/p>\n

foreach($cn in $computer)<\/p>\n

{<\/p>\n

 if($cn -match $env:COMPUTERNAME)<\/p>\n

   {<\/p>\n

   $obj = Get-WmiObject -class win32_processor -Property  $property |<\/p>\n

          Select-Object -Property $property<\/p>\n

   $os =  Get-WmiObject -class win32_OperatingSystem -Property  $osproperty |<\/p>\n

          Select-Object -Property $osproperty<\/p>\n

   } #end if     <\/p>\n

 elseif($cn.Length -gt 0)<\/p>\n

  {<\/p>\n

   $obj = Get-WmiObject -class win32_processor -Property $property -cn $cn -cred $cred |<\/p>\n

   Select-Object -Property $property<\/p>\n

   $os = Get-WmiObject -class win32_OperatingSystem -Property $osproperty -cn $cn -cred $cred |<\/p>\n

   Select-Object -Property $osproperty<\/p>\n

  } #end elseif<\/p>\n

  New-Object psobject -Property @{<\/p>\n

   “name” = $obj.systemname<\/p>\n

   “speed” = $obj.maxclockspeed<\/p>\n

   “addressWidth” = $obj.addressWidth<\/p>\n

   “numberCores” = $obj.numberOfCores<\/p>\n

   “numberLogicalProcessors” = $obj.NumberOfLogicalProcessors<\/p>\n

   “OSname” = $os.Caption<\/p>\n

   “OSArchitecture” = $os.OSArchitecture<\/p>\n

   “ServicePack” = $os.ServicePackMajorVersion<\/p>\n

   }<\/p>\n

  #$os<\/p>\n

 } #END FOREACH<\/p>\n

When the script runs, the first thing that happens is a credential dialog box displays. This is because I request credentials for connection to remote systems. The credentials are not used to connect to the local computer. The credential dialog box is shown in the following figure.<\/p>\n

\"Image<\/a><\/p>\n

I added an array of properties to store the operating system information:<\/p>\n

$osProperty = “Caption”, “OSArchitecture”,”ServicePackMajorVersion”<\/p>\n

This change is shown in the following figure.<\/p>\n

\"Image<\/a><\/p>\n

In addition, I changed the portion of the script inside the Foreach<\/b> loop so that I am storing the Processor<\/b> object instead of directly emitting. I also added a WMI query to retrieve the operating system information. The revised section is shown here:<\/p>\n

foreach($cn in $computer)<\/p>\n

{<\/p>\n

 if($cn -match $env:COMPUTERNAME)<\/p>\n

   {<\/p>\n

   $obj = Get-WmiObject -class win32_processor -Property  $property |<\/p>\n

          Select-Object -Property $property<\/p>\n

   $os =  Get-WmiObject -class win32_OperatingSystem -Property  $osproperty |<\/p>\n

          Select-Object -Property $osproperty<\/p>\n

   } #end if     <\/p>\n

 elseif($cn.Length -gt 0)<\/p>\n

  {<\/p>\n

   $obj = Get-WmiObject -class win32_processor -Property $property -cn $cn -cred $cred |<\/p>\n

   Select-Object -Property $property<\/p>\n

   $os = Get-WmiObject -class win32_OperatingSystem -Property $osproperty -cn $cn -cred $cred |<\/p>\n

   Select-Object -Property $osproperty<\/p>\n

  } #end elseif<\/p>\n

This portion of the revised code is shown in the following figure.<\/p>\n

\"Image<\/a><\/p>\n

To make it easier to work with the output, I decided to return a custom object. This object contains information from both WMI classes. In addition, I changed some of the column headings to make it easier to read. This section of the script that creates the new object is shown here:<\/p>\n

New-Object psobject -Property @{<\/p>\n

   “name” = $obj.systemname<\/p>\n

   “speed” = $obj.maxclockspeed<\/p>\n

   “addressWidth” = $obj.addressWidth<\/p>\n

   “numberCores” = $obj.numberOfCores<\/p>\n

   “numberLogicalProcessors” = $obj.NumberOfLogicalProcessors<\/p>\n

   “OSname” = $os.Caption<\/p>\n

   “OSArchitecture” = $os.OSArchitecture<\/p>\n

   “ServicePack” = $os.ServicePackMajorVersion<\/p>\n

   } #end new object<\/p>\n

This portion of the new code is shown in the following figure.<\/p>\n

\"Image<\/a><\/p>\n

When the script runs, the following output is displayed.<\/p>\n

\"Image<\/a><\/p>\n

 <\/p>\n

BB, that is all there is to using Windows PowerShell to query for both processor and operating system information. <\/p>\n

I invite you to follow me on Twitter<\/a> and Facebook<\/a>. If you have any questions, send email to me at scripter@microsoft.com<\/a>, or post your questions on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then, peace.<\/p>\n

Ed Wilson, Microsoft Scripting Guy<\/b><\/p>\n

 <\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Summary: Create a custom object from WMI to display processor and operating system information using Windows PowerShell.   Hey, Scripting Guy! Your script yesterday was pretty cool. However, in addition to obtaining information about the processor, I also need to know operating system is 32-bit or 64-bit, the version of Windows that is installed, and […]<\/p>\n","protected":false},"author":596,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[237,16,31,287,2,3,4,203,288,45,6],"class_list":["post-12571","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-basic-computer-information","tag-desktop-management","tag-operating-system","tag-receiving-input","tag-running","tag-scripting-guy","tag-scripting-techniques","tag-service-packs-and-hotfixes","tag-version-information","tag-windows-powershell","tag-wmi"],"acf":[],"blog_post_summary":"

Summary: Create a custom object from WMI to display processor and operating system information using Windows PowerShell.   Hey, Scripting Guy! Your script yesterday was pretty cool. However, in addition to obtaining information about the processor, I also need to know operating system is 32-bit or 64-bit, the version of Windows that is installed, and […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/12571","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/596"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=12571"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/12571\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=12571"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=12571"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=12571"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}