In my particular situation, i have server 2008 r2 which has 24 drives connected to it via map unc (\\Server Name\Movies\then movie drives\then folders)
all the clients that connect to that jrvier library in home network or outside if authentication is set to on, have the ability to delete all of the server jriver files/Mapped unc files.
Exactly. That's what I mean.
Why??
Ignore JRiver for a minute. On the share, especially if you're serving them off of Windows Server, but even if they're on Windows regular, you can choose permissions for the share. I'll assume that the Windows user that all of your client machines are logging in as has Read/Write/Modify permissions on the share (Full Control in Windows parlance). Why?!? The whole idea is you don't want these people to delete the files. MC has nothing to do with it (that's just the mechanism they're using to delete the files). Block them from deleting the files.
I'm not 100% that this will work, but I'm about 85% that it will. I can explain...
I have a setup at the office that is just the opposite. We have a file share on the
Isilon that contains all of the lecture captures we do at the office. This UNC path is watched by a copy of MC, which auto-imports their contents, and then our web server uses the JRSidecar XML files to generate a "corporate YouTube" on the fly from the metadata in MC's Library. It sounds fancy, but it is actually pretty clunky (and really should use MCWS -- if it did, it'd be way cooler).
Anyway, I have a set of users who run the lectures, and actually do the captures. They have copies of MC installed and can tag the files, adding [Name], [Description], and [Series] (for the name of the course or event or whatever). A lot of times what happens when you're recording these things is you end up with little 3-30 second "stub" files that are junk. You think they're about to start... The dude walks up to the podium so you hit start and then they realize they forgot something or their shoe is untied, and it is a fake-out, so you click stop and wait a bit more. It doesn't matter. You end up with these little useless stub recordings.
I'd have to check what actually works, but the policy we have (which I invented) is that when they have one of these, they send the filename to me and I delete them. Because (again, I need to check it to be sure this is true) they cannot. They have Read-Only access to the actual UNC path, and when the MC client tries to delete a file (I'm 85% sure) the client deletes it "locally" from disk. It doesn't "tell the server" to delete it, it updates its local cache of the Library (which eventually gets synced to the server) and then it tries to delete the file locally. Since they don't have permissions to delete the file on the UNC path, this fails (silently) and this happens:
* MC Client copy deletes the file.
* It
can remove the file from the Library, and does, but cannot delete the file from disk.
* MC Client eventually syncs this to the server, which removes the file from the Library.
* MC Server's Auto-Import immediately re-imports the file (since the Ignore Previously Removed option is unchecked, because I'm not an animal)
* Since the file was previously removed, MC doesn't re-import it from scratch, but "un-deletes" it, as it does, and no metadata is lost, regardless of the JRSidecar status.
The only "metadata" I lose when they forget and try to delete one of these is the [Date Imported]. For me, this is actually pretty convenient since I have a Recently Imported view that is my default on that server, so I just pop it open and notice 2 or 3 new 3-second clips at the top of the list, and I email them and scold them for forgetting to tell me to delete them, and I delete them.
This scenario plays out on a monthly basis. The only part I don't know for sure is the mechanism of the deletion, because I haven't tested it explicitly (at least recently). But, if I could have these users delete the files directly, I would (because it is a pain in my butt and it really isn't my problem if they accidentally delete their own valuable content)... So, I think this is exactly how it works.
So... Make the clients log in
to Windows with user credentials that cannot delete anything. It still risks the MC Library metadata, if you care about [Date Imported] anyway, but MC auto-backs-up the Library anyway so it really doesn't matter. You can always restore the backup, and they cannot delete the files themselves (the real risk). If they
do mass-delete like jerks you:
* Find them and smack them.
* Restore the Library Backup
* Sigh and crack open a beer reveling in how awesome you are.