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

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes.  While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted.  When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places.  First off in the Active Directory Administrative Center.  This is what caused the initial confusion.  Take a look.  This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3.  Test3 is a valid, functioning user account.  Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

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.