Skip to main content

What is the Difference between $PSItem and $PSItem.Something?

Diversity is a wonderful thing.  So many different experiences leads us to look at the same thing in so many different ways.  I just had a simple, yet really good question in my PowerShell class.
“What is the difference between $PSItem and $PSItem.something?”

Good question.  We are currently studying the PowerShell Pipeline.  As a result, we are looking at $_ and $PSItem.  These two automatic variables represent the current object in the PowerShell pipeline.  If you look at the PowerShell help file About_Automatic_Variables you will see this:
    $_
       Same as $PSItem. Contains the current object in the pipeline object.
       You can use this variable in commands that perform an action on every
       object or on selected objects in a pipeline.

I tend to use $_ because it is shorter and most of my content needs to fit nicely in a book or in a blog post.  Let’s look at an object that we will place in the PowerShell pipeline.
PS Variable:\> Get-Date | Get-Member -MemberType Properties


   TypeName: System.DateTime

Name        MemberType     Definition                                                                 ----        ----------     ----------                                                               DisplayHint NoteProperty   DisplayHintType DisplayHint=DateTime                                     Date        Property       datetime Date {get;}                                                       Day         Property       int Day {get;}                                                           DayOfWeek   Property       System.DayOfWeek DayOfWeek {get;}                                         DayOfYear   Property       int DayOfYear {get;}                                                     Hour        Property       int Hour {get;}                                                           Kind        Property       System.DateTimeKind Kind {get;}                                           Millisecond Property       int Millisecond {get;}                                                   Minute      Property       int Minute {get;}                                                         Month       Property       int Month {get;}                                                         Second      Property       int Second {get;}                                                         Ticks       Property       long Ticks {get;}                                                         TimeOfDay   Property       timespan TimeOfDay {get;}                                                 Year        Property       int Year {get;}                                                           DateTime    ScriptProperty System.Object DateTime {get=if ((& { Set-StrictMode -Version 1; $this.DisplayHint }) -ieq  "Date")...    

This object has several members.  This first example will show you the results of using just $PSItem
PS C:\> Get-Date | ForEach-Object { $PSItem }

Tuesday, July 12, 2016 1:15:22 PM

This second example will show you the result of using $PSItem.DayOfYear
PS C:\> Get-Date | ForEach-Object { $PSItem.DayOfYear }
194

This third example involves a method of the object.
PS Variable:\> Get-Date | ForEach-Object { $PSItem.AddDays(10) }

Friday, July 22, 2016 2:59:56 PM

See the difference?  When you reference $PSItem, you are referencing the entire object.  When you add the name of a property or the name of a method of the object to $PSItem, you are asking for the value of that property or for that method to execute.



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