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

Visio Stencils Pack for Azure and Microsoft Integration (v5.0.0)

First off, I'd like to send a big shout out to Sandro Pereira who's been managing the vision stencils pack. Essentially, I'm re-posting his information here, because I had a really hard time finding the latest Visio pack for Azure, that wasn't a bunch of SVG's. My thought is that if more people re-post, maybe the search engines of the internet will have an easier time propagating the information... Sandero's Blog (the original post around the new stencils): https://blog.sandro-pereira.com/2019/10/18/microsoft-integration-and-azure-stencils-pack-for-visio-new-major-version-available-v5-0-0/ Sandero's GitHub: https://github.com/sandroasp/Microsoft-Integration-and-Azure-Stencils-Pack-for-Visio Microsoft TechNet Download: https://gallery.technet.microsoft.com/Collection-of-Integration-e6a3f4d0 I will say, and maybe it's just because I'm using Visio 2013, each icon has a boarder that needs to be removed when putting it on the page... Likely it

Disable Security Features to Dual Boot OS X - El Capitan

So, I've recently been working on updating/rebuilding my latest little friend (an 11" MacBook Air) to dual boot the latest OS X, El Capitan, and Kali. I'll go over everything in full detail as soon as I can finish the setup, but I wanted to get this out there for anyone else that may stumble upon any issues with setting up rEFInd on an updated mac. To start, while on Yosemite, I downloaded El Capitan from the App Store, and copied the install files to a USB. From there I preformed my upgrade. This might not be a good option for some people, as I'm sure your mac might be your primary computer... For me, that's not a problem. I tend to keep my essentials on USB drives / cloud storage as I tend to need access from different devices (phone, computer, tablet, etc.). After preforming a clean install of El Capitan, I headed over to the rEFInd website, download the program and ran the install.sh script... Now, that appears to work, like it did with pervious versions of

Windows Server 2008: Log on as batch job

From time to time, I have to set up some scheduled tasks that required a dedicated account to run. And when doing so, I'll usually forget that the dedicated account usually isn't given any more permissions than what it needs to complete the task at hand. So, after setting up the task, Windows will usually yell at me and say "The account needs batch job rights". So here's how to grant batch job permissions on your server. Go to your start menu, and start searching for Local Security Policy In the left pane of the MMC that opens up, expand Local Policies, and highlight User Rights Assignment. Now, in the left right pane, locate "Log on as a batch job" and double click it. In the properties window that opens up, add the user or group that needs this permission. I find that if you have multiple service accounts running different tasks on the same server, it's easier to just add a group verses the individual a