Deny delete creates temp files

  • Thread starter Thread starter kevgroups
  • Start date Start date
K

kevgroups

All,

On a Windows 2000 server I have a file which I want users to modify
but do not want them to be bale to delete it. I am sure I have set
the permissions correctly. The permissions are not inherited and I
went through the advanced screens to deny the delete (got the deny
takes precedence warning etc) and now the users ahve "Special
Permissions".

However, when the file is modified, an oddly named file is left
behind. The file in question is an Excel file.

Can someone please tell me

a) Excel is doing this. I doubt htis as the behaviour affects all
users and the only began when permissions were changed.

b) Windows is doing for some reason other than file permissions

c) Windows has to do this to prevent the file being deleted. As the
file cannot be deleted (and modified????) a new file is created with a
new name. This new file is saved with the changes. Then the new and
old files are renamed (names swapped).

I am thinking C - but the above behaviour occurs even when the domain
admin modifies the file and the domain admin has delete permissions.

If anyone can shed any light on this I would be msot grateful.

Kev
 
A

Office applications use temp files
Not having delete means that the account running the Office
application is unable to clean up after itself.

Consider using a grant of Full to Creator Owner so that accounts
will have the needed permissions on files (these temps) that they
have created.
 
A

Office applications use temp files
Not having delete means that the account running the Office
application is unable to clean up after itself.

Consider using a grant of Full to Creator Owner so that accounts
will have the needed permissions on files (these temps) that they
have created.
Click to expand...

Many thanks for your suggestion. Office not being able to delete its
own temp files does make sense. The question now is how do I
correctly configure permissions so that the temp files can be deleted
but not the original Excel file. I am assuming it's possible - I
can't be the first person wanting to do this.

I tried your suggestion of giving Creator Owner full control, but when
applying the changes the actual user who created the file is added to
the permissions list. What I need is to be able to specify the
"Creator Owner" of the temp file - i.e. the person who opened the
spreadsheet.

Can this be done?

Kev
 
Many thanks for your suggestion. Office not being able to delete its
own temp files does make sense. The question now is how do I
correctly configure permissions so that the temp files can be deleted
but not the original Excel file. I am assuming it's possible - I
can't be the first person wanting to do this.

I tried your suggestion of giving Creator Owner full control, but when
applying the changes the actual user who created the file is added to
the permissions list. What I need is to be able to specify the
"Creator Owner" of the temp file - i.e. the person who opened the
spreadsheet.

Can this be done?
Click to expand...

Without doing programming, use of Creator Owner is about a close
as you will get, meaning that the account that owns a file (including
the temps) will have the elevated grant over it. You may feel better
with Creator Owner Modify rather than Full.

Roger
 
Back
Top