I'm running into an issue with user's not being able to move documents and/or folders because they are still open by someone, somewhere.
Basically, users have built a process where they have a network mapped drive that contain a bunch of folders and sub-folders that contain various documents (Word, Excel, PDF, etc). Multiple users access those folders and files as different employees have different parts to do in the process. Then, when everything is done and ready, someone will move files and/or entire folders from one place to another as part of this workflow.
The problem here is that many times users cannot move the files or folders sometimes because they get the message that someone has them still in use. Then, I get a call back in IT to request I see who has the file open and/or if I can close those files.
I have to go into Windows Computer Management > Shared Folders > Open Files and then manually search for the folder path and file and then see who has it open. Many times the user reports that they in fact do not have the file open and then I have to manually close the session.
My question is: is there a reason that the file/folder would still be open by the user or computer (perhaps and unrelease file handle in memory) even though they've closed out, or what? What is the cause of this if the user doesn't actually have it open? Are there any tools or settings I can change on the file server, the user workstation or the Microsoft Office apps to fix this?