I’ve already learned how to configure the Seafile client in a Terminal Server (TS) infrastructure. The solution to assign individual ports to each user is working - but not very convenient when you have a few hundreds of users on your TS farm.
Therefore, I was hoping that the new SeaDrive solution would deal with this problem of multiple users logged in in parallel in a better way - but recently found out that the first user logged in the TS successfully sees his libs on drive S:. However, the next user also now has a S:\ and an own different drive - which is empty. Not really convincing.
Q1: is there a hack to use SeaDrive on a TS infrastructure?
Q2: are there plans to adopt SeaDrive for a TS infrastructure?