But don't take it from us. The Firebox M370 is Miercom tested and Miercom approved, outperforming its competitors for stateless and stateful traffic throughput scenarios. Learn more about the M370, M470, M570 and M670 and find the right solution for your organization today!
COURSE of the MONTH
8 days, 17 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Simple powershell script
Posted on 2011-03-04
I have a script right now that looks for all files certain day old and certain file extension and it deletes all of the files. This works fine and it counts fine
Then I have to delete all folders that correspond to being empty and that includes all sub folders too. I also have to output this into a file and display each file deleted. The output would show 30 folders deleted but actually 48 were really deleted.
Now my question is i am trying to do a count of all the folders deleted. I have this script but it just counts the deepest folders not all the ones deleted. Here is the part of the script i can not get to count
$TargetFolder = "C:\Users\user\Desktop\tem
$LogFile = "C:\Summary.txt"
$Count = 0
Date | Out-File -filepath $LogFile
get-childitem $TargetFolder -recurse -force | Where-Object {$_.psIsContainer}| sort fullName -des |
Where-Object {!(get-childitem $_.fullName -force)} | ForEach-Object{$Count++; $_.fullName} | remove-item -whatif | Out-File -filepath $LogFile -append
$Count = "Total Folders = " + $Count
$Count | Out-File -filepath $LogFile -append
Then I have to delete all folders that correspond to being empty and that includes all sub folders too. I also have to output this into a file and display each file deleted. The output would show 30 folders deleted but actually 48 were really deleted.
Now my question is i am trying to do a count of all the folders deleted. I have this script but it just counts the deepest folders not all the ones deleted. Here is the part of the script i can not get to count
$TargetFolder = "C:\Users\user\Desktop\tem
$LogFile = "C:\Summary.txt"
$Count = 0
Date | Out-File -filepath $LogFile
get-childitem $TargetFolder -recurse -force | Where-Object {$_.psIsContainer}| sort fullName -des |
Where-Object {!(get-childitem $_.fullName -force)} | ForEach-Object{$Count++; $_.fullName} | remove-item -whatif | Out-File -filepath $LogFile -append
$Count = "Total Folders = " + $Count
$Count | Out-File -filepath $LogFile -append
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
4-
4
8 Comments
if you JUST run this.... is the count correct?
$TargetFolder = "C:\Users\user\Desktop\temp"
(
get-childitem $TargetFolder -recurse -force | Where-Object {$_.psIsContainer}| sort fullName -des |
Where-Object {!(get-childitem $_.fullName -force)}
).count
Active 6 days ago
No the count shows 30. So it is counting incorrectly but deleting the right amount.
Active 6 days ago
It seems to just count the deepest folders and ignores the others. This I do not understand i thought the recurse would count each folder?
Hmmm.... I just ran a similar test...
Nested folders with no files in them... and others with files. The folders deleted were ONLY the deepest folder... I assume this would be due to parent folders *not* being empty... they contain other folders. In my case, the count was also correct
Nested folders with no files in them... and others with files. The folders deleted were ONLY the deepest folder... I assume this would be due to parent folders *not* being empty... they contain other folders. In my case, the count was also correct
Check this link out...
http://softwaresalariman.blogspot.com/2008/01/prune-directories-with-powershell.html
http://softwaresalariman.blogspot.com/2008/01/prune-directories-with-powershell.html
Active 6 days ago
not sure if you tested this at all but i get an error of
The term 'prune-directory' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is co
rrect and try again.
At line:1 char:16
+ prune-directory <<<< c:\users\paul.healey\temp
+ CategoryInfo : ObjectNotFound: (prune-directory:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
The term 'prune-directory' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is co
rrect and try again.
At line:1 char:16
+ prune-directory <<<< c:\users\paul.healey\temp
+ CategoryInfo : ObjectNotFound: (prune-directory:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
prune-directory is actually a function that the author of the post wrote (see the article).
I am guessing that powershell is removing items from top level (rather than bottom up).. resulting in the skewed results... that is... all empty folders deleted, but the count does not add up for empty folders.
If I run this on my test folder:
$TargetFolder = "C:\folders\"
get-childitem $TargetFolder -recurse -force | ? {$_.psIsContainer} |
sort fullName -des | ? {!(get-childitem $_.fullName -force -recurse)} | select fullName
... the bottom level folders are listed. If I replace the 'select' statement with the 'remove'... the top level folder is also removed.
I am guessing that powershell is removing items from top level (rather than bottom up).. resulting in the skewed results... that is... all empty folders deleted, but the count does not add up for empty folders.
If I run this on my test folder:
$TargetFolder = "C:\folders\"
get-childitem $TargetFolder -recurse -force | ? {$_.psIsContainer} |
sort fullName -des | ? {!(get-childitem $_.fullName -force -recurse)} | select fullName
... the bottom level folders are listed. If I replace the 'select' statement with the 'remove'... the top level folder is also removed.
Featured Post
Managing Active Directory can get complicated. Often, the native tools for managing AD are just not up to the task. The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
A brief introduction to what I consider to be the best editor for PowerShell.
My attempt to use PowerShell and other great resources found online to simplify the deployment of Office 365 ProPlus client components to any workstation that needs it, regardless of existing Office components that may be needing attention.
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
This tutorial will teach you the special effect of super speed similar to the fictional character Wally West aka "The Flash"
After Shake : http://www.videocopilot.net/presets/after_shake/
All lightning effects with instructions : http://www.mediaf…
Suggested Courses
Course of the Month8 days, 17 hours left to enroll
765 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.