Skip to main content

PowerShell Scripting: Removing Multiple Directories

Update 20150916
So the pic I used to display the CSV sample went missing. So the latest update just includes a text version of what was displayed. Thanks!

Original Post
I'm still fairly new to utilizing PowerShell to automate tasks and get big tasks done. But every time I use it, the tool makes my life a whole lot easier. Recently I was tasked with deleting over 500 directories. Thankfully someone else had the task of identifying the directories that were slated to be deleted, I just had to complete the process of removing them. Thanks to a little article from the Scripting Guy! Blog (found HERE) I had some direction to start in.

What I ended up doing is creating a single column CSV file that contains the path to the directories to be deleted. This path includes drive letter, and the overall path to the folder. It should look similar to this:
delete
C:\Path\to\folder
C:\Path\to\folder2
D:\Path\to\folder
D:\Path\to\folder2

I named the file "delete.csv" and placed it into my scripting folder on the C drive. Now with this set up and in place we can move onto using PowerShell. We will be using a combination of commands in a one-liner that will not only delete the files but auto-confirm the deletion. I'll put the command next and attempt to break it down as far as my knowledge of PowerShell goes...

Import-CSV .\delete.csv | Foreach-Object { Remove-Item -LiteralPath $_.delete -Force -Recurse -WhatIf }

The first part "Import-CSV" obviously tells PowerShell to look at the CSV we created with the necessary directories to be deleted. The "Foreach-Object" will loop through the CSV to delete all items in it. The "Remove-Item" part tells PowerShell to deleted the specified items with a "LiteralPath" (where the directory can be found) found in the "delete" column. The "Force" item tells PowerShell to remove items that cannot be changed, such as read only or hidden files. The "Recurse" item will force the confirmation of the deletion (so you don't have to babysit the command and keep hitting "Y"). Finally the "WhatIf" item allows you to test the command and see if it works before running it. This also gives you an opportunity to make sure you have the correct directories that you want to delete. Be sure to remove the "-WhatIf" when you are ready for the command to delete the selected directories!!

For more information check out the Microsoft Tech Net article on the Remove-Item cmdlet HERE.

Comments

  1. Larry,

    Thanks much. This worked great. You may want to make available a CSV sample to help in setting that file up. Even without that file (though), I was able to clean up some folders that had a specific criteria.

    Great Work,
    Greg R

    ReplyDelete
    Replies
    1. Hi Greg,

      Thanks for pointing that out! I had a screen shot there of the sample CSV that seems to have been lost... I've updated the post with some sample text of what the CSV should contain. Glad it worked for you.

      Delete

Post a Comment

Popular posts from this blog

Facebook and Two-Factor Auth

So in this post, I'm going to go over a quick setup on how to turn of two-factor auth with Facebook. Facebook does some interesting things once you turn on two-factor auth. If you have the app installed on your device, it will push a login code to that device. You can also set this up with SMS and the DUO Mobile app. We'll go over all three here. For a more high-level document on 2-factor auth, see my post HERE . As I've said before, this is not meant to be an in-depth guide, but more of a how-to for those that wouldn't normally think of turning on additional security settings. With that, let's get started: 1) Fist off, log into your Facebook on a computer and go over to the little down arrow in the upper right corner and select Settings. In the settings area, you'll want to select "Security" on the left. 2) In the Security Settings, you'll need to select the Edit button in the "Login Approvals" section. You'll be presented wi...

Replacing rsyslog with syslog-ng on RHEL 6.5

So...I had a piece of monitoring software that didn't play nice with the RHEL default rsyslog for log collection. The software was developed to only work with syslog-ng. I'll be going over the steps that I took, that worked for me, in replacing rsyslog with syslog-ng. I would imagine that these same steps should work for any Linux system similar to RHEL (Fedora, CentOS, etc.). For others (like Debein based distributions), I would need to look into that (coming in a future update to this post). First, remove rsyslog. You will need to keep the dependencies as they will be needed for syslog-ng: sudo rpm -e --nodeps rsyslog Next we will need to add the EPEL repository (more info can be found HERE ): wget http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm sudo rpm -ivh epel-release-6-8.rpm sudo yum repolist That last command will list all the installed repositories. You are simply verifying that the EPEL package has been installed. Now that we fi...

Using Python for GPG/PGP File Encryption - Part 2

Previously we looked at creating keys, importing public and private keys and the overall setup of gnupg with python. This time around, we're going to take a look at file encryption. Overall the file encryption process is fairly general/easy. But it lacks in the area of scaleablilty, ie to start, you'll only be encrypting one file at a time, which can be done outside of Python with ease. The idea of going over everything in Python, is that you can setup a script to encrypt multiple files in a folder (look for that in Part 3). Assumptions; you have python, and python-gnupg installed, and a public key from someone you want to encrypt and send files to imported to your keystore home (see Part 1 for more information here. Let's get started with Python file encryption. Start off by getting into your python shell, and enter the following: >>> import os >>> import gnupg >>> gpg_home = "/path/to/keyfile/.gnupg" >>> gpg = gnupg....