File Director provides offline access to content by keeping local copies (caches) on the endpoint, which File Director tracks and keeps in sync with the back end storage. Some users are used to working corroboratively on shared resources where desktop applications honor read-write or read-only access depending on who accesses the content first. Such local cached access requires changes to workflows and behaviors.
The File Director locking feature provides the benefits of local cached content whilst providing the native file locking experience that users may be used to when accessing content directly over SMB. The file locking feature maintains a lock on back end storage for files open on the endpoint whilst keeping the endpoint cache in sync. This file lock is not only part of the
Native SMB locking is driven by the application, with most not requesting to maintain a lock. File Director uses a whitelist approach to define which application requests to maintain a lock through File Director.
File Director file locking is not enabled by default and is activated on the Windows endpoint.
For this setting to function correctly, clients must be connected to a server that supports file locking.
|Value Name: ServerLockingEnabled
Value Type: REG_DWORD
|A non-zero value activates file locking. Activated windows clients synchronously contact the File Director server to obtain a lock where the application supports it.
When activated the default applications that request to maintain a lock are:
All File Director Windows endpoints must be activated to provide a consistent experience across the entire estate.
Was this article useful?