How can I parse a string of text in PowerShell?

For you vbscripters out we had a built in function call split that allowed us to split text strings into an array. We have the same functionality as method in PowerShell.

First create a variable:

$Var1="“10,15,20,9,8,7”"

Now let's discover the methods that are available to this variable. Powershell is smart enough to know that this variable is a string.

$Var1 | Get-Member

Noticed that Split is a method. Let’s go ahead and execute this method.
• $Var1.Split(“,”).

The “,” tells PowersShell that our delimiter is going to be the comma. You can choose any character to be your delimiter.

You can also treat these as cells in an array.

• $Var2 = $Var1.Split(“,”)
• $Var2[1]

After you execute the second command, the contents of cell 1 in the array $Var2 will be displayed. In this case, it should be 15.

Comments

Anonymous said…

V2 also introduces the -split operator (get-help about_split,) and you can also go all the way with http://www.leeholmes.com/blog/parsetextObjectAWKWithAVengeance.aspx

Lee Holmes [MSFT]
Windows PowerShell Development
Microsoft Corporation

September 15, 2009 at 10:51 AM

Anonymous said…

1st Thank You!

I needed to count the number of comma's in a string:

$Var.Split(",").Count

May 19, 2015 at 7:25 AM

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?

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

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.

Sticky Key problem between Windows Server 2012 and LogMeIn

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 .

Jason Yoder, MCT

Search This Blog