Before installing the FileWave server we recommend setting aside a static IP and DNS name for it. This will make it 1) easier to move the server to another IP later and 2) possible to manage off-LAN devices over the internet.
Note that the FQDN selected must be resolvable on all network segments you plan to manage the client devices from. If you want to manage devices both on and off your network then the same FQDN must be resolvable both on and off your network. Inside your LAN this DNS will resolve to the internal IP address of your FileWave server. Externally that same DNS will resolve to the public IP address of the internet router in front of the FileWave server. With mobile devices like iPhones and iPads that have a high possibility of leaving your LAN, it is essential that they be able to access the FileWave server at all times, especially when they are off-LAN.
A static IP allows you to easily forward the ports used by the FileWave server to its internal IP on your LAN, ensuring that requests from client devices are still able to reach it even when they are off-LAN. For mobile devices to be able to reach the FileWave server while they are off-LAN you must forward TCP 20443 to the internal IP of the FileWave server. A full listing of FileWave ports and traffic maps are available here.
2195 TCP/IP outgoing port used to send APNs to Apple's server (22.214.171.124/8)
5223 TCP/IP outgoing port used by IOS devices to connect to Apple's APN server (126.96.36.199/8)
5228, 5229 & 5230 TCP/IP outgoing ports, server to Google push, mobile to Google push (android.googleapis.com)
20016 TCP/IP incoming for admin-server
20445 TCP/IP incoming for admin-server HTTPS and Engage to Server
20446 Admin and browser to Dashboard (HTTPS)
20443 TCP/IP incoming for mobile-server HTTPS (Android and iOS) - Must be accessible externally & forwarded to manage mobile devices off-LAN.
Follow one of the following sets of instructions on installing the FileWave server and then configure its internal settings. You can install the the FileWave server natively on a Mac, Windows, or Linux system. Another option is to import a FileWave Server Linux virtual appliance available from the FileWave web site. For the purposes of this evaluation it is assumed that you will either be installing the FileWave server natively on macOS/Windows or importing a Linux virtual appliance. Due to the limits on how slowly the Windows version of Apache opens and releases socket connections we do not recommend installing the FileWave server natively on Windows if your device population exceeds 800 devices.
When choosing a virtualization platform for your FileWave Server virtual appliance, we recommend a server platform such as vSphere or Hyper-V over a client platform like VMware Workstation/Fusion or VirtualBox. A VM server platform does not require that you be logged into a user session for the VM to be running. Also in the event the physical system hosting the VM server restarts the VMs hosted on it can also be configured start up automatically also.
- Mac FileWave Server - Mac OS 10.12 and higher (min 4GB RAM but 8 GB recommended)
- Mac Admin Console - Mac OS 10.12 and higher
- Windows FileWave Server - Windows 2012 R2 and 2016 (min 4GB RAM but 8 GB recommended)
Windows Servers: End of Life
FileWave 13.3 will be the last FileWave release capable of running natively on the Windows Server platform. FileWave Server version 14 and beyond will only be supported on macOS and Linux platforms. FileWave Server on Windows will continue to function and be supported through the end of this year, but no new features or functions will be added after the 13.3 release. For more information, see Windows Server End of Life KB.
- Windows Admin Console - Windows 7 SP1 and 10
- Mount the FileWave_macOS_XX.X.X.dmg downloaded from the FileWave web site.
- Double click the FileWave Server.pkg or FileWave Admin.pkg installer, depending on the component, to begin the installation.
- Click Continue and then Agree to the license.
- Click Install and enter your admin credentials to complete the installation.
- Unzip the FileWave_Windows_XX.X.X zip file downloaded from the FileWave web site to a convenient location, like your desktop.
- Double click the FileWaveServer.exe or FileWaveAdmin.msi file, depending on the component, to begin the installation.
- Click Next and agree to the terms in the license agreement.
- Click Install to complete the installation.
Hyper-V Linux Appliance Import
- Extract the contents of the FileWaveServer_XX.X.X_VHD.zip file to a convenient location, like your desktop, on your Hyper-V system.
- Launch Hyper-V Manager, highlight your server on the left-hand pane, and go to Action > Import Virtual Machine.
- Click Next, then Browse, select the folder that the FileWave Server virtual appliance was extracted to (e.g. FileWaveServer_XX.X.X), and click the Select Folder button. If it reports that it can't file a VM to import follow the instructions here.
- Keep clicking Next until you reach the Choose Import Type screen. Select Copy the virtual machine (create a new unique ID).
- Continue to click Next and then Finish to complete the VM import.
- Select the FileWave server VM in the list of VMs and go to Action > Settings.
- Click Network Adapter in the list of Hardware settings for the VM and click the Virtual switch pull-down to connect it to your network.
- If there is no virtual switch available go to Action > Virtual Switch Manager to add one. For the connection type be sure to select External network.
VMware ESXi Linux Appliance Import
- Log into the VMware web console on your ESXi sever, go to Host on the left, choose Create/Register VM on the right, select Deploy a virtual machine from an OVF or OVA file, and click the Next button.
- At the Select OVF and VMDK files screen enter a display name for your VM.
- Drag the FileWaveServer_<version>.ova file into the blue field at the lower right and click Next.
VMware Fusion Linux Appliance Import
- Launch Fusion and go to File > Import > Choose File.
- Select the FileWave_Server<version>.ova file and click Open and then Continue.
- Choose the path where you would like to copy the VM to and click Save.
- Click the Customize Settings button at the Finish screen to bring up the settings screen for the VM.
- In the Network Adapter section ensure that Connect Network Adapter is checked and then select an Ethernet based option under Bridged Networking.
VMware Workstation Linux Appliance Import
- Launch VMware Workstation and click Open a Virtual Machine in the Home tab. Alternatively you can also go to File > Open.
- Browse to the FileWave_Server_<version>.ova file and click Open.
- Change the storage path for the VM if desired and click Import.
- Edit the network settings for the VM and ensure that that Connect at power on is checked and that Bridged: Connected directly to the physical network is selected.
- Click OK.
VirtualBox Linux Appliance Import
- Launch VirtualBox, go to File > Import Appliance, select the FileWave_Server_<version>.ova file, and click Open.
- Check Reinitialize the MAC address of all network cards and click Import.
- Select your the FileWave server VM and click the Settings icon in the icon bar.
- In the Adapter 1 tab ensure that Enable Network Adapter and Cable Connected are checked and that Attached to is set to Bridged Adapter.
- Click OK when you are done.
Configuring the Linux Appliance Internal Settings
Once you are done importing the FileWave Server Linux appliance, start it up to configure its internal settings.
- At the login screen note the URL to remotely manage the server, e.g. https://<ip_address>:<port>.
- If there is no IP address specified because DHCP is not available on the subnet for your FileWave Linux Appliance, login with the username "root" with password "filewave".
- Run "nmtui" at the command prompt to launch the Network Manager Text UI so you can configure the networking for the FileWave VM appliance. You'll need to reload the IP stack with "service network restart". Skip the network configuration steps later in the Webmin.