Build Custom FileWave Client and Booster Installers

WhyWhat a custom installer contains

WhenA installingcustom FileWave Client installer includes the FileWaveconnection clientsettings ona computers,new itdevice isneeds, necessarysuch for the client to know certain information, for example,as the FileWave Server address,address. whilstIt othercan informationalso mayinclude 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 usefulbuilt tofor include: Boosters, Booster Routing, Enabling/Disabling Remote Connections, etc.Debian.

Similarly, when installing Boosters, they also require essential information including

Choose the FieWavebuilder for your Server version

FileWave Server 16.4.0 and ports.later

For this reason,Use the integrated custom installer builder in FileWave CustomCentral. Builder allows details to be enteredBuild and then for Clients download an MSI or PKG ready for provisioning devices or with Boosters there is the addition of creating a Debian custom installer.

When

Each of the installers could be used manually on devices, but the custom MSI is particularly useful when imaging Windows onto devices, whilst the custom PKG achieves the zero-touch enrolment for macOS and DEP.

Information

The FilleWave Custom Installer is available via two URLs:

https://custom.filewave.com https://custom.filewave.ch

Enter the details to match the FileWave Environment, e.g server's FQDN,required Client or Booster version,package etc.  Once completed, hitfrom the 'Build'Server buttonyou will enroll the component into.

FileWave Server 16.3.3 and FileWaveearlier

will

Use createcustom.filewave.com until the Server is upgraded to 16.4.0 or later.

When to use the packages

Use the generated package for manual installation, software deployment, or provisioning workflows. A custom installer.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. Confirm Booster routing and Remote Connections 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.