Skip to main content

PowerShell search for files




Searching files in PowerShell is quite flexible in some ways.

Why it's flexible? It provides a lot of option that you can type on cmdlet parameters.

This code below will search for ".doc" and ".docx" files recursively in a given path.

Get-ChildItem -Path "D:\My Docs Folder" -Filter *.doc* -Recurse

If you have standard file naming convention, or you save files in a way that you could easily remember then PowerShell can also do it for you.

Code below will search for any documents that its file name starts with Feb or feb.

Get-ChildItem -Path "D:\My Docs Folder" -Filter Feb*.doc* -Recurse

It's just document, the file name extension can be replace with *.xls* to search for excel worksheets or any file name extension such as ".png" or ".jpeg" or other video files or any type of file.

Or if you searching for saved outlook messages, use *.msg to search for saved outlook emails.

If you want to search by file size, PowerShell can also do the task.

Example below will search for any PDF files which size is greater than 3 megabytes or 3MB.

Get-ChildItem -Path "D:\My PDF Files" -Filter *.pdf -Recurse |

Where-Object {$_.Length -gt 3MB}

If need to search by file creation date, see example below:

Get-ChildItem -Path "D:\My Documents" -Filter *.doc* -Recurse |

Where-Object {$_.CreationTime.Date -match "2013"}

Example above will search for files created on year 2013.

Example below will search for text files modified on the current date.

$xtoday = (get-date).Date

Get-ChildItem -Path "D:\My Documents" -Filter *.txt -Recurse |

Where-Object {$_.LastWriteTime.Date -match $xtoday }

That is just few examples on how PowerShell can do to search for files, the rest will depends on what creativity can brings.



To check for files or folder modified on last X minutes check out link below:
http://quickbytesstuff.blogspot.sg/2014/04/powershell-check-folder-for-modified.html



Cheers!! Hope it helps...

Comments

Popular posts from this blog

WMIC get computer name

WMIC get computer model, manufacturer, computer name and  username. WMIC is a command-line tool and that can generate information about computer model, its manufacturer, its username and other informations depending on the parameters provided. Why would you need a command line tool if there’s a GUI to check? If you have 20 or 100 computers, or even more. It’s quite a big task just checking the GUI to check the computer model and username. If you have remote computers, you need to delegate someone in the remote office or location to check. Or you can just write a batch file or script to automate the task. Here’s the code below on how get computer model, manufacturer and the username. Open an elevated command prompt and type:     wmic computersystem get "Model","Manufacturer", "Name", "UserName" Just copy and paste the code above, the word “computersystem” does not need to be change to a computer name. A...

Print error 016-799 - Fuji Film Xerox

016-799 Fuji Xerox or Fuji Film print error code. That shows a description error as “Print instruction Fail detected in decomposer.” The error code and error description are alien languages for users and even system administrators who are not familiar with Fuji Xerox error code. The error code is quite simple and easy to fix, if the job print goes to the printer but print out doesn’t come out. So, basically the print job was received by the printer, but the printer just doesn’t know what type of paper or what size to use or which tray to utilize for the print out. In some instances, this is just a paper mismatch but the error description; if using Windows 10 to print does not exactly points to what is the issue. First thing to check, is the paper size selected by the user to print. Example, if the printer configuration is A3 and A4 sizes only. But then the person printing the file accidentally chooses “A4 Cover” then this error 016-799 will occur. ...

How to check office version from command line

The are quite a few ways to check office version it can be done via registry, PowerShell or VBScript and of course, good old command line can also do it. Checking Windows office version whether it is Office 2010, Office, 2013, Office 2016 or other version is quite important to check compatibility of documents; or just a part of software inventory. For PowerShell this simple snippet can check the office version: $ol = New-Object -ComObject Excel.Application $ol . Version The command line option will tell you where’s the path located; the result will also tell whether office is 32-bit, 64-bit and of course the version of the office as well. Here’s the command that will check the office version and which program directory the file is located which will tell whether it’s 32-bit or 64-bit. Command to search for Excel.exe: DIR C:\ /s excel.exe | find   /i "Directory of"  Above command assumes that program files is on  C: drive. Sample O...