Skip to content
Docs

Install FileAgent on Windows

Run the Windows installer on a server or workstation that can reach your storage systems. Installation sets up FileAgent as background services and a secure HTTPS console.

Last updated July 17, 2026

#Before you begin

  • Use a 64-bit Windows machine that stays on and can reach your sources and destinations.
  • You need Administrator rights — setup installs background services and secured runtime folders.
  • Have your license key ready if you purchased a plan (Free needs none).

#Install

  1. Download the Windows installer from fileagent.app/download.
  2. Right-click the installer and choose Run as administrator.
  3. Follow the prompts. You can accept the default secure console port or set a custom one during setup.
  4. Finish the installer. FileAgent installs its services and starts automatically.
FileAgent serves its console over HTTPS only. There is no plain-HTTP console for installed FileAgent.

#Open the console

On the FileAgent host, open your browser to:

https://localhost

If you chose a custom port, add it: https://localhost:<port>. From another administrator's machine, use the host's name or IP address — for example https://fileagent.example.com — pointed at the FileAgent server.

New installs use a self-signed certificate until you install your own, so your browser will show a certificate warning at first. That's expected — install a trusted certificate to remove it (see Certificates).

#Verify it's running

  • The console loads over HTTPS and shows the first-run setup screen (or the sign-in page).
  • In Windows Services, the FileAgent web and scheduler services show Running and start automatically.
  • After a reboot, both services come back on their own.

Next: create your administrator account.

#Common mistakes

  • Not running as administrator. Without elevation, setup can't register services. Re-run with Run as administrator.
  • Using http://. The console is HTTPS only — use https://.
  • Installing on a machine that sleeps. Scheduled jobs run from this host; pick a machine that stays on.

If setup fails or the console won't load, see installation troubleshooting.