Skip to main content

Keeping a HASH Table in Order

By

When working with HASH tables, sometimes they display a little bit of a randomization problem.  Take a look:

1

2

3

4

5

6

7

8

$Hash = ConvertFrom-StringData @'

Apple=Red

Orange=Orange

Banana=Yellow

Pear=Green

Blueberry=Blue

Plum=Purple

'@

$Hash

 

Name                           Value                                                                               

----                           -----                                                                               

Pear                           Green                                                                               

Plum                           Purple                                                                              

Apple                          Red                                                                                 

Blueberry                      Blue                                                                                

Banana                         Yellow                                                                              

Orange                         Orange        

 

The output is not in the same order that I provided when I created the hash table.  This is where PowerShell’s Ordered Dictionary helps.  Take a look at the change in the code and the output.

1

2

3

4

5

6

$Hash = [Ordered]@{"Apple"="Red";

"Orange"="Orange";

"Banana"="Yellow";

"Pear"="Green";

"Blueberry"="Blue";

"Plum"="Purple"}

$Hash

 

Name                           Value                                                                               

----                           -----                                                                               

Apple                          Red                                                                                 

Orange                         Orange                                                                              

Banana                         Yellow                                                                              

Pear                           Green                                                                               

Blueberry                      Blue                                                                                

Plum                           Purple                

 

Just a few things to note.  You must placed the [Ordered] attribute in front of the @ or it will not work. You also need at least PowerShell V3.  Is there any advantage to using an ordered list? I would say this is just if you plan to display the hash table.  Otherwise, it works just the same as a none ordered hash table.

Labels:

Comments

Post a Comment

Popular posts from this blog

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

Where did a User’s Account Get Locked Out?

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