Before you install
Pick the right host, confirm network access to your endpoints, and gather what you'll need so installation and your first job go smoothly.
Last updated July 17, 2026
#Choose where to run FileAgent
FileAgent installs on one host that can reach your sources and destinations over the network. Choose a machine that stays on — scheduled jobs run from this host, so a laptop that sleeps overnight will miss its windows. Teams typically place it:
- On a small Windows or Linux utility server in the data center or office network.
- On a cloud VM when most endpoints are cloud storage or internet-reachable SFTP.
- Close to the largest data source when volume is high, to keep traffic on the local network.
#What you'll need
- A supported operating system: 64-bit Windows or 64-bit Debian/Ubuntu-based Linux.
- Administrator (Windows) or root/sudo (Linux) rights on the host — installation sets up background services.
- A modern web browser to reach the console.
- Your license key if you've purchased a plan (it arrives by email after checkout). The Free plan needs no key.
- Connection details and a service account for each remote system you'll connect to.
#Confirm network access
The host needs to reach every endpoint you plan to use, plus a little outbound internet for licensing and updates:
- To your storage systems — SMB shares, FTP/SFTP servers, and outbound HTTPS to Amazon S3 / Azure Blob.
- Outbound HTTPS for license validation and update checks.
- Inbound — only your administrators need to reach the console; no inbound access from the internet is required.
Details and exact ports are in Network & permissions.
#Decide your first job
Pick one simple, low-risk transfer to start with — for example, copying a folder of reports to a test location. Starting with a Copy into an empty test destination lets you confirm the file selection before you rely on it. You can switch to Move or Sync/Mirror once you trust the result.