How to Provide Double Quotes in a String

PowerShell is full of little mysteries to uncover. Here is one using the PowerShell Escape Character.

The problem that we are addressing is that a string needed to be created in code that contains a path that had a space in it that was provided by a variable. In order to provide the value of a variable to a string, we have a few options.

$uninst = "MsiExec.exe /X{26A24AE4-039D-4CA4-87B4-2F32180101F0}"

$Path = "/c `"$uninst`" /quiet /norestart"

$Path

This example uses the PowerShell escape character. We place the back tick in front of both of the double quotes surrounding $uninst. Here is the result.

/c "MsiExec.exe /X{26A24AE4-039D-4CA4-87B4-2F32180101F0}" /quiet /norestart

You can clearly see the double quotes are now inside the string. Here is what it looked like without the escape characters.

You can see PowerShell considers this an error.

Here is another example using a combination of the string Join “+” operator and the single quotes.

$uninst = "MsiExec.exe /X{26A24AE4-039D-4CA4-87B4-2F32180101F0}"

$Path = '/c "'+"$uninst"+'"/quiet /norestart'

$Path

/c "MsiExec.exe /X{26A24AE4-039D-4CA4-87B4-2F32180101F0}"/quiet /norestart

We are only using the double quotes to extract the value of $uninst. The other double quotes are inside of the single quotes. This treats them as the literal character of a double quote. We actually created 3 different strings and joined them together into one string using the “+” operator.

Comments

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix. This customization deals with Group Policy and PowerShell. For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material. I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO. This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy. One organization in the crowd had over 5,000 Group Policies. In an environment like that, the comment section can be priceless. I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2 # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2 #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers. The first command creates a collection with 2 duplicates of both 1 and 2. The second command creates another collection with the duplicates filtered out. The Compare-Object cmdlet will first find items that are diffe

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory. To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

Jason Yoder, MCT

Search This Blog