Is there a way of preventing users from copying files from a share?
Scenario:
We have a large share containing video files + audio files.
We want to prevent staff from copying files from this location and storing in their H: drives - therefore preserving what space we have left.
What we don't want to do is prevent staff from saving certain file extensions to their H: drive using R2 for example.
Any advice would be appreciated.
Not easily i would think mate. How do you stop copying from ... id first of all think that there isnt going to be a permission or right that can achive this unfortunatley (if there is id love to hear it aswell).
Maybe write a hook to intercept the file copy request to the HDD if you got the goods in programming ( i dont, dont even know if its possible, but i think this is how FSRM does it blockign/quota thing) .
Only solution i can even concieve is append a prefix/suffix to all the files you dont want to copy away (like noCopy_filename.mp3) to write a service that loops looking for file with name noCopy_* then delete that stuff accordingly.
One way to skin a cat, but ill be honest probably the worst way haha Id love to hear a solution to this aswell.
Slightly more sensible but tedious is to use a file restriction policy with hash rules and disallow the files on H:\
But surely they could rename the file to get around this?
if your talking teachers..... most of them don't know what a file extension is(edit: even after telling them), let alone changing it :P
no, hash rules work on the checksum of a file. So even renaming it wont stop a file restriction policy blocking it.
I have looked at this and each avi file has a different hash - apart from the 32771 at the end - does this code give it the .avi characteristics?
So for example:
a4a7834df9c45b5c1a439de452b8dc00:290148616:32771
or
b4ed0fcb0170272dd3b33296d986bc32:373203218:32771
are the file hash for two different avi files
If so by creating a hash rule for avi ending 32771 accroding to hash = that is no different to preventing .avi using FSRM in R2?
Or is it we would have to create a hash rule for each avi that was created which we wanted them to prevent saving to their own H: drive?
Last edited by Paid_Peanuts; 23rd May 2008 at 02:12 PM.
One hash rule for each file I'm afraid. You can only use wildcards for path rules.
Have you thought setting up a streaming server to share the files instead of a traditional file server?
There a probably a number of products you could use, a brief list.
Shoutcast - audio only I think
Windows 2000 came with a media server. I don't know if it exists for new versions though.
Real's Helix server.
Last edited by sjatkn; 25th May 2008 at 09:20 AM.
2003 has one built in, I've got some music on there which is (or at least was) used by teachers for pacifying pupils in class (or just drowning out their whines!) Can't recall trying video on it, but don't see why it wouldn't work, as it's called streaming media services not streaming audio!
I''ve got a 2008 box here at home, I'll have a play later and see what I come up with!
There are currently 1 users browsing this thread. (0 members and 1 guests)