Skip to main content

Getting Rid of the Back Ticks

By

For those of you who have been utilizing my blog posts over these past several years, you may have noticed that I generally rely on the back tick to prevent my code from horizontally extending outside of the screen and to provide order to cmdlets with a lot of parameters.  The back tick consists of only 3 pixels.  Here it is: `  Did you miss it?  So, if the back tick is bad, how to do you prevent horizontal scrolling? 

The back tick does allow for some very orderly presentation of code.  Take a look at this simple example:

$Obj = New-Object -TypeName PSObject

$Obj | Add-Member -MemberType NoteProperty `

        -Name "Prop1" `

        -Value "PowerShell Rocks"

 

 

This code simply makes an object with one property.  Notice that in using the Add-Member cmdlet, I separated three different parameters using the back tick.  The problem, it may not be easy to see.  Here is an alternative using splatting.

$Prop1 = @{

    MemberType = "NoteProperty"

    Name="Prop1"

    Value = "PowerShell Rocks"}

 

$Obj = New-Object -TypeName PSObject

$Obj | Add-Member @Prop1

 

 

In this example, we created a hash table utilizing the name of the parameter as the key, and what we want to set it to as the value.  This method still allows for an orderly presentation of the cmdlets parameters.  It also has another advantage.  If you need to create another object with the same property, you can just reuse the splat. Here is some code to create a new Fine Grain Password Policy written without using back ticks.

New-ADFineGrainedPasswordPolicy -Name "Group1PSO" -Precedence 10 -ComplexityEnabled $True -Description "PSO for Group 1" -DisplayName "Group1PSO" -LockoutDuration "0.12:00:00" -LockoutObservationWindow "0.00:15:00" -LockoutThreshold 3 -MaxPasswordAge "10.00:00:00" -MinPasswordAge "1.00:00:00" -MinPasswordLength 8 -PasswordHistoryCount 10 -ReversibleEncryptionEnabled $False

 

This is not very easy to read.  It is essentially noise.  And now with the back ticks:

 

New-ADFineGrainedPasswordPolicy -Name "Group1PSO" `

 -Precedence 10 `

 -ComplexityEnabled $True `

 -Description "PSO for Group 1" `

 -DisplayName "Group1PSO" `

 -LockoutDuration "0.12:00:00" `

 -LockoutObservationWindow "0.00:15:00" `

 -LockoutThreshold 3 `

 -MaxPasswordAge "10.00:00:00" `

 -MinPasswordAge "1.00:00:00" `

 -MinPasswordLength 8 `

 -PasswordHistoryCount 10 `

 -ReversibleEncryptionEnabled $False

 

Much better and very organized.  It is easy to both see which parameters are being used and their values. And now utilizing splatting:

  $Params = @{

    Name = "Group1PSO"

    Precedence = 10

    ComplexityEnabled = $True

    Description = "PSO for Group 1"

    DisplayName = "Group1PSO"

    LockoutDuration = "0.12:00:00"

    LockoutObservationWindow = "0.00:15:00"

    LockoutThreshold = 3

    MaxPasswordAge = "10.00:00:00"

    MinPasswordAge = "1.00:00:00"

    MinPasswordLength = 8

    PasswordHistoryCount = 10

    ReversibleEncryptionEnabled = $False}

 

 New-ADFineGrainedPasswordPolicy @Params

 

Yes, there is a little bit more code.  The advantage is that you do not have to worry about if the recipient of this code will notice a back tick or not.  In my past PowerShell V2 classes, I had to spend some time with the ISE magnification on high to demonstrate the back tick being used as the escape character.  This included line continuation.  Moving forward with the V3 classes, I will be focusing on splatting as my means of line continuation when parameters are involved.

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

Backup and Restore AD LDS with DSDBUTIL.exe

By
Active Directory Lightweight Directory Services allow you to create a directory service that allows applications to have access to user accounts, groups, and authentication similar to Active Directory Domain Services.  The big advantage here is that the schema of the directory service will not be bound by the rules of an Active Directory database.  Exchange 2007/2010, for example, use an instance of AD LDS on the Edge Transport Server to provide for user authentication from the internet.  Because your Active Directory database is not exposed to the internet, this is more secure. Applications will handle most of the dirty work should they require AD LDS.  You may want to make sure the database is being backed up and also have a restore plan in place.  Should the database become corrupt, the application that uses that database will fail.  This document will walk you through backing up and restoring an instance of AD LDS using the dsdbutil.exe command. Fi...
6 comments
Read more