|Last Review||:||December 3, 2007|
Notes for Windows Vista
|•||The opportunistic locking registry keys are valid only for traditional SMB (SMB1). You cannot turn off opportunistic locking for SMB2. SMB2 was introduced in Windows Vista to enable faster communication between computer that are running Windows Vista and Windows Server 2008.|
|•||If you disable opportunistic locking, the offline files feature in Windows Vista fails.|
The location of the client registry entry for opportunistic locking has changed from the location in Microsoft Windows NT. In later versions of Windows, you can disable opportunistic locking by setting the following registry entry to 1:
Default: 0 (not disabled)
Note The OplocksDisabled entry configures Windows clients to request or not to request opportunistic locks on a remote file.
You can also deny the granting of opportunistic locks by setting the following registry entry to 0:
Default: 1 (enabled)
Note The EnableOplocks entry configures Windows-based servers to allow or to deny opportunistic locks on local files. These servers include workstations that share files.
In addition, you can use the following values to tune opportunistic locking for Windows-based computers that have granted opportunistic locks.
The following value specifies the minimum link throughput that the server allows before it disables raw and opportunistic locks for this connection:
The following value specifies the maximum time that is allowed for a link delay. If delays exceed this number, the server disables raw I/O and opportunistic locking for this connection.
The following value specifies the time that the server waits for a client to respond to an oplock break request. Smaller values allow detection of crashed clients more quickly, but might potentially cause loss of cached data.
Note You must restart the computer for these registry changes to take effect.