I'm posting here just in case this helps someone. My Google Drive problem was a bit different from the OP's (same error message but very different configuration). tmp.drivedownload is created, Google Drive will throw an error when attempting to synchronise a file or a folder from the online site to the local computer Unfortunately all this is broken since the introduction of Google Drive for Desktop, which replaces good ol’ Backup & Sync. tmp.drivedownload, and regularly moved to the corresponding folder, which is located in a different partition, allowing proper inheritance of ACLs as expected.
Google drive for desktop download download#
For instance mklink /d C:\drive\.tmp.drivedownload \\QNAP-TS231P\tmpDriveĭoing so, files would download to the. tmp.drivedownload folder and creating a symbolic link to a folder located on another volume did the trick.
Google drive for desktop download windows#
What I have discovered is that, in a Windows system, when files are moved across volumes, these will inherit ACLs from the target/destination folder. tmp.drivedownload, whose ACLs are set to SYSTEM and Administrator accounts, therefore the downloaded file will inherit these permissions.Īt this point the file is moved to c:\drive\mike, which is set to grant exclusive access to user Mike, BUT as the file will retain ACLs when moved into another folder on the same partition, user Mike will not be allowed to open this file!
The file otherNotes.txt is downloaded to the local computer into the folder. Once the upload is completed, Google Drive for Desktop (or Backup and Sync), which is running on the client computer, namely a Windows Server computer, will detect a change and will issue a download of the above file The file otherNotes.txt is uploaded to Google Drive into the folder My Drive > Mike See what happens when user Mike will upload a file to Google Drive using a browser: It’s easy to setup ACLs both on Windows Server and on Google Drive. In this scenario, multiple users require accessing files in a secure way, as the system must ensure that file permissions are fully respected.įor instance, we suppose that the “Mike” folder must only be accessible to user Mike.
tmp.drivedownload on the local computer, then, assuming c:\drive is the Google Drive root folder, it is moved into the folder c:\drive\MikeĪll this is perfectly reasonable, however, the issues arise as soon as the local computer which is running Google Drive is a Windows Server. Once the upload is completed, Google Drive for Desktop (or Backup and Sync), which is running on the client computer, will detect a change and will issue a download of the above file Using a browser, the file notes.txt is uploaded to Google Drive into the folder My Drive > Mike Let’s focus on the process occurring when a file or a folder is uploaded from a browser to Google Drive. Google Drive for Desktop (and Backup & Sync) uses two temporary hidden folders to synchronize files and folders, online and locally.įiles and folders which are being synchronized, are initially downloaded/moved into the above folders, then to the corresponding folder, online or locally.
0 kommentar(er)
