We have a windows 2016 file server with a DFS namespace.
Users have their shared drive "S" pointed to a share called \\dfsnamespace\shared.
Users currently have an issues with changes being lost on word documents which are edited by multiple users as they collaborate on these documents.
The problem is that if one UserA has the word document open then if UserB opens this document sometime later then he doesn't get prompted that UserA has the document open and UserB can only open it in read only mode. Thus UserB also gets a read-write copy of the document. Now if user User A saves the document with his changes and then later on UserB saves the document with his copy then the UserA's document changes are lost and UserB's changes are kept.
Have you seen this issue and what is the cause?
I ran the "Get-SmbServerConfiguration" and ensured that the "EnableOplocks" is currently set to "true" and has a "OplockBreakWait" setting of 35.
From these values I understand that if a windows 10 client machine is off the network for 35 seconds then this oplock will be released.
From these I understand:-
1. If the UserA's client's machine goes to sleep state then the lock will be lost and thus UserB will get a read-write copy of the document and thus resulting in this issue. Is this write? (I tested this in another environment and this is the behavior I observed there as well)
2. If UserA switches from wired to wireless network then because network has changed then his lock will be lost on the server. Is this correct?
3. In scenario 2 if the user establishes connection with wireless before 35 seconds (when the old oplock from wired connection is released) then he will have to wait for 35 seconds to get a new oplock and then he can save the document.Before that he can't save the document. Is this correct?
Also :-
a) How is the oplock created - Is it based on the hash of client & server IP? Or just uses client name?
b) If this word/excel document is shared. Will that make any difference to this behaviour.
I understand that Sharepoint is the best collaboration application which will resolve these issues but the client does not have sharepoint.
Users have their shared drive "S" pointed to a share called \\dfsnamespace\shared.
Users currently have an issues with changes being lost on word documents which are edited by multiple users as they collaborate on these documents.
The problem is that if one UserA has the word document open then if UserB opens this document sometime later then he doesn't get prompted that UserA has the document open and UserB can only open it in read only mode. Thus UserB also gets a read-write copy of the document. Now if user User A saves the document with his changes and then later on UserB saves the document with his copy then the UserA's document changes are lost and UserB's changes are kept.
Have you seen this issue and what is the cause?
I ran the "Get-SmbServerConfiguration" and ensured that the "EnableOplocks" is currently set to "true" and has a "OplockBreakWait" setting of 35.
From these values I understand that if a windows 10 client machine is off the network for 35 seconds then this oplock will be released.
From these I understand:-
1. If the UserA's client's machine goes to sleep state then the lock will be lost and thus UserB will get a read-write copy of the document and thus resulting in this issue. Is this write? (I tested this in another environment and this is the behavior I observed there as well)
2. If UserA switches from wired to wireless network then because network has changed then his lock will be lost on the server. Is this correct?
3. In scenario 2 if the user establishes connection with wireless before 35 seconds (when the old oplock from wired connection is released) then he will have to wait for 35 seconds to get a new oplock and then he can save the document.Before that he can't save the document. Is this correct?
Also :-
a) How is the oplock created - Is it based on the hash of client & server IP? Or just uses client name?
b) If this word/excel document is shared. Will that make any difference to this behaviour.
I understand that Sharepoint is the best collaboration application which will resolve these issues but the client does not have sharepoint.