• There is a 1TB/user limit when using File Server Sync in conjunction with the Unlimited storage package.
  • Removing the Full Control permission for the SYSTEM account for folders mapped to SecuriSync, once File Server Sync is running on a File Server, will put the application in an inconsistent state and result in undesired deletion of content
  • Mapping cannot be created between the entire local disc and a SecuriSync folder
  • Mapping cannot be created between a mapped network drive or external hard drive and a SecuriSync folder
  • There is a theoretical upper limit of 1 million files that can be synced using this app. The app will start to consume high amount of RAM for larger file sets
  • It is impossible to create Mappings between multiple source folders on File Server and one particular folder on SecuriSync
  • If a folder on File Server has an established Mapping, it is impossible to create Mappings for its child/parent folders
  • It is impossible to create a Mapping for a folder on File Server with a path longer than 256 symbols
  • If the user has Google Chrome set as the default browser, the End-user license agreement, Open source notice and Privacy policy links might not work: users see the error pop-up. This is a Chrome issue. Read the Google article for more details: https://code.google.com/p/chromium/issues/detail?id=156400
  • Current mapping limitations are:
    • Full volume drive cannot be set up as a source for mapping, for example, K:\ cannot be chosen to be synced, however, K:\Shared can be mapped with SecuriSync folder
    • Folder under the previously mapped folder cannot be chosen for new mapping. For example, K:\Shared is mapped and K:\Shared\Presentations cannot be mapped separately. This folder will appear on the $fileSync side underneath the folder that is mapped with K:\Shared