I am moving from 2008 R2 to a new 2022 server. I remember that we needed to turn off op-locks because we have topspeed tables. To do that on the new servers would require turning on SMB1. Not recommended because of security risks.
So I reached out to Experts Exchange here was their recommendation:
OPLOCKS was a feature of SMB1. For SMB2 and 3, it’s called leasing, and here’s how to turn it off:
Click Windows Start Press the Windows keyand then type Command. Right-click on Command Prompt and choose Run as administrator.
Copy and paste the following commands into the command prompt window:
I have a 20 year old utility called FixOLandRC. OL is “OpLocks”, and I can’t quite recall what RC stands for. Resource Contention? However, I’ve not used it for at least 5 years.
More recently, I’ve used oplock.sbi within Lindersoft’s SetupBuilder. That’s probably a better approach.
I believe it’s something that Friedrich provided. Mine is from 12 years ago, so there may be a newer version. It’s probably best to reach out to him and ask.
I popped your image into another tab, Mike.
One thing I do see in the bottom quarter of the image is the disabling of SMB 2.0.
Presumably now one would also need to disable SMB 3 if one were to go back to the world of disabling oplocks.
(I don’t think it would be polite to disable those silently on somebody’s server.)
Again, I haven’t had to keep up with oplocks. Possibly interesting the “DisableLeasing” approach described in the original post in this thread? SMB2, SMB3 and Opportunistic Locking
Yeah, it’s definitely a very heavy-handed solution, just for the sake of continuing with TPS files. Moving to SQL is definitely the preferred solution.
I will be converting most of these tables to SQL, mySQL, or Oracle in the near future. Still weighing out all three. The thing is some of the vendors that make enhancements for Clarion ship their software with TPS files. I guess when the time comes I’ll have to approach the vendors about this.
In the mean time I am going to take OPlocks into consideration as I am setting up this server. I am responsible for installing the new in house server. I also wrote the software they are currently using for their accounting, billing, and inventory systems.
Pretty much makes me responsible for everything.
49 years and still coding and setting up networks. Love this profession!