Updates to Mac and Linux are also scheduled. There is no change to the virtual drive functionality for Mac and Linux though. The only new addition is encrypted library support.
It is possible to exclude the SeaDrive cache folder in Windows search. Actually we disabled the old cached folder in SeaDrive 1.0 to avoid a confusing situation: users may accidentally open the file in the cache folder instead of the one in virtual drive when use the Windows search. But in SeaDrive 2.0, the mechanism is changed. The users should open the file in the cache folder directly. There is NO internal, user-invisible cache any more.
Excluding the cache folder from Windows search will make the files un-searchable in Windows search. This can confuse some users.
I think the “issue” you observed is a natural consequence of having too many files in the virtual drive. Even though Windows search won’t index the file contents, it still has to index the file names. This can take time and CPU. Once it’s done, it should not use too much CPU time in the future. I think having the virtual drive work smoothly with Windows search is one advantage of using the Windows native API.
I myself have about 20,000 files in the virtual drive. After the index servicing running for a while, now it never takes much CPU time anymore.
Example: When you are connected to two different servers, you do not have two nodes in your navigation. The the account selected is the one kept in sync.
Thanks @Jonathan, that is exactly why I’m looking forward to the Linux version as I was not able to use Seadrive before as all my libraries are encrypted.
Hello,
I have a little weird behavior at the Cache level.
The “Free up space” option works very well when files have been downloaded from a library on the server.
However, if I add files from my computer to a library with the help of the Seadrive reader.
10go approx. I am waiting for synchronization to be ok with the server
Then I want to use The “Free up space” option, in this specific case nothing happened.
Not a single byte was released on the disk.
I tested with smaller files (60MB) and it works. “Free up space” only works after the file is synced to the server and marked as “green tick”. Do you have a green tick status on the file? Does it work after you restart SeaDrive?
You have to use Windows 10 1709 or later. The new API is only available from that version on. I think there is a corresponding Windows server 2016 1709 update too.
All necessary pre-configure options for SeaDrive will be compatible. But some options don’t apply to SeaDrive (only make sense in sync client), so they won’t work.