Hi
Thanks for the response but I think you're misunderstanding my question and perhaps I haven't explained it clearly enough.
We don't want to use SMBv1 at all - We know how to enable\disable it on the clients and server.
What we want to do is to use SMBv3 but disable oplocks to avoid any issues caused by them when using this legacy application.
Unfortunately you can't disable oplocks on server 2012R2 under SMBv3. It's only possible to disable it under SMBv1, so you have disable SMB2\3 first before adding the reg key to disable oplocks.
With our Windows 7 clients you didn't have to do this as SMBv1 was already in place but since replacing them with Windows 10 we have to enable SMBv1 so they can still talk to the server.
However, in Windows 10 we've noticed an option under the set-smbclientconfiguration cmdlet which is "useOpportunisticLocking (which can be set to false" and "OplocksDisabled (which can be set to true)" . This looks as though we can tell the client not to use oplocks. If this is the case then implementing this option will allow us to re-enable SMBv3 on the server side and also the clients and prevent the issues caused by using oplocks.
My question is - Is my understanding of the cmdlet correct? Will this option prevent the client from requesting an oplock on the server?
Cheers