Consider the following scenario:
In this scenario, when you use a Microsoft Office Application to open files from the Sharepoint Webdav Share by using the DFS path and you make changes to the files, the files remain locked for extended periods of time after saving the changes and closing the files.
Therefore every user that tries to open the file during this time will be presented with a dialog simillar to this:
"This file is locked for editing by %Username%
Do You want to:
o View a read-only copy
o Save and edit a copy of the file
o Receive a notification when the server file is available."
Opening and Saving Files with other Applications such as Notepad is not affected.
The Problem does not ocurre if the WebDav Path is used instead of the DFS path.
- You are using a Distributed File System Namespace (domain based or standalone)
- You are using a Sharepoint Foundation Server
- You configured a DFS link to point to your Sharepoints Webdav share with a Folder Target such as \\Server@port\DavWWWRoot\Share\Folder
- You use the DFS path (i.e. \\Contoso.com\DFS\Link-to-Sharepoint) to access Data on the WebDav share.
In this scenario, when you use a Microsoft Office Application to open files from the Sharepoint Webdav Share by using the DFS path and you make changes to the files, the files remain locked for extended periods of time after saving the changes and closing the files.
Therefore every user that tries to open the file during this time will be presented with a dialog simillar to this:
"This file is locked for editing by %Username%
Do You want to:
o View a read-only copy
o Save and edit a copy of the file
o Receive a notification when the server file is available."
Opening and Saving Files with other Applications such as Notepad is not affected.
The Problem does not ocurre if the WebDav Path is used instead of the DFS path.