There are scenarios when opening a file with Office for desktop a file becomes locked for a period of time after saving.


This unfortunately can  happen because Cloud Drive Mapper uses WebDAV as it's protocol base which leverages the WebClient service built into windows 7 and above. When working with a file that was opened with WebDAV it will open this file into a temporary space located "C:\Windows\ServiceProfiles\LocalService\AppData\Local\Temp\TfsStore\Tfs_DAV" this is not a configurable path.

When using Office for Desktop, it can lock the file for a period of time as some applications do not know of the real location the file is being opened from. It can therefore leave the file in a locked state. 

Solution 1

A parameter exists in the WebClient which Cloud Drive Mapper will attempt to set.

If Cloud Drive Mapper is installed via command-line or using the "Install" feature from the menu context it will alter this default setting from 1 (enable) to 0 (disable). However if CDM is in run only mode it may not have the appropriate permissions so this setting will need to be set manually.

This can be done via GPO:

Deployment via a Group Policy

To use Group Policy to manage the Deployment of Cloud Drive Mapper, a policy and distribution method needs to be created.In the following example ‘CDM F1’ is defined as the policy and a security group name ‘CDM’ for the distribution method. Users/Computers within this group will have the policy assigned to them which contains the MSI installation as shown below.

To install Cloud Drive Mapper, apply the MSI to the following policy path:Computer Configuration > Policies > Software Settings > Software Installation (Below Is an example policy)

Once this policy has been completed ensure that user account control has been disabled for this particular policy.Disabling user account control for a policySelect Your Policy > Computer Configuration > Policies > Windows Settings > Security Settings> Local Polices > Security Option. The following policies need to be disabled to ensure there are no conflicts during the installation process.

1. User Account Control: Detect Application Installations and prompt for elevation

2. User Account Control: only elevate UIAccess applications that are installed in securelocations

3. User Account Control: Run all administrators in Admin Approval Mode

You may want to adjust the permissions/roll out method to suit your environment.

Solution 2

Go to the registry "HKLM\SYSTEM\CurrentControlSet\Services\WebClient\Parameters" and manually edit "SupportLocking" and set to 0. This will then disable locking and Office Desktop will be able to safely open the files. 

Solution 3

Auto fix this with an ELEVATED cmd line:


REG ADD "HKLM\SYSTEM\CurrentControlSet\Services\WebClient\Parameters" /v "SupportLocking" /t "Reg_Dword" /d "0" /f

If you need any assistance please contact