{"id":1603,"date":"2011-08-16T09:45:04","date_gmt":"2011-08-16T13:45:04","guid":{"rendered":"http:\/\/jdhitsolutions.com\/blog\/?p=1603"},"modified":"2011-08-12T14:50:21","modified_gmt":"2011-08-12T18:50:21","slug":"select-object-properties-with-values","status":"publish","type":"post","link":"https:\/\/jdhitsolutions.com\/blog\/scripting\/1603\/select-object-properties-with-values\/","title":{"rendered":"Select Object Properties with Values"},"content":{"rendered":"

Here's another concept I know I've written about in the past but that needed an update. A common technique I use when exploring and discovering objects is to pipe the object to Select-Object specifying all properties, get-service spooler | select *. There's nothing wrong with this approach but depending on the object I might get a lot of empty values. This is especially true with WMI objects or items from Active Directory like a user account. The other issue I have is that when using this technique with a WMI object, I also get the system properties like __PATH, which I'd often like to ignore. The solution I came up is a function called Select-PropertyValue. Pipe objects to the function and it will write a custom object to the pipeline only with properties that have a value.<\/p>\n

[cc lang=\"PowerShell\"]
\nFunction Select-PropertyValue {
\n[cmdletbinding()]<\/p>\n

Param(
\n[Parameter(Position=0,ValueFromPipeline=$True)]
\n[object]$InputObject,
\n[Switch]$NoSystem,
\n[Switch]$Inquire = $False
\n)<\/p>\n

Begin {
\n Write-Verbose \"Starting $($myinvocation.mycommand)\" <\/p>\n

#define a variable we will be using to keep StrictMode happy.
\n $properties=@()
\n} #begin<\/p>\n

Process {<\/p>\n

<#\n set debug preference to continue when using -Debug unless user\n has also used -Inquire. Otherwise, PowerShell will prompt\n for each command. Due to scoping issues I found the best solution\n was to set the debug preference for each object in the pipeline\n #><\/p>\n

if (($PSCmdlet.MyInvocation.BoundParameters.ContainsKey(\"debug\")) -AND (-NOT $Inquire)) {
\n $DebugPreference=\"Continue\"
\n }<\/p>\n

Write-Debug \"In process\"
\nWrite-Debug \"Checking for `$properties\"
\n<#\nbecause this only takes pipelined objects, we only need to get the properties from \nGet-Member once. When the second object is processed, this IF block will get skipped.\nThe assumption that all pipelined objects are of the same type.\n#><\/p>\n

if (-Not $properties) {
\n Write-Verbose \"Creating property list\"
\n Write-Debug \"Creating property list for pipelined object\"<\/p>\n

#get properties for the pipelined object sorted by property name
\n $properties=$_ | Get-Member -membertype Properties | sort Name
\n $typename=($_ |Get-Member)[0].TypeName
\n Write-Debug \"Typename =$typename\"<\/p>\n

#filter out WMI System properties if -NoSystem
\n if ($NoSystem) {
\n Write-Verbose \"Filtering out WMI System properties\"
\n Write-Debug \"Filtering out WMI System properties.\"
\n $properties=$properties | where {$_.name -notlike \"__*\"}
\n }<\/p>\n

Write-Verbose \"Found $($properties.count) properties\"
\n Write-Debug \"Found $($properties.count) properties\"
\n}<\/p>\n

#create an empty custom object
\n Write-Debug \"Creating empty object\"
\n $obj=New-Object PSObject<\/p>\n

#enumerate the list of properties
\nWrite-Verbose \"Checking properties for values\"
\nforeach ($property in $properties) {
\n Write-Debug \"Checking $($property.name)\"
\n #if object has a value for the current property
\n if ($_.($property.name)) {
\n Write-Debug \"found value for: $($_.($property.name))\"<\/p>\n

#assign properties to the custom object
\n Write-Debug \"Adding property and value to custom object\"
\n $obj | Add-Member -MemberType Noteproperty -name $property.Name -value ($_.($property.name))<\/p>\n

} #end If
\n} #end ForEach<\/p>\n

#Add the typename to the object
\nWrite-Debug \"Adding typename to custom object\"
\n$obj | Add-Member -MemberType Noteproperty -Name \"Type\" -Value $typename<\/p>\n

#write the custom object to the pipeline
\nWrite-Debug \"Writing custom object to the pipeline\"
\nWrite $obj
\n} #end process<\/p>\n

End {
\n Write-Verbose \"Ending $($myinvocation.mycommand)\"
\n }<\/p>\n

} #end function
\n[\/cc]<\/p>\n

The function is intended to be used in a pipelined expression and assumes that all the objects are of the same type. The essence of the function is to run each object through Get-Member and keep a list of property names.<\/p>\n

[cc lang=\"PowerShell\"]
\nif (-Not $properties) {
\n Write-Verbose \"Creating property list\"
\n Write-Debug \"Creating property list for pipelined object\"
\n $properties=$_ | Get-Member -membertype Properties | sort Name
\n[\/cc]<\/p>\n

Because this happens in the process script block, which runs once for every piped in object, this line only runs if $properties doesn't already exist. If the user includes the -NoSystem parameter, then any property that starts with __ is removed.<\/p>\n

[cc lang=\"PowerShell\"]
\nif ($NoSystem) {
\n Write-Verbose \"Filtering out WMI System properties\"
\n Write-Debug \"Filtering out WMI System properties.\"
\n $properties=$properties | where {$_.name -notlike \"__*\"}
\n }
\n[\/cc]<\/p>\n

Armed with the array of property names, the pipelined object is checked for each property name. <\/p>\n

[cc lang=\"PowerShell\"]
\nforeach ($property in $properties) {
\n Write-Debug \"Checking $($property.name)\"
\n #if object has a value for the current property
\n if ($_.($property.name)) {
\n Write-Debug \"found value for: $($_.($property.name))\"
\n[\/cc]<\/p>\n

If a value is found<\/p>\n

[cc lang=\"PowerShell\"]
\nif ($_.($property.name))
\n[\/cc]<\/p>\n

Then the property and value are added to the blank custom object which is created for each piped object.<\/p>\n

[cc lang=\"PowerShell\"]
\n$obj | Add-Member -MemberType Noteproperty -name $property.Name -value ($_.($property.name))
\n[\/cc]<\/p>\n

I include the object type name and write the custom object to the pipeline.<\/p>\n

[cc lang=\"PowerShell\"]
\n#Add the typename to the object
\nWrite-Debug \"Adding typename to custom object\"
\n$obj | Add-Member -MemberType Noteproperty -Name \"Type\" -Value $typename<\/p>\n

#write the custom object to the pipeline
\nWrite-Debug \"Writing custom object to the pipeline\"
\nWrite $obj
\n[\/cc]<\/p>\n

Here's the end result.<\/p>\n

[cc lang=\"DOS\"]
\nBiosCharacteristics : {4, 7, 8, 9...}
\nBIOSVersion : {TOSQCI - 6040000, Ver 1.00PARTTBL}
\nCaption : Ver 1.00PARTTBL
\nDescription : Ver 1.00PARTTBL
\nManufacturer : TOSHIBA
\nName : Ver 1.00PARTTBL
\nPrimaryBIOS : True
\nReleaseDate : 20101210000000.000000+000
\nSerialNumber : Z9131790W
\nSMBIOSBIOSVersion : V2.90
\nSMBIOSMajorVersion : 2
\nSMBIOSMinorVersion : 6
\nSMBIOSPresent : True
\nSoftwareElementID : Ver 1.00PARTTBL
\nSoftwareElementState : 3
\nStatus : OK
\nVersion : TOSQCI - 6040000
\nType : System.Management.ManagementObject#root\\cimv2\\Win32_BIOS
\n[\/cc]<\/p>\n

You probably also noticed the Write-Verbose and Write-Debug lines in the script. Continuing the discussion I started in my post on Write-Verbose vs Write-Debug<\/a>, I'm including the suggestion on controlling the debug preference. By default if you the function with -debug you'll get all the debug messages. But if you also use -Inquire, then you'll get prompted for each command which is the normal process when using -Debug. I wanted to see how this would work in one of my own scripts.<\/p>\n

As always, I hope you'll let me know how this works out for you. Download Select-PropertyValue<\/a>. The full script includes comment-based help as well as an optional alias. Uncomment the last line of the script if you want to use it or define your own.<\/p>\n","protected":false},"excerpt":{"rendered":"

Here’s another concept I know I’ve written about in the past but that needed an update. A common technique I use when exploring and discovering objects is to pipe the object to Select-Object specifying all properties, get-service spooler | select *. There’s nothing wrong with this approach but depending on the object I might get…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[75,8],"tags":[32,317,144,534,540,302],"class_list":["post-1603","post","type-post","status-publish","format-standard","hentry","category-powershell-v2-0","category-scripting","tag-functions","tag-get-member","tag-objects","tag-powershell","tag-scripting","tag-select-object"],"yoast_head":"\nSelect Object Properties with Values • The Lonely Administrator<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/jdhitsolutions.com\/blog\/scripting\/1603\/select-object-properties-with-values\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Select Object Properties with Values • The Lonely Administrator\" \/>\n<meta property=\"og:description\" content=\"Here's another concept I know I've written about in the past but that needed an update. A common technique I use when exploring and discovering objects is to pipe the object to Select-Object specifying all properties, get-service spooler | select *. There's nothing wrong with this approach but depending on the object I might get...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/jdhitsolutions.com\/blog\/scripting\/1603\/select-object-properties-with-values\/\" \/>\n<meta property=\"og:site_name\" content=\"The Lonely Administrator\" \/>\n<meta property=\"article:published_time\" content=\"2011-08-16T13:45:04+00:00\" \/>\n<meta name=\"author\" content=\"Jeffery Hicks\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@JeffHicks\" \/>\n<meta name=\"twitter:site\" content=\"@JeffHicks\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Jeffery Hicks\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/1603\\\/select-object-properties-with-values\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/1603\\\/select-object-properties-with-values\\\/\"},\"author\":{\"name\":\"Jeffery Hicks\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\"},\"headline\":\"Select Object Properties with Values\",\"datePublished\":\"2011-08-16T13:45:04+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/1603\\\/select-object-properties-with-values\\\/\"},\"wordCount\":853,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\"},\"keywords\":[\"functions\",\"get-member\",\"objects\",\"PowerShell\",\"Scripting\",\"Select-Object\"],\"articleSection\":[\"PowerShell v2.0\",\"Scripting\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/1603\\\/select-object-properties-with-values\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/1603\\\/select-object-properties-with-values\\\/\",\"url\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/1603\\\/select-object-properties-with-values\\\/\",\"name\":\"Select Object Properties with Values • The Lonely Administrator\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#website\"},\"datePublished\":\"2011-08-16T13:45:04+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/1603\\\/select-object-properties-with-values\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/1603\\\/select-object-properties-with-values\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/scripting\\\/1603\\\/select-object-properties-with-values\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"PowerShell v2.0\",\"item\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/category\\\/powershell-v2-0\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Select Object Properties with Values\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/\",\"name\":\"The Lonely Administrator\",\"description\":\"Practical Advice for the Automating IT Pro\",\"publisher\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\",\"name\":\"Jeffery Hicks\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\",\"caption\":\"Jeffery Hicks\"},\"logo\":{\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Select Object Properties with Values • The Lonely Administrator","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/jdhitsolutions.com\/blog\/scripting\/1603\/select-object-properties-with-values\/","og_locale":"en_US","og_type":"article","og_title":"Select Object Properties with Values • The Lonely Administrator","og_description":"Here's another concept I know I've written about in the past but that needed an update. A common technique I use when exploring and discovering objects is to pipe the object to Select-Object specifying all properties, get-service spooler | select *. There's nothing wrong with this approach but depending on the object I might get...","og_url":"https:\/\/jdhitsolutions.com\/blog\/scripting\/1603\/select-object-properties-with-values\/","og_site_name":"The Lonely Administrator","article_published_time":"2011-08-16T13:45:04+00:00","author":"Jeffery Hicks","twitter_card":"summary_large_image","twitter_creator":"@JeffHicks","twitter_site":"@JeffHicks","twitter_misc":{"Written by":"Jeffery Hicks","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/1603\/select-object-properties-with-values\/#article","isPartOf":{"@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/1603\/select-object-properties-with-values\/"},"author":{"name":"Jeffery Hicks","@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9"},"headline":"Select Object Properties with Values","datePublished":"2011-08-16T13:45:04+00:00","mainEntityOfPage":{"@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/1603\/select-object-properties-with-values\/"},"wordCount":853,"commentCount":0,"publisher":{"@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9"},"keywords":["functions","get-member","objects","PowerShell","Scripting","Select-Object"],"articleSection":["PowerShell v2.0","Scripting"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/jdhitsolutions.com\/blog\/scripting\/1603\/select-object-properties-with-values\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/1603\/select-object-properties-with-values\/","url":"https:\/\/jdhitsolutions.com\/blog\/scripting\/1603\/select-object-properties-with-values\/","name":"Select Object Properties with Values • The Lonely Administrator","isPartOf":{"@id":"https:\/\/jdhitsolutions.com\/blog\/#website"},"datePublished":"2011-08-16T13:45:04+00:00","breadcrumb":{"@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/1603\/select-object-properties-with-values\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/jdhitsolutions.com\/blog\/scripting\/1603\/select-object-properties-with-values\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/jdhitsolutions.com\/blog\/scripting\/1603\/select-object-properties-with-values\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"PowerShell v2.0","item":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell-v2-0\/"},{"@type":"ListItem","position":2,"name":"Select Object Properties with Values"}]},{"@type":"WebSite","@id":"https:\/\/jdhitsolutions.com\/blog\/#website","url":"https:\/\/jdhitsolutions.com\/blog\/","name":"The Lonely Administrator","description":"Practical Advice for the Automating IT Pro","publisher":{"@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/jdhitsolutions.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":["Person","Organization"],"@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9","name":"Jeffery Hicks","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg","url":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg","caption":"Jeffery Hicks"},"logo":{"@id":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg"}}]}},"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"jetpack-related-posts":[{"id":639,"url":"https:\/\/jdhitsolutions.com\/blog\/scripting\/639\/join-object\/","url_meta":{"origin":1603,"position":0},"title":"Join Object","author":"Jeffery Hicks","date":"May 14, 2010","format":false,"excerpt":"Related to some of the WMI stuff I\u2019ve been working on lately is the idea of melding or joining objects. This comes about because I often see forum posts from administrators looking to collect information from different WMI classes but present it as a single object. One way you might\u2026","rel":"","context":"In "PowerShell v2.0"","block_context":{"text":"PowerShell v2.0","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell-v2-0\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":636,"url":"https:\/\/jdhitsolutions.com\/blog\/scripting\/636\/select-wmi\/","url_meta":{"origin":1603,"position":1},"title":"Select WMI","author":"Jeffery Hicks","date":"May 13, 2010","format":false,"excerpt":"I\u2019ve been helping out on some WMI and PowerShell issues in the forums at ScriptingAnswers.com. As I was working on a problem I ended up taking a slight detour to address an issue that has always bugged me. When I run a command like this: get-wmiobject -query \"Select Name,Description,Disabled from\u2026","rel":"","context":"In "PowerShell v2.0"","block_context":{"text":"PowerShell v2.0","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell-v2-0\/"},"img":{"alt_text":"selectwmi","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2010\/05\/selectwmi-300x89.png?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":2241,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/2241\/skipping-wmi-system-properties-in-powershell\/","url_meta":{"origin":1603,"position":2},"title":"Skipping WMI System Properties in PowerShell","author":"Jeffery Hicks","date":"April 25, 2012","format":false,"excerpt":"One of my favorite techniques when using WMI in PowerShell is to pipe an object to Select-Object and select all properties. Try this: get-wmiobject win32_bios | select * It works, but it also gets all of the system properties like __PATH which I rarely care about. I also get other\u2026","rel":"","context":"In "PowerShell"","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1542,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/1542\/get-properties-with-values\/","url_meta":{"origin":1603,"position":3},"title":"Get Properties with Values","author":"Jeffery Hicks","date":"July 4, 2011","format":false,"excerpt":"One of my nuisance issues when using WMI with Windows PowerShell, is that when looking at all properties I have to wade though many that have no value. I'd prefer to only view properties that have a populated value. Here's one way. Every WMI object has a property called Properties\u2026","rel":"","context":"In "PowerShell"","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":654,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/654\/new-wmi-object\/","url_meta":{"origin":1603,"position":4},"title":"New WMI Object","author":"Jeffery Hicks","date":"May 17, 2010","format":false,"excerpt":"I have one more variation on my recent theme of working with WMI objects. I wanted to come up with something flexible and re-usable where you could specify a WMI class and some properties and get a custom object with all the classes combined. My solution is a function called\u2026","rel":"","context":"In "PowerShell"","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":9074,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/9074\/the-value-of-objects\/","url_meta":{"origin":1603,"position":5},"title":"The Value of Objects","author":"Jeffery Hicks","date":"July 5, 2022","format":false,"excerpt":"This is a reprint of an article published earlier this year in my premium PowerShell newsletter, Behind the PowerShell Pipeline. This is a sample of what my subscribers get 6-8 times a month. I expect I will write several articles about PowerShell and its relationship with objects. I know that\u2026","rel":"","context":"In "PowerShell"","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2022\/07\/getting-drive-usage.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2022\/07\/getting-drive-usage.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2022\/07\/getting-drive-usage.png?resize=525%2C300&ssl=1 1.5x"},"classes":[]}],"_links":{"self":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/1603","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/comments?post=1603"}],"version-history":[{"count":0,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/1603\/revisions"}],"wp:attachment":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/media?parent=1603"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/categories?post=1603"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/tags?post=1603"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}