• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 311
  • Last Modified:

Can't save documents with deny delete permissions on shared drive

We have a shared directory on a Windows Server 2003. For user accounts, I have given them full access for the share permissions, and with the NTFS permissions I have allowed everything while denying "delete" and "delete files and subfolders."

Since this is for a school's computer lab, we need to meet certain requirements.

1. All students use 1 account to log in.
2. Students need to be allowed to create, modify, and save their work.
3. Students cannot be allowed to delete any files.

The problem exists with PowerPoint that prevents someone from being able to save their work if they are prohibited from deleting files, because Office deletes the temp files that are created when working on the file.  With Word and Excel this is not a big deal, as it just leaves some temp files in there that need to be cleaned out.  But with PowerPoint it won't let the user save without generating error messages that the file already exists, is read-only, etc.  The only way around this according to Microsoft and other posts I have read is to allow the users to have the delete permissions.

This is a REALLY foolish shortcoming on Microsoft's part.  Anyone have any thoughts on how to work around this?
0
Ad-Apex
Asked:
Ad-Apex
  • 3
  • 2
1 Solution
 
ewkellyCommented:
You could set your temp and tmp folders to something local, or to a network share where they can delete.
0
 
Ad-ApexAuthor Commented:
Can you please tell me where to do this?
0
 
ewkellyCommented:
Windows control panel, system settings, advanced, environment.
0
 
Ad-ApexAuthor Commented:
That doesn't work. The files exist on a shared drive.  When they open them it automatically creates the working copy in that location and not in a local temp drive.

I looked into this further, and it seems there is no way around it except to give every user their own login and set right so that only they can delete their own files.  There is no other way around it.
0
 
Ad-ApexAuthor Commented:
I accepted my own answer because there is no solution to this problem according to Microsoft. I have to change the actual procedure that I am using.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now