Skip to main content

Remove files from external storage devices attached to your clients

This is one that is sure to upset a few users.  This project came from one of my PowerShell classes. The client had a strict policy that only company issued USB storage devices may be used on company computers. Group Policy can help keep that requirement enforced.  They also had a policy that described the files types that can be stored on these USB drivers. The problem is that users were storing files that were not of the approved type.  So, what can PowerShell do in this situation?

The code below allows the administrator to provide a list of computer names and a list of  file name patterns to look for.  They were particularly concerned about .exe files.  So the pattern for this would be “*.exe”.  Just be fore warned that code like this can be particularly upsetting to users.  Make sure that a well known acceptable usage policy is in place in your organization before unleashing this code on your people.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64


 

Function Remove-Contraband

{

[cmdletbinding()]

Param(

    [String[]]$ComputerName = "LocalHost",

    [String[]]$Pattern

)

    ForEach ($Client in $ComputerName)

    {

        Write-Host "Scanning: $Client" `

         -ForegroundColor Cyan `

         -BackgroundColor DarkCyan

        ForEach ($Item in $Pattern)

        {

 

            Try

            {

                $Files=(Get-WmiObject win32_logicalDisk `

                 -ComputerName $Client -ErrorAction Stop |

                 Where-Object {$_.DriveType -eq 2} |

                 Select-Object *,@{Name="DrivePath";Expression={$_.Caption}} |

                 ForEach-Object {Get-ChildItem -File -Path $_.DrivePath `

                  -Recurse -filter "$($Item)"})

          

                If ($Files -ne $Null)   

                    {

                        Write-Host "Deleteing: $($Files.Name)" -ForegroundColor Red

                        $Files | Remove-Item -Force

                    }

                    Else

                    {

              

                    }

            } # End Try Block

            Catch{}

        } # End: ForEach ($Item in $Pattern)

        Write-Host "Completed: $Client" `

         -ForegroundColor Gray `

         -BackgroundColor DarkGray

    }

<#

.SYNOPSIS

Removes files matching a pattern from removable storage devices

 

.DESCRIPTION

Discovers removable storage devices attached to remote clients

and then scans the files of that device for patterns in the file

name.  If the name matches, then the file is deleted.

 

.PARAMETER Pattern

A string pattern to search for.  Use of wildcard characters are accepted.

 

.PARAMETER ComputerName

A list of computer names to search for removable storage devices on.

 

.EXAMPLE

Remove-Contraband -ComputerName "Indy-CL1", "Indy-CL2" -Pattern "*ps123","PS456"

 

Scans both clients Indy-CL1 and Indy-CL2 for removable storage devices.

The cmdlet then scans those storage devices for any file ending in

"ps123" and any file named "PS456"  If found, these files are deleted.

 

#>

}

Comments

Popular posts from this blog

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

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.

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