Skip to main content

Build Custom FileWave Client and Booster Installers

What a custom installer contains

A custom FileWave Client installer includes the connection settings a new device needs, such as the FileWave Server address. It can also include Booster addresses, Booster routing, and the Remote Connections setting.

A custom Booster installer includes its FileWave Server address and required port settings. Available packages depend on the component and platform: Client installers use PKG or MSI, while Booster installers can also be built for Debian.

Choose the builder forby yourcomponent and Server version

FileWave Client installer

    FileWave Server 16.4.0 and later

    Use the integrated custom installer builder in FileWave Central.later:

    Build and download the requiredcustom Client or Booster packageinstaller from the integrated builder in FileWave Central on the Server youthe Client will enroll thewith. component into.

    FileWave Server 16.3.3 and earlierearlier:

    UseBuild the custom Client installer at custom.filewave.com.

    until the

    FileWave Booster installer

    For every supported FileWave Server isversion, upgradedbuild tocustom 16.4.0Booster orinstallers later.at custom.filewave.com. FileWave Central does not build custom Booster installers.

    When to use the packages

    Use the generated package for manual installation, software deployment, or provisioning workflows. A custom MSI can be included in a Windows provisioning process. A custom PKG can install the FileWave Client during macOS provisioning; Automated Device Enrollment provides the MDM enrollment path and does not itself install the FileWave Client.

    Before deployment

    • Enter the FileWave Server fully qualified domain name and the intended Client or Booster version.
    • ConfirmFor a Client installer, confirm Booster routingaddresses, Booster routing, and Remote Connections settings before building the package.
    For a Booster installer, confirm the FileWave Server address and required port settings before building the package. Install the package on a representative test device or Booster and verify check-in before wider deployment.

    Rebuild the installer when its embedded Server, routing, port, or component-version settings need to change.

    Back to top