FileWave Server Installation & Upgrade

FileWave Server Installation

FileWave Server is the key component to device management.  The setup process will require not only a FileWave Server installation, but basic configuration will require the FileWave Central App (macOS or Windows).  Some additional configuration may also be achieved through the web admin: FileWave Anywhere.

Other appliances not covered in this chapter are:

Overall requirements

FileWave server installation.  This can be hosted or on-premise.  For on-premise, FileWave Download pages not only provide the installer, but pre-built VMs are available for quick setup.

Manual Installation

If not using a pre-built VM:

Follow the instructions, regarding the commands required, from the matching download pages.

FileWave Server networking

Please review the Default TCP and UDP Port Usage and also review FileWave Server should not have IPv6 enabled.

FileWave Access - Passwords

FileWave Administrator

FileWave installations provide an initial user which has full permissions.  On initial launch, this password should be changed as a matter of security.  The default account is:

The password may be changed in the FileWave Central software application Menus, through:

Select the 'fwadmin' account, followed by the 'Set Password' radial button.  Enter the chosen secure password


SSH is initially enabled and the root account of the default setup has the same password as fwadmin, however, they are not aligned.  Consider immediately changing the root users account password and disable the ability to access SSH to the server from the internet.

Log into a shell on the server as root and run the following command:


A prompt will require input of the new password and secondary confirmation of this new password.



FileWave Server On-Premise

Where servers are installed in on-premise environments, a couple of basic procedures should follow immediately.

Server Name

Arguably, the local server name need not necessarily matter, but the FileWave Server name is very much something to consider carefully.

When naming the server, always provide a Fully Qualified Domain Name.  This should be a name that could be used externally, even if that is not the initial plan at inception.  Subsequently changing the server name has massive impact or devices already enrolled.  Using a name that could be used at a latter date, provides future-proofing, extensively simplifying workload.


A cert will need to be generated with a Subject Alternate Name (SAN) which matches the chosen server name.  Please see our KB pages on certificates:

Once a P12 certificate is generated, it may be uploaded to the FileWave Server through the FileWave Central Application.


Naming the Server

The chosen name should be entered into the FileWave Central application's Mobile tab.  For example, for a server called '':


Server Command Line Configuration

With a certificate and name configured, there is a small amount of input required via the server's command line.

Hosts File

The server's host file should be edited to ensure the FileWave Server name is entered.  Take the following example hosts file:	localhost
::1             localhost

From the same above example '', the hosts file may edited in one of two ways.  Either:	localhost
::1             localhost

or	localhost
::1             localhost

It does not matter if the additional entry is space separated on the same line or a new line entry, either method does the same process.

Apache Conf File

This is only required if the local server name does not match the FileWave Server name.

Edit the following file: 


Add the following entry for ServerName:


Restart Server Process

After configuration change, the server process should be restarted.  This command should be ran as root.

fwcontrol server restart



FileWave Server Time

Time is critical with servers and acceptance of certificates and communication.  As such, it is imperative that time is kept in sync.  It is possible to run one-off commands to achieve this, but better still, consider enabling automated time sync.


macOS devices may just have time configured through the System Preferences or Settings


For linux servers, check out our KB on this topic:

Set date/time on Virtual Appliances


FileWave Server Upgrades

Upgrading for hosted servers will be a matter of communication between FileWave and hosted customers.  However for on-premise, consider the following process

Upgrade Process

  1. Download the chosen upgrades from the FileWave Download Pages.  This will be at the very least the FileWave Server and FileWave Central application
  2. Copy FileWave server installer to the server
  3. Copy FileWave Central installer to a chosen macOS or Windows device
  4. Lock all devices, from the right click contextual menu 'Lock' (Mobile and Computer devices can be locked separately from the relevant client View.  Multiple devices may be selected and actioned in one go.)
  5. Run an Update Model
  6. Run a backup
  7. If this is a VM, stop the FileWave Server process and take a snapshot
  8. Follow upgrade instructions from the download pages matching the installer version, including updating the server OS.
  9. Once completed, instal or upgrade FileWave Central application
  10. Connect and test a Model Update
  11. Unlock an example, test device and ensure all is well
  12. Either test further or once satisfied, unlock all other devices necessary

Before locking clients, confirm none are already locked for an alternate reason.  Once completed and unlocking, these devices may then be targeted to remain locked.