J
JoeOst
Hi all,
A client of ours is facing performance issues with a specific app (Sage 100 Contractor). They have a 20 second delay when opening certain areas of the program. Long story short (after dealing with the vendor and going through every troubleshooting step), i now suspect it may be an OpLock issue. This app is using flat DBF files, which is very likely to be affected by OpLocking. The file server is a 2012 VM, and yes, virtual machine queuing is disabled on the hosts NIC.
If i recall correctly, one cannot not disable OpLocking for SMB2, and the only solution was to disable SMB2. With server 2012, SMB3 was release. Is this still true for SMB3?
In Server 2012, Microsoft introduced new powershell cmtlet to control SMB. I could run Set-SmbServerConfiguration -EnableOplocks $false to disable OPLocking, but does that do anything if SMB2 and SMB3 are enabled? If i do disable SMB2/SMB3, is it enough to disable it on the server, or do i also need to disable on the workstation?
If i cant disable OpLocking in SMB3, but dont want to disable it, then i could disable OpLocking on all (Windows 7) clients (to stop them from requesting locks), by setting OplocksDisabled to 1 in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters. But, will this be enough to completely stop OpLocking from taking place
Thanks.
Continue reading...
A client of ours is facing performance issues with a specific app (Sage 100 Contractor). They have a 20 second delay when opening certain areas of the program. Long story short (after dealing with the vendor and going through every troubleshooting step), i now suspect it may be an OpLock issue. This app is using flat DBF files, which is very likely to be affected by OpLocking. The file server is a 2012 VM, and yes, virtual machine queuing is disabled on the hosts NIC.
If i recall correctly, one cannot not disable OpLocking for SMB2, and the only solution was to disable SMB2. With server 2012, SMB3 was release. Is this still true for SMB3?
In Server 2012, Microsoft introduced new powershell cmtlet to control SMB. I could run Set-SmbServerConfiguration -EnableOplocks $false to disable OPLocking, but does that do anything if SMB2 and SMB3 are enabled? If i do disable SMB2/SMB3, is it enough to disable it on the server, or do i also need to disable on the workstation?
If i cant disable OpLocking in SMB3, but dont want to disable it, then i could disable OpLocking on all (Windows 7) clients (to stop them from requesting locks), by setting OplocksDisabled to 1 in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters. But, will this be enough to completely stop OpLocking from taking place
Thanks.
Continue reading...