FileWave Central Setup

Connect to your FileWave Server

FileWave Central is the native administration application for macOS and Windows. This guide covers installing Central, connecting it to your FileWave Server, and committing changes with Update Model. FileWave Anywhere provides browser access for supported workflows, but some administration tasks still require Central.

Download and install FileWave Central

1. Visit FileWave's Software Downloads page here.

2. Click on the version of your FileWave Server.

3. Scroll down to either "macOS Downloads" or "Windows Downloads", under "Upgrading Your Environment".

4. Download either the "macOS Admin" or "Windows Admin", respectively.

5. Run the FileWave Admin PKG or FileWave Admin MSI and accept the licensing agreement to install.

Connect FileWave Central to the server

Open FileWave Central

• Windows: "Start Menu>FileWave>Admin"
• macOS: "/Applications/FileWave/FileWave Admin.app"
  • "Applications/FileWave/FileWave Admin (root).app" is only required for Fileset Magic.

Enter the Server Address, Username, and Password and then "Connect"

• Do not include "https://" in "Address" field
• Do not change the "Port" from "20016"

Credentials

• Hosted FileWave: the Address, Username, and Password are provided by your FileWave contact or implementation team.
• Self-managed FileWave Server: initial username fwadmin and password filewave. Change the default password immediately after the first successful connection.

Save and commit changes with Update Model

In FileWave Central, Update Model commits pending configuration changes. For example, associating a software Fileset with a Client does not immediately deploy it; the association remains pending until you choose Update Model. Review pending changes before committing so accidental associations or deletions can be corrected first.

After Update Model, the model number in the lower-right corner of FileWave Central increments. That change confirms that Central committed a new server model; it does not by itself prove that every Client has received or completed the work. Clients check in at the configured tickle interval to learn whether a newer model is available. A Client with applicable changes downloads its updated manifest and processes those changes; a Client with no applicable changes continues its normal check-in cycle. Use Client status and Fileset deployment results to verify completion on the intended devices.