SecuriSync for Windows File Servers is an application that can be installed on Windows File servers and used to:
- sync all or a subset of the File Server content to the cloud which makes it accessible from remote offices, mobile devices and easily shareable with internal and external collaborators
- migrate File Server content to SecuriSync in case you no longer require a File Server
The app is supported on:
- Windows Server OS 2008 R2, 2012, 2016
- Check here supported Windows OS
SecuriSync for File Servers can be enabled on the HostPilot® Control Panel > Services > SecuriSync > File Server Sync page. Click the Enable File Server Sync button:
Once File Server Sync is enabled, you can download the distributive file by clicking the Download button on the File Server Sync page. You can also disable the service:
Important: we strongly recommend against installing File Server Sync App in parallel with the regular SecuriSync Windows App on the same machine as this may create a conflict.
- Install File Server Sync App
- Manage mappings
- File system permissions
- Share content
- Other settings
- Known issues
To install File Server Sync App, run the distributive file and:
- Click Next in the first window:
- Accept the terms of the agreement and click Next:
- Wait until File Server Sync App is installed:
- Launch the app, enter your credentials and click Next:
To create a new mapping between any folder on the local disc and either an existing SecuriSync top-level folder or a new SecuriSync folder:
- Right-click SecuriSync icon in tray and click Settings:
- On the Mappings tab, click Add New Mapping:
- Choose a local folder
- Create a new SecuriSync folder or choose an existing one
- Click Add Mapping:
- if Choose existing folder option is selected, the folder can either be private or shared. For shared folders:
- the user account used for File Server sync has to have Modify, Co-Owner, or Owner permissions on the folder
- any existing content in the SecuriSync folder will be added to the File Server folder
- any existing content in the File Server folder will be added to the SecuriSync folder
- all sub-folders with matching names (from both sources) will be merged into one sub-folder with content both from SecuriSync and File Server. The app will recognize all files with matching names and content in source and target folders. These files will neither be synced again nor duplicated
- all files with matching names (but different content) will be saved as conflict copies according to the following rule: files from Sync will be saved with original name, and files from File Server will be renamed as Conflict copy
- if the target SecuriSync folder contains the same content as the source folder on the File Server (usually a result of adding a mapping, syncing the content, and then removing the mapping), when these folders are re-mapped, the File Server Sync app will recognize that the files and folder are the same, only new content would be synced to both the file server and the SecuriSync account
- SecuriSync File Server Sync Windows Service is independent from UI App component, which allows to sync content even if Tray client is not launched or File Server is locked
- the contents of mapped folders on File Server and SecuriSync will be synced. All subsequent changes made on either the File Server or SecuriSync will be synchronized.
- Important: If you delete content on SecuriSync, the same mapped content will be deleted on the File Server, but it will be available in the SecuriSync Recycle Bin, and can be restored to both locations.
To remove the mapping, click Remove next to the mapping name > Remove Mapping:
Note: once the mapping is removed, content will be kept both on File Server and SecuriSync but these folders wouldn't being synced anymore.
File Server Sync runs under the SYSTEM account. In order to be able to sync the contents of mapped folders, the SYSTEM account has to have Full permissions on those folders and all of their contents.
If you notice that mapped content is not syncing, it is likely due to the missing SYSTEM permission.
- File Server Sync log will show a warning such as this one:
WARN | E6BB3BC7 | 55 | LocalIndexer | Failed to index folder 'D:\Site Photos\WaterProofing'. | Access is denied.
- This issue can be fixed by adding the Full Control permission for the SYSTEM account at the top-level folder (on the File Server) and setting the permission to propagate down the folder tree. After all the permissions are set, restart the File Server Sync windows service.
Important: 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.
In order to share content, log in to the SecuriSync Web App, select the folder or file you want to sync and click Share:
In the Settings menu, you can also:
- unlink SecuriSync from computer on the Account tab:
- send diagnostic report for troubleshooting purposes on the Help tab:
Note: diagnostic logs are located in the C:\ProgramData\SecuriSync\FileServer\Service\Logs or in the C:\Documents and Settings\All Users\Application Data\SecuriSyncFileServer\Service\Logs directory.
- 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 drive and a SecuriSync folder
- There is a theoretical upper limit of 1 million files which 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
- Current mapping limitations are:
- Full volume drive cannot be set up as 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 SecuriSync side underneath the folder that is mapped with K:\Shared