Skip to main content

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

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



Labels:

Comments

Post a Comment

Popular posts from this blog

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

By
This was an interesting observation from one of my Windows Server 2012 classes.  While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted.  When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places.  First off in the Active Directory Administrative Center.  This is what caused the initial confusion.  Take a look.  This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3.  Test3 is a valid, functioning user account.  Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...
Post a Comment
Read more

Sticky Key problem between Windows Server 2012 and LogMeIn

By
This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .
6 comments
Read more

Backup and Restore AD LDS with DSDBUTIL.exe

By
Active Directory Lightweight Directory Services allow you to create a directory service that allows applications to have access to user accounts, groups, and authentication similar to Active Directory Domain Services.  The big advantage here is that the schema of the directory service will not be bound by the rules of an Active Directory database.  Exchange 2007/2010, for example, use an instance of AD LDS on the Edge Transport Server to provide for user authentication from the internet.  Because your Active Directory database is not exposed to the internet, this is more secure. Applications will handle most of the dirty work should they require AD LDS.  You may want to make sure the database is being backed up and also have a restore plan in place.  Should the database become corrupt, the application that uses that database will fail.  This document will walk you through backing up and restoring an instance of AD LDS using the dsdbutil.exe command. Fi...
6 comments
Read more