Do not allow users to delete files from server share.

[Guest]

When I set up user security on my W2k server for users to be able to read,
write, execute, and modify, but not delete on file shares, I run into issues
with Microsoft Office documents. When you edit an Office document, a temp
file(s) is created and it is actually the temp file that you are editing.
When you go to save your changes, the changes are applied to the temp file
only. The original Office document is auto deleted and the temp file is auto
renamed to the name of the original Office document. The problem is that I
do not want users to be able to delete files out in the share. Even though
they are not directy deleting the files, Office is doing it on their behalf
in order to save their work. Their Saves are erroring out because they do
not have delete rights, and the share fills up with a bunch of temp files.
Does anyone know a way around this?

 

[Bill Baka]

When I set up user security on my W2k server for users to be able to read,
write, execute, and modify, but not delete on file shares, I run into issues
with Microsoft Office documents. When you edit an Office document, a temp
file(s) is created and it is actually the temp file that you are editing.
When you go to save your changes, the changes are applied to the temp file
only. The original Office document is auto deleted and the temp file is auto
renamed to the name of the original Office document. The problem is that I
do not want users to be able to delete files out in the share. Even though
they are not directy deleting the files, Office is doing it on their behalf
in order to save their work. Their Saves are erroring out because they do
not have delete rights, and the share fills up with a bunch of temp files.
Does anyone know a way around this?

There is one idea I have that may be a little off the wall, but I have
seen programs to make a ram drive on the users PC if they have enough
memory. That means a Gig or more so you can set up a few hundred Megs
for the .tmp files. Just set it up so they can save the documents on
their hard drives until it is time to upload the finished document.
Windows seems to be all about memory, memory, and more memory. A friend
is experimenting with filling a machine with 3 Gigs and making a 1 GB
swap file if he can get it to boot and be stable. I am running on a
measly 128 MB since my big stick blew up and was out of warranty.
Zdnet, cnet, Brian Livingston, Peter Coffee, or one of the many gurus
should be able to answer this much better than I can.
Best of luck, and if you learn a new trick please report it back here.
Bill Baka

 

[lforbes]

There is one idea I have that may be a little off the wall,
but I have
seen programs to make a ram drive on the users PC if they have
enough
memory. That means a Gig or more so you can set up a few
hundred Megs
for the .tmp files. Just set it up so they can save the
documents on
their hard drives until it is time to upload the finished
document.
Windows seems to be all about memory, memory, and more memory.
A friend
is experimenting with filling a machine with 3 Gigs and making
a 1 GB
swap file if he can get it to boot and be stable. I am running
on a
measly 128 MB since my big stick blew up and was out of
warranty.
Zdnet, cnet, Brian Livingston, Peter Coffee, or one of the
many gurus
should be able to answer this much better than I can.
Best of luck, and if you learn a new trick please report it
back here.
Bill Baka

Hi,

Have you tried giving SYSTEM=Full Control to the drive? I haven’t ever
had this problem with MSOffice before. I have SYSTEM=Full control on
all my shares though.

Cheers,

Lara

 

[Bob I]

Work around in this "security arrangement" would be to "edit the file
locally" and then copy it back to the server.