Skip to main content

Adding properties to PowerShell Output

This morning on PowerShell.com, I helped with a question about adding data to an output.  Essentially, there were two data sources and the user needed the data to be presented in one object so they could pipe it to Export-CSV.  The Select-Object cmdlet has the ability to add data to an object.  Take a look at this code.

1

2

3

4

5

6

7

8

9

10

11

12

13

 

$Servers= "Server1", "Server2"

$MasterArray = @()

ForEach($Server in $Servers)

{

 

    If(Test-Connection -quiet -computer $server)

    {

    $Result=Get-Counter -Counter "\\$server\Processor Information(_Total)\% Processor Time"

    $Result | Select-Object -Property *,

        @{N="Online";E={$True}}

    }

 

}

 

This is the complete code.  What was missing was lines 9 and 10.  Lines 9 and 10 are actually the same line.

On line 9, I am using the comma to act as a line continuation character.  Line 10 is where the magic starts.  On line 9, we are piping the object stored in $Results to the Select-Object statement.  We have chosen to retain all of the properties of the object.  The “,” tells PowerShell that I want more.

Line 10 is a hash table.  The value of “N” is going to be the Name of the property.  The value of “E” is what to assign as the value of the property “Online”.  Yes, you need the extra {} as part of the expression.  In other words, let’s say that $Result has two properties; Name and Counter.  In this case, the question was how to add the result of  Test-Connection to the object.  Inside of the IF block is where we add the hash table to the Select-Object statement. The Hash table adds the third property of Online to the object.  If the connection was not made, we would not be getting any information.

For better design, consider using error handling and creating the object with both the computer name and setting the Online value to False.  That way you have a record of which clients were contacted and which ones were not.

Comments

Popular posts from this blog

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe

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.