what would be the fastest way in powershell or batch to search for the existance of a file

what would be the fastest way to search the entire computer for a known file and make a log of what computers have the file?
basically search c:\*.* recursive for somefile.exe

I need to see if this file being used on our network because it needs to be removed.  Thanks!
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

Justin YeungConnect With a Mentor Senior Systems EngineerCommented:
I agree with Qlemo, if you want  a script to scan the network will take ages to finish (it really do 1 by 1).....specially you are talking about scanning all machines on the network (I don't know how much machine you have but it is not fun even with 100 machines)

either setup a powershell script to run via GPO as logon script or enable powershell remoting (I personally disagree enabling PS remoting on workstation)
Justin YeungSenior Systems EngineerCommented:
do you mean search the entire network of all the computers that contain certain .exe file and create a log of what is found and not?
sirbountyConnect With a Mentor Commented:
Good info here: stackoverflow.com/questions/7196937/how-to-speed-up-powershell-get-childitem-over-unc

# Usage:
# $directory = "\\SERVER\SHARE"
# $searchterms = "filname[*].ext"
# PS> $Results = Search $directory $searchterms

[reflection.assembly]::loadwithpartialname("Microsoft.VisualBasic") | Out-Null

Function Search {
  # Parameters $Path and $SearchString
  param ([Parameter(Mandatory=$true, ValueFromPipeline = $true)][string]$Path,
  try {
    #.NET FindInFiles Method to Look for file
    # BENEFITS : Possibly running as background job (haven't looked into it yet)

  } catch { $_ }


Open in new window

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

bbimisAuthor Commented:
something more on the lines of this
$creds = Get-Credential
Get-Content C:\office.txt | ForEach-Object `
    $compname = $_
    If (Test-Connection $compname -Count 1 -Quiet)
      $files = get-childitem c:\ -recurse | ? {$_.name -eq "blah.exe"}

 	  write-host there are $files.count matching that name on computer $compname

 	  foreach ($file in $files){
 		$directory = $file.directory
 		$fulldirectorypath = $file.directory.fullname
 		$fullfilepath = $file.fullname
		$info1 = $file.name 
        $info2 = "The directory path is $fulldirectorypath "
        $info3 = "Computer ID is: $compname "
        Write-Host $info3
		"---------------------------" | Out-File c:\blah.txt -Append
		$info1|Out-File c:\blah.txt -Append
 		$info2|Out-File c:\blah.txt -Append 
		$info3|Out-File c:\blah.txt -Append
		"*******End of Data*************" | Out-File blah.txt -Append

Open in new window

Justin YeungSenior Systems EngineerCommented:
ok, so how would you get the source? from AD search with specified name? or from an OU?
or from a txt file?

and the output, what info would you need?

what would you like to do with the file that found? delete it ? move it somewhere and rename it?
bbimisAuthor Commented:
Well we have found a file that is causing errors on our system. i would simply like to generate a list and make 100% certain that i have scanned each computer on the network with the supplied list (i pull it form active directory).  
i would like the file to be in cvs or excel so i could look at each computer in a grid and see if it has the file and also where on the system it is.

Thanks for the help!
Ok, so you have a text list with computer names we can process. No issue with that.

Get-ChildItem is not suited well, unless execute locally. It needs to create and manage a lot of objects, so a lot of overhead there. You do not really need the file info, only path and name, and that can be retrieved with the above routine.
a) it is processing one machine at a time, waiting for completion
b) stops as soon as there is an error like missing privileges.
bbimisAuthor Commented:
so can you help me with a solution that will scan all of them even if it errors?
Sadly I cannot see anything different than either running Get-ChildItem with an UNC path  - slow, involving a lot of resources, ... -  or remote execute that cmdlet. However, that requires to have PowerShell Remoting enabled on all boxes, and set up correctly so you can access it. Not something you can be sure about.

The traditional approach is to write a logon script running the scan in background locally, writing back results to a central file, and not running if it has been running already.
Are you able to narrow down the directories to search for?
bbimisAuthor Commented:
i used this method and worked fine after a few tweaks for my enviroment.  Thanks!
All Courses

From novice to tech pro — start learning today.