Skip to main content

How to use PowerShell to scan a server for a specific file type?

This is an easy one liner:

Get-WMIObject Win32_LogicalDisk -filter "DriveType = 3" | Select-Object DeviceID | ForEach-Object {Get-Childitem ($_.DeviceID + "\") -include *.wav -recurse}

Let’s break this one down into its individual parts.


Get-WMIObject Win32_LogicalDisk –filter “DriveType = 3”


In the above line, we are using WMI to access all the logical drives on the server.  We are using logical drives because we do not know how the drives are partitioned.  We are also looking for Drive type #3. Here is a list of the different drive types:


1 - Drive could not be determined



2 - Removable drive



3 - Local hard disk



4 - Network disk



5 - Compact disk (CD)



6 - RAM disk



 



Select-Object DeviceID



The Select-Object cmdlet allows us to focus just the DeviceID. The DeviceID is the drive letter.



ForEach-Object {Get-Childitem ($_.DeviceID + "\") -include *.wav -recurse}



The ForEach-Object cmdlet allows us to examine one object at a time in an array of objects.  The Get-Childitem is functionally the same as DIR in dos.  By using the $_.DeviceID we are simply saying “get the drive letter of the hard drive we are looking at.”  Adding the “\” sets up the correct syntax for our search. the –include parameter tells PowerShell what we are interested in.  In this case, we are looking for all files with a .wav extension. The –recurse parameter gets the items in a location, and in all child locations.  It is what allows us to search through each folder, and sub folder on each hard drive.



We can take this one step forward.  The remove the files found, add this to the end of the command line above



| Remove-Item



Be careful with this. You can do some damage if you are not careful. If you want to confirm each deletion, uses this line instead:



| Remove-Item – confirm

Comments

Popular posts from this blog

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.

Set up your Environment to utilize Invoke-GPUpdate

I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...

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