FileWave Server On-Premise
For on-premise FileWave Server installs, make the server name and certificate decisions early. These settings affect how clients and MDM-enrolled devices connect to the server, so changing them later can be disruptive.
Server Name
The FileWave Server name should be a fully qualified domain name (FQDN). Prefer a name that could also work externally later, even if the first deployment is internal only. Choosing the right name up front gives you room to publish services or change network layout later without touching every enrolled device.
Certificates
The server certificate must include the chosen server name as a Subject Alternative Name (SAN). See the certificate articles for the current certificate workflow:
https://kb.filewave.com/books/certificates
After the P12 certificate is generated, upload it to the FileWave Server through the FileWave Central/FileWave Admin preferences.
Naming the Server
Enter the same FQDN on the Mobile tab. For example, for a server called demo.filewave.ch:
Server Command Line Configuration
After the certificate and server name are configured in the admin application, make sure the FileWave Server itself can resolve that name locally.
Hosts File
Edit the server's hosts file so the FileWave Server name resolves to the local server. Starting with this simple hosts file:
127.0.0.1 localhost
::1 localhost
Using the example server name demo.filewave.ch, either of these approaches is acceptable:
127.0.0.1 localhost demo.filewave.ch
::1 localhost demo.filewave.ch
or:
127.0.0.1 localhost
127.0.0.1 demo.filewave.ch
::1 localhost
::1 demo.filewave.ch
The entries can be space-separated on the same line or split onto separate lines. The goal is that a lookup for the FileWave Server FQDN from the server returns the local host.
Apache Conf File
This is only required if the server's local hostname does not match the FileWave Server name.
Edit the following file:
/usr/local/filewave/apache/conf/httpd_custom.conf
Add the following ServerName entry:
ServerName demo.filewave.ch
Restart Server Process
Restart the FileWave Server after the change. Run the command as root, or use sudo:
sudo fwcontrol server restart


No comments to display
No comments to display