FileWave Server Setup

Choose your server route

By the end of this lesson, you will have either the details for your assigned hosted Server or a newly installed self-managed Server, so you can move on to your first connection from FileWave Central. Choose one route. Central installation, application-password security, and the final certificate and service checks follow in the next two lessons.

Your setup	Start here	Who manages the server?
FileWave hosts your server	Cloud-Hosted Server	FileWave manages the hosting; you administer devices through Central or supported Anywhere workflows.
You will use a dedicated Mac	Self-managed macOS Server	Your server and network administrators.
You will use a virtual machine	Debian Server appliance	Your virtualization, server, and network administrators.

These are new-server instructions. If your evaluation already has a working server, confirm its address and version with its owner and go to FileWave Central Setup. Do not reinstall or upgrade it just to follow this lesson.

A Booster provides optional content caching, and an Imaging Virtual Server (IVS) supports optional Windows imaging. Neither is required to connect to your Server or begin a device-enrollment evaluation.

Cloud-Hosted Server

1. Obtain the server's fully qualified domain name (FQDN), FileWave version, and application administrator credentials from your assigned FileWave systems engineer (SE) or implementation contact. An FQDN is the complete server name, such as filewave.example.com, rather than an IP address.
2. Confirm the evaluation start and expiration dates. Hosted evaluations are intended to retain your work if you purchase FileWave. Before the evaluation expires, ask your contact how your work will carry over and confirm the hosting charges and service terms.
3. Ask your network administrator to allow the connections needed from your administration computer and test-device network. The port reference separates Central, Client, and platform traffic. Internet access alone does not mean a firewall allows every required connection.
4. Keep the supplied Server name and version ready. Next, follow FileWave Central Setup to install Central and make your first connection.

Ready for Central Setup: you have the assigned Server FQDN, version, authorized access details, and a network path approved by your network administrator. Continue to FileWave Central Setup, then initial Preferences to confirm the connection and service readiness.

If any details are missing: ask your FileWave contact to confirm them. Do not try appliance passwords or repeatedly guess a password.

What FileWave hosting takes care of

FileWave manages hosted infrastructure, the standard hosted server name and certificate, backups, and Server upgrades. This reduces your setup and maintenance work. See Cloud Hosting Product Information for the service overview; pricing, availability commitments, and upgrade arrangements depend on your agreement.

Stop here if FileWave hosts your Server. Do not follow the SSH, Webmin, server installation, or server certificate and file-editing instructions in the self-managed sections below. Ask your FileWave contact to coordinate any hosted-server changes.

Before you install a self-managed server

Agree on the network and recovery plan

Work with the administrators who own your network and server. Have these details ready before installation:

• A dedicated evaluation server and an authorized administrator. Keep it separate from an existing production FileWave installation. Agree on who will maintain backups, security updates, power protection, and recovery.
• A stable IPv4 address: use a DHCP reservation tied to the appliance’s persistent virtual NIC MAC address when available. If the network owner requires a manually configured static address, have them approve it and the supported configuration method first. Record the address, subnet mask, default gateway, and approved DNS servers. The network owner must prevent address conflicts.
• One FQDN and a DNS record. Have the DNS administrator create the server's A record. Do not use an IP-only identity for enrollment: a name lets you change the server's address later without changing every device's connection settings.
• A trusted certificate for that name. The name must be included in the certificate's Subject Alternative Name (SAN). Have the certificate owner prepare a protected PKCS #12 (.p12) bundle and its password. See Name and Certificate Planning. Protect the private key and arrange renewal before expiration.
• Local or hypervisor console access. Confirm that it works before changing networking. Record existing settings and arrange a recoverable backup or a clean, pre-enrollment VM snapshot. A remote session can disconnect when an address changes; it is not your recovery method.
• Enough resources for your evaluation. Account for the OS, database, Filesets, software-update content, and backups—not only the installer download. Use Server System Requirements for general sizing and the selected release's Server compatibility table for OS support. The older OS list in the general requirements article is not the current release matrix.

Manage devices on and off your network

The same FQDN must resolve correctly from every intended device network, and devices on each network must be able to reach the Server using that name. In a typical setup, internal DNS returns the private server address; external DNS returns the public address whose firewall forwards the required device traffic to that Server. Ask the network owner to verify both paths. A successful connection from the server room does not confirm that a device outside your network can connect.

Use Default TCP and UDP Port Usage to select rules for your actual components and platforms, including their outbound services. Do not open every listed port. Keep administration access restricted to trusted networks or your approved remote-administration path; do not publish SSH or Webmin port 10000 to the internet. Central uses port 20016 for its main connection and has additional connections listed in the reference.

FileWave Server components should use IPv4 with IPv6 disabled. Current Debian appliances already handle this configuration. The macOS preparation below explains how to check the correct network service before changing it.

FileWave Server Installation

Choose a release and its matching downloads

Start at Downloads. Use the latest generally available release unless your FileWave contact has selected another supported version. Do not choose an Early Access build just because its version number is higher.

The steps below use FileWave 16.4.1:

• macOS Server: choose the Mac hardware and macOS version from the Server compatibility table on the release page. That table distinguishes QA-tested versions from other listed platforms. Do not use the Client requirements for a Server installation.
• Debian Server appliance: use the prebuilt Debian x86_64 Server image and check its release-specific requirements. Do not select the Booster or IVS image.
• Memory: the release lists an 8 GB Server minimum. General guidance recommends 16 GB; agree on CPU and storage sizing with the server owner rather than treating the minimum as a capacity recommendation.
• Virtualization: the Hyper-V image is Generation 2. Confirm that the host supports the appliance format and virtual-hardware requirements listed on the selected release page before importing it.

A server virtualization platform such as vSphere or Hyper-V lets the owner adjust resources and run the VM without a desktop user session. Configure automatic startup after the host restarts. Desktop hypervisors can be useful for a lab, but their startup and availability depend on the host configuration.

Route: Self-managed macOS Server

Follow this route on the dedicated Mac that will run FileWave Server, not on a Mac used only to administer FileWave.

1. Prepare the Mac

1. Confirm its macOS version and hardware against the release's Server table, and sign in with a local administrator account. Confirm the agreed storage and backup plan.
2. Connect the Mac to the intended server network. For a manually assigned address, open System Settings > Network, select the connection, then Details > TCP/IP. Set Configure IPv4 to Manually and enter the approved IP address, subnet mask, and router. Under DNS, add the approved DNS servers, then save the settings. See Apple's manual IP instructions if your macOS layout differs.
3. Confirm correct date, time, and time synchronization, and configure the Mac to remain available for server work rather than sleeping during the evaluation. Keep local access available while changing network or power settings.
4. Have the Mac administrator disable IPv6 on the network service used by the Server. First list the services in Terminal:

networksetup -listallnetworkservices

Use the network service name, not a device identifier such as en0. For example, only if the listed service is named Ethernet, the command is:

sudo networksetup -setv6off "Ethernet"
networksetup -getinfo "Ethernet"

Confirm that the reported IPv6 setting is off and that IPv4, router, and DNS connectivity still work. Use the actual service name in both commands. Record the original IPv6 setting before changing it; if access breaks, use local access to restore the recorded network settings and involve the network owner. Do not disable IPv4. FileWave's IPv4 guidance explains why server components use this configuration.

2. Install FileWave Server

1. On the 16.4.1 release page, find macOS Downloads and download macOS Server. For this release, the file is FileWave Server.pkg, a direct PKG download—not a DMG. Do not choose the Client, Booster, or Central package instead.
2. Open FileWave Server.pkg on the Server Mac. The installer is signed by FileWave (USA), Inc. Read its introduction/readme and license, continue through the installer, accept the license if authorized, then choose Install and authenticate with the Mac's local administrator credentials. Do not bypass a signature or security warning; stop and check the download with your FileWave contact.
3. Wait for Installer to report completion. If installation fails, retain the error and installer log for the server owner; do not repeatedly reinstall or run copied Linux installation commands.
4. Allow the Server services to finish starting. The 16.4.1 package starts them automatically, with final startup work continuing in the background. An Installer success message alone does not confirm that Central can connect. Do not run a second Server installer to try to speed this up.

3. Continue to Central Setup

Continue to FileWave Central Setup on your administration computer, then initial Preferences for Server identity and readiness checks. Skip the Debian and Webmin sections. The Mac’s local administrator account is separate from the FileWave application account.

Route: Debian Server appliance

1. Import the Server appliance

From the 16.4.1 release page, download one Server image for your hypervisor:

Hypervisor	Server download
VMware / OVA-compatible platform	FileWave_Server_Debian_16.4.1.ova
Microsoft Hyper-V, Generation 2	FileWave_Server_Debian_16.4.1_hyperv-gen-2_VHD.zip

• VMware: start the OVF/OVA deployment workflow, select the Server OVA, give the VM an evaluation name, choose its host and datastore, and map its network adapter to the approved server network. Review resources and disk provisioning with the virtualization owner, finish the import, and wait for it to complete before powering on. The VMware import reference illustrates an older vSphere interface; use it for import mechanics, not its IVS-specific closing steps.
• Hyper-V: extract the Server ZIP on the Hyper-V host. In Hyper-V Manager, select the host and choose Action > Import Virtual Machine, select the extracted VM folder, and choose Copy the virtual machine (create a new unique ID) for this new evaluation instance. Complete the import, then open the VM's Settings > Network Adapter and connect it to the approved external virtual switch. If the host cannot read the supplied VM definition, have the virtualization owner use the existing-VHDX method: create a Generation 2 VM, attach the Server disk, and apply the agreed Server resources. Do not copy IVS memory or second-NIC instructions into a Server VM.
• Confirm the VM's resource allocation, connected network, persistent MAC address if using a reservation, and automatic-start behavior. Open the hypervisor console and power on the VM. The appliance already contains FileWave Server; do not run a separate Server installer inside it.

For instructions on other lab hypervisors, see FileWave Virtual Appliances. Use an x86_64-compatible host for this Debian image; macOS Server support on Apple Silicon does not make the x86_64 appliance an ARM image.

2. Secure the appliance account and give it a stable address

Keep the hypervisor console open throughout setup.

1. At the console, sign in to the new appliance as fwadmin using the factory password filewave. Complete the required password change immediately and store the new password in your organization's approved credential manager.
2. Test a separate login with the new password before closing the original session. New Debian appliances delivered with 15.5.0 or later disable direct root login; use fwadmin and sudo for administrative work. Upgrading FileWave software on an older appliance does not change its accounts to this configuration. Follow First Login and Password Change for those distinctions and failed-login recovery.
3. Use the console's displayed address, or run the read-only command ip a, to identify the connected interface's IPv4 address and MAC address. Interface names vary; do not assume eth0, ens160, or ens32.
4. For the shortest setup, keep the appliance on DHCP and ask the network administrator to reserve the approved address for that MAC address. Confirm the DHCP service supplies the intended subnet, default gateway, and DNS servers. If the reservation changes the current address, arrange a controlled reboot from the hypervisor console after the reservation is in place. Wait for boot to finish and confirm the reserved address at the console.
5. Have the DNS administrator point the agreed FQDN's A record to that stable address. Follow the appliance DHCP reference if the appliance receives an unexpected address; another DHCP server or the wrong reservation can be responsible.

No DHCP or no address? Keep console access open. Ask the network owner to provide temporary approved DHCP access, or have the appliance administrator configure a static address using the supported method for its installed networking stack. Do not guess interface names, DNS values, or a default gateway.

The appliance account controls the operating system, SSH, and Webmin. It is separate from the FileWave application account used in Central, even if both are named fwadmin.

3. Review the appliance in Webmin

Webmin is the appliance's browser interface for operating-system settings, not FileWave Central or Anywhere.

1. On a trusted administration computer, open the Webmin address shown by the console, using HTTPS and port 10000. If the factory appliance presents a self-signed certificate warning, first match the hostname or IP to the console and confirm that you are on the intended management network. Before entering credentials, have the appliance owner verify the initial certificate or connection through an approved, independent method; an address match alone does not authenticate a self-signed certificate. This initial appliance check is not permission to ignore certificate warnings on device-enrollment services.
2. Sign in as fwadmin with the new password you just set. Do not use the factory password again, and do not change root as a substitute for securing fwadmin.
3. Open Webmin > Webmin Configuration > Operating System and Environment and confirm that the detected OS matches the installed Debian release. Do not force the old Debian 12.4 value shown in older instructions onto a Debian 13 appliance. If the detected release is wrong or unsupported by the installed Webmin, stop and ask the appliance owner to resolve it.
4. Under Hardware > System Time, check the timezone and current time. If the timezone needs correction, have the appliance owner use Change timezone and Save. Appliances normally arrive with time synchronization configured; review Time server sync, and have the appliance owner change the source only if your network requires an approved alternative.
5. Under Networking > Network Configuration, review Network Interfaces, Hostname and DNS Client, and Routing and Gateways. Check the connected interface and its address, DNS servers, and active default route against the network plan. With a working DHCP reservation, leave the interface on DHCP; you do not also need a static configuration in Webmin.
6. Confirm that you can sign out and back in with the changed appliance password. For a later password change, use Change a FileWave Appliance Password in Webmin, selecting fwadmin on new 15.5+ appliances.

You can now continue to Connect and verify your self-managed Server. If Webmin is unreachable, first check the console address and access from the management network. Do not change application credentials in Central to fix an appliance-login problem.

Optional: use a manually configured static address instead of a DHCP reservation

Use this alternative only when your network owner requires it and the appliance administrator has confirmed that the persistent interface, DNS, and routing controls described below apply to the installed Webmin version. Have the approved IP, subnet mask, DNS servers, default gateway, console access, and a recoverable pre-change backup ready. Record the original values first. Changing the address can disconnect Webmin and SSH.

In Networking > Network Configuration, configure the actual connected interface under Network Interfaces. In its boot-time settings, select Static configuration, enter the approved address and subnet mask, and save the persistent configuration. Configure the approved DNS servers under Hostname and DNS Client and the default route/interface under Routing and Gateways. Review all three before applying network changes or rebooting. Where separate Save and Save and Apply controls are available, Save stages the interface settings; Save and Apply can interrupt your current session immediately.

Have the appliance owner apply the completed configuration during the agreed window. If you use Webmin's System > Bootup and Shutdown > Reboot System, remember that it restarts the entire appliance and disconnects users. Confirm the reboot only after checking the saved configuration. Follow boot progress at the hypervisor console, then reopen Webmin at the new address. Verify the address, active default route, and DNS—not just the IP field. If access fails, use the console to restore the recorded settings or the agreed pre-change recovery point before trying again.

If your installed Webmin does not provide the persistent interface, DNS, and routing controls described here, stop and ask the appliance owner or your FileWave contact for the supported configuration method. Do not apply instructions from a different operating system.

Other network configurations

Manual command-line configuration depends on the appliance’s actual networking and resolver setup. Have the appliance owner confirm the supported method, protect the current configuration, and arrange console recovery before changing it. For a new evaluation, use the DHCP-reservation route above whenever your network allows it.

Existing appliances may retain older login and network settings. Consult their owner and First Login and Password Change rather than enabling root or assuming a software upgrade changed the operating-system accounts.

Next: connect and check readiness

Once you have completed your self-managed installation route, your Server is provisioned, but it is not yet cleared for device enrollment. Follow FileWave Central Setup to install Central, make the first connection, and secure the initial application account. Then complete initial Preferences for the name, certificate, network, and service checks.

Provisioning checkpoint: the Server is assigned or installed, its agreed name and stable address are recorded, the responsible administrators are known, and the self-managed OS account is secured. Keep passwords and private keys in the approved credential manager. Complete Central Setup and initial Preferences before preparing a device for enrollment.

If installation reports an error, keep the error and installer log for the Server owner. On macOS, allow the initial service startup to finish. On an appliance, confirm the reserved or static address at the console. Do not reimport a VM, reinstall Server, or restart shared services as a first troubleshooting step.