Skip to main content

PowerShell Script to replace items in a text file

This script is a product of one my PowerShell classes in March 2011.  The problem was presented by a learner in the class.  His task was to take a large text file that needed to be parsed for question marks and have them replaced with spaces.  We expanded the script to make it more portable and useful in more situations.

As with all my PowerShell classes, I encourage the participants to have a project in mind when they arrive.  With a project in hand, the light bulb in the participants head turns on as they learn more and more skills to make their project a success.

<# ========================================================
Script: Replace.ps1
-----------------------------------------------------------
The input parameters are the input file, the new output
file.  We also needed to provide what we wanted to replace
with what.  Adding these extra parameters made the script
more portable.
-----------------------------------------------------------
#>
Param (
    $InFile = $(Read-Host 'Input File:
'),
    $OutFile = $(Read-Host 'Output File:
'),
    $ReplaceWhat = $(Read-Host 'Replace what:
'),
    $ReplaceWith = $(Read-Host 'Replace With:
')
    )
<#
After testing reviled that the question mark needed
an escape character, we added this switch statement
for some of the special characters used in Regular
Expressions.
#>
Switch ($ReplaceWhat){
    "^" {$ReplaceWhat = "\$ReplaceWhat"; Break
}
    "$" {$ReplaceWhat = "\$ReplaceWhat"; Break
}
    "*" {$ReplaceWhat = "\$ReplaceWhat"; Break
}
    "?" {$ReplaceWhat = "\$ReplaceWhat"; Break
}
    "\" {$ReplaceWhat = "\$ReplaceWhat"; Break
}
    "." {$ReplaceWhat = "\$ReplaceWhat"; Break
}
}
<#
The code below first grabs the content of the input file.
It then pipes that content to a ForEach loop that issues
a replace command between the contents of the $ReplaceWhat
with the $ReplaceWith variables.
#>

   
(Get-Content $InFile
) |
    ForEach {$_ -replace $ReplaceWhat, $ReplaceWith
} |
   Add-Content $OutFile

   
Write-Host
"Script: Replace.ps1 - Completed"

Comments

Popular posts from this blog

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 .

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

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.