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

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.

Set up your Environment to utilize Invoke-GPUpdate

I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...

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...