7 Jun
2017
7 Jun
'17
4:20 a.m.
On 2017-06-06 17:18, Fred Taylor wrote:
Sounds like a caching issue.
My thoughts too; however, the write-behind caching is turned off on the CLIENT. I *do wonder* however about the Windows Server 2016 write-behind setting. Is this related to the OpLocks setting mentioned in past server versions?