Skip to main content

New Syntax for Hash Tables with Select-Object

By
Wow!  I am actually getting around to blogging this year.  This has been an epic year in terms of how busy I have been.  Between speaking at both the PowerShell Conferences in Europe and Asia, but also expanding my client base in Asia and the Pacific islands, I have been busy.  Oh, let’s not forget adding Windows Server 2016 classes, Security+ and my work on the Azure platform. 

OK, yes I have been busy.  At some point, what I have been learning does get spilled over into my classes and this blog.

One of the sticky points with learning PowerShell has been the creation of calculated properties with Select-Object.  To do so you need to use a hash table, associative table, or dictionary.  What you call it depends on your background.   Just remember that most IT pros who take my PowerShell classes are not programmers and have never been trained as such.  Makes for an interesting week for me.  
Below is an example of how we have been teaching calculated properties.
Get-Process |
    Select-Object -Property Name,
        @{
            Name = 'VirtMemory'
            Expression = {$PSItem.VM}
        }

You could short hand it as such.

Get-Process |
    Select-Object -Property Name, @{N = 'VirtMemory'; E = {$PSItem.VM}}

Well, that hash table is the problem.  I have not found a way to eliminate it, but I have found a way to write it a different way.

$Hash1 = @{ 'Name' = 'VirtMemory'; Expression = {$PSItem.VM}}
Get-Process | Select-Object -Property Name, $Hash1

The idea is to break it up into multiple parts so the student can focus more on what is going on and less on the confusing syntax used with Select-Object. You can add additional calculated properties as shown below.

$Hash1 = @{ 'Name' = 'VirtMemory'; Expression = {$PSItem.VM}}
$Hash2 = @{ 'Name' = 'WorkMemory'; Expression = {$PSItem.WS}}
Get-Process | Select-Object -Property Name, $Hash1, $Hash2

This technique will not work for all.  If what you are using works for you, then continue to use your technique.  I will be introducing this syntax in my PowerShell class next week in Phoenix to gauge the class response to this technique as a step in their understanding of how to perform this very common task and understand it.
 


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

How to run GPResult on a remote client with PowerShell

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