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

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 .

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

Where did a User’s Account Get Locked Out?

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

Jason Yoder, MCT

Search This Blog