We have several RDS environment (plain RDS or Citrix XenApp) where we would like to integrate Syncplicity. The users can end-up on different servers after each logoff/logon sequence and thus have to reconfigure en resync all files in that case.
The major problem occurs when a users syncs a folder to an RDS server and then at next logon ends up on another server. The folder there does not exist, so it just stops syncing that folder. Any way to modify that behaviour? We use local storage on each RDS server for syncplicity syncing as fileshares (which would solve this problem) are not supported.
Any tips?
Syncplicity supported platforms are listed here:
https://syncplicity.zendesk.com/hc/en-us/articles/201569954-Supported-platforms
Any virtualized desktop must be persistent, in file storage and in all user configuration and settings. The user's complete environment must be preserved between sessions, and all storage accessed by the client must be local, or simulated at the filesystem as if local.
Please sign in to leave a comment.
Fair enough. Thank you for your answer.
On a related note (in a way to make it easier for our users in said scenario): can we change the behaviour of Syncplicity where it stops synchronising a folder when it cannot find its location. I would rather have it re-sync it in that case instead of stopping the sync altogether.