This article is a step-by-step instruction guiding you through the installation of Resilio Connect product and configuring it to sync data between the Resilio Connect Server on a Windows PC, OS X and Windows agents.
Let's assume that you need to:
- Set up a job "Updates" which will deliver a software update from Server to all other agents
- Set up a folder "Engineering documents" which will be syncing between all three (and possibly some other computers will be added to the folder later)
1. Installing Resilio Connect Server
Run the “resilio-connect-server-windows.msi” installation package and follow installation wizard. By default Resilio Connect Server is installed to "C:\Program Files\Resilio Connect Server\", it registers itself as a service and runs itself after installation. You can see the service registered and running in Windows Services:
Note that installation requires admin rights.
More on this step: installing Connect server
2. Ensure your firewall allows incoming connections to Resilio Connect Server
If you are using Windows Firewall, Resilio Management Console will take care to add itself to firewall exceptions. Although, if you are using any third party firewall, please ensure you allow incoming connections to ports used by Management ConsoleMore on this step: port used by Resilio Connect, configuring your firewall
3. Apply your server license and prepare config file for your clients
Open a browser and navigate to your server Web UI https://localhost:8443. Make sure to specify "https://" protocol explicitly as server rejects all plain HTTP connection attempts.
As the certificate is self-signed, you'll see a warning.
Ignore it for now and add the self-signed certificate to the exception list.
On first login, Connect Server will request you to specify admin login and password and agree to EULA:
After login and password, server asks for a license file.
Pick the license supplied to you by Support or Sales representative.
Once the license is applied, server lets you through to its interface. Open Settings -> General and click "Generate client config". You'll need to edit your config file before downloading.
Adjust the fields in the config:edit the server's IP address if necessary or put there server's DNS address; you can also regenerate the bootstrap token if it expired or got compromised; if necessary, edit default storage path.
Now download the sync.conf file and deliver it to all computers you are going to deploy Resilio Connect Agent to (including Connect Server itself).
4. Install your Agents and connect them to Server
- Get the MSI installer to your windows client
- Put the sync.conf file next to installer (it will get copied and used by client right after installation)
- Run installer and follow the wizard.
- Once installation is complete, you'll see your new client in the "Clients" tab on the Server
OS X Agent
- Open the “resilio-connect-agent.dmg” package
- Drag the "Resilio Connect.app" to the "Applications" folder and launch from there
- When prompted, you can either pick the sync.conf delivered from the server, or manually fill in connection details: Server's IP addres, copy-paste bootstrap token and certificate fingerprint, and change default folder path if necessary.
- Unpack the Agent package to your preferred location
- Put the sync.conf file into your preferred location
- Ensure that Agent is started up when necessary with the following arguments:
./rslagent --config <path_to_sync.conf>
You won't see any UI and if everything is done correctly, you'll see your Mac computer on the list of clients in the Connect Server Web UI.
More on this step: installing clients
5. Organizing your clients and sharing folders with them
Now you should have Connect Server running and 3 clients visible in the "Agents" tab. Agents can be organized in groups and get jobs assigned.
At the very beginning of this guide we decided to setup an "Updates" job for Server to deliver updates to everyone and "Engineering documents" to get docs shared between all clients. These two will be done with Distribution and Synchronization jobs accordingly.
Open the JOBS tab and click "Add job" -> Distribution. Give it name Updates, add description if necessary. On nest step pick the source agent - Management Server in our example.
On next step pick or create a group with destination agents, OS X and Windows agents in our example.
On step "Path" specify the path on agents. On source agent this shall be an existing path with existing files.
On step "Post commands" specify commands or scripts that need to be executed after transfer is done, if necessary. Review the job and save. See here for more details about Distribution job.
Now creating a job for Engineering documents exchange. Go back to tab JOBS -> Add job -> Synchronization. Give it name and description.
On step "RW group" pick an existing group or create a group of agent who'll have Read-Write access to the folder.
On step "RO group" pick or create a group of agent who'll have Read-Only access to the folder. This step can be skipped.
In our example all agents will have RW access.
On step "Path" specify the paths to the share on agents.
Review the job and save.
For more details about Synchronization job see here.
Now you have three groups created sharing two folders with different access level:
After a client is added to a folder, it's time to check that the folders are created in their file system, in accordance with path macros.
If you place some data into the "Updates" folder on your Server, you get it automatically distributed to your other clients. However, other clients won't upload any new/updated files to the Server and each other because they have Read-Only access there.
All clients will be uploading to each other new and updated files for the Engineering documents folder because they all have Read-write access there.
More on this step: groups, users, folders