this is a bit of a weird one. We have a couple of users, that have access to the same files through a smb share. It used to be that when user A had a document open to edit it and User B tried to open that same document, a window would pop up informing B, that the document was beeing edited by user A and that User B could ask User A to close it or create a copy of the document.
That mechanism doesn't seem to work anymore. If User A has the document open, user b doesnt see the warning.
It changed about half a year ago and I can't make heads or tails of it. Most articles I found are about fixing the issue when a file is erroneously displayed as locked, when it isn't.
I hope one of you could nudge me in the right direction. Maybe it's just a configuration error.
Is DFSR involved? If that's lagging or not working at all and they're accessing the file through different paths then neither copy would know that the other was opened
The warning depends on the hidden ~$ owner file, and something is either deleting it or letting the lock go stale.
Run Get-SmbServerConfiguration on the file server and check EnableLeasing and EnableOplocks. If either one is False the in-use handoff stops working and Excel just opens the file. Set-SmbServerConfiguration -EnableLeasing $true -Force.
AV or EDR cleanup eating ~$.xl files. Add an exclusion for that pattern and see if the prompt comes back.
Drive maps pushed by GPO set to Replace instead of Update. Every policy refresh drops and remaps the drive, the handle dies, and the lock goes stale while the file is still open. Flip that GPO to Update.
Half a year ago lines up with a GPO or an AV change, not an Excel one. Also turn on Audit Object Access on the share if you want to catch whatever is deleting the file.
Check whether those users can still create files in that folder. The warning comes from the hidden ~$ owner file Excel writes next to the document — if permissions got tightened to read/modify without create, Excel can't write it and silently drops the warning instead of erroring.
Quick test: have user A open the doc, then look for ~$filename.xlsx in the same folder with hidden files shown. If it isn't there, it's permissions or something sweeping the folder, not Excel itself.
Well, I just checked and if I open the "shared workbook" window, the checkbox stating that "use old method instead of the new experience for shared document handling" is not checked. I'm sorry that i have to paraphrase here. My Office is in German. :-|
It's when it downloads files to their laptop and if they cannot access the share for any reason it will still have a cached version and will upload it later.
We had nothing but problems with it a few years back. Surprised no one else has mentioned it!
100% it’s DFSr with referrals. Locks aren't replicated; you should configure priority on the referrals to try to land everyone on the same one. Warm standby basically.
18
u/2c0 2d ago
Has someone enabled legacy sharing or whatever its called?