VMware Horizon Community
eblindauer
Contributor
Contributor

writable volume and cloud service seafile

Hello,

we are using on horizon 8 , with appvolume 4 (2111 - 4.5.0.77).

I've packaged an appvolume for Seadrive (http://www.seafile.com), a cloud storage , which act similar to Onedrive. This package works fine for instant clone VM. But each user must log in each time.

I've activated the writable volume (UIA+Profiles) for my users, and the Appvolume for seadrive stopped working.

The error is similar to some old errors seen on onedrive (https://communities.vmware.com/t5/App-Volumes/OneDrive-with-Files-on-Demand-and-App-Volumes/m-p/5299...) but this issue seems to be fixed since several releases!

I also tried to exclude some reg key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\SyncRootManager but without success

I have in seadrive one error related to this problem: 

[06/30/22 06:37:17] Failed to get repo id or repo path by \{ca41ccc5-8c0a-4ccf-843d-99170d288ac9}\SVROOT\Users\test.blindauer\seadrive_root\Emmanuel\Mes bibliothèques\Ma bibliothèque\devis.xlsx

 

Capture d’écran 2022-06-30 à 06.37.36.png

0 Kudos
2 Replies
kmgp
VMware Employee
VMware Employee

Hi,

You are suggesting two issues here.

  1. The seafile desktop client credentials are not retained.
  2. There is a file access error as we access the files in SeaDrive.

I  am able to reproduce the issue  2. but not 1.

A defect report is filed internally for 2.

WRT 1. as we log in with writable of UIA + Profile, did you confirm that remember credentials Checkbox is checked?

Thanks

GURU

Views expressed in here are my own.
0 Kudos
eblindauer
Contributor
Contributor

Hello,

Thanks you for the answer.

The issue 1 is only present if no writable volume is present, which is normal. When the writable is used, there is no issue for retaining the credentials.

I wait for further informations about the state of the second issue 🙂

 

Emmanuel

0 Kudos