EJWill

Well, when I see them playing games through Internet Explorer, I close the whole instance. They should not be playing games, and as such if there was any work on the other tabs, then hard luck. As long as the programme doesn't make any false positives, it's well within acceptable policy control to shut down the whole lot. I know of one school that shuts down the computer if they're caught. With regards to opening up SWF in other files, surely group policy already prohibits running and installing new programmes. The only programmes that need to be closed are those already installed. Maybe a KILL list is needed for customisation, like your last build.

What about if you take the application being used, as assumed. For example, if the file type being opened has the extension .swf and/or the mimetype application/x-shockwave-flash. Then closing SAFlashPlayer and/or any other media process as a given. This would then release the resource for you to delete?

I can't see why it can't be done peterp. Are you able to post a snippit of your code? One of us might come up with something ingenius!

When I was browsing through the FileSystemWatcher library I never found anything that might signify OnAccess. How wrong I was, I apologise for the unintentional misdirection However surely if the file is a registered game in the hashlist. One could also save the deletion until the resource becomes available to do so? With the previous release of your programme, we tested out a few logging ideas. Such as recording every instance a SWF file was loaded. Builds up a nice history to show to their form tutors. What I have done to those I have caught via a remote session, is change the SWF file permissions to deny total access for students. As soon as they load the SWF again, the SAFlashPlayer just stays white and never loads. I can't thank you enough peterp for giving a few of us hope, the battle might soon be over! Well until the next bright spark comes along...

Here, things have got so bad that we've had to setup ISA too block all SWF files from being downloaded. This does the job nicely and at least enables a whitelist for legit sites. However, the real problem we face at the moment is kids bringing in their SWF games on USB sticks and what not. As fellow IT techs are aware of too, classroom discipline is rarely upheld and the kids believe they can get away with it. With Flash also being on the syllabus, we can't prevent SAFlashPlayer from running. So right now we have a nightmare trying to stop the wave of gameplaying. Windows Server 2008 might have a solution for us for the future, but what with the state of the country and budgets we're now getting, we're stuck on Server 2003, with no proper filtering (and in some cases working)! But to think, if FileSystemWatcher had an OnAccess event, we'd all be laughing. Is anybody aware of an open source on-access scanner? My searching has come up trumps.