Skip to main content

Desktop / Laptop Client Install and Configure

The FileWave Client runs on both OS X/macOS and Windows computers with the following requirements:

Operating Systems Supported

  • macOS
  • Windows 10 & 11

For specific versions look at the Downloads  page to see what is required for that version.

Downloading the FileWave client installer

The FileWave Client installer is available as part of the FileWave bundle for the specific operating system. The most current version, as well as selected older versions, of the installer are located on the FileWave KB in in Downloads. For the computers mentioned under Legacy Support, you will need to install the most recent client supported on your OS.


You should download all installers you will need for your deployment at the same time. They can be stored on a file server, or on a flash drive in Windows format for cross platform compatibility (OS X / macOS systems can read Windows-formatted drives without additional drivers).

Note: The installer instructions for the Linux server and Booster are also located on the same page of the web site. Server installation instructions are covered in FileWave Server Installation. There is no Linux client.

Installing the FileWave client

Client installers for both macOS and Windows use the same general dialogs. You will need to read and accept the license agreement, and you will be presented with a dialog window asking you for specific information to connect your client. Note: on some Windows computers, the FileWave Client Installer Assistant window is positioned directly behind the installer window, which you need to move to get to the Installer Assistant to complete the installation.

Installation Settings

  • Server address / port - Enter the IP address or FQDN of your FileWave server. Enter the TCP port number for the client to communicate with the server (default is 20015)
  • Booster address / port - If your client is going to get its Filesets from a Booster, enter the IP address or FQDN of the FileWave Booster. Enter the TCP port number for the client to communicate with the Booster (20013)

Note: More on working with FileWave Boosters in Boosters.

  • Use Computer Name for Client Name - this box allows you to use the device's computer name as its FileWave client name.
  • Client Name - enter a valid name based on any criteria you have for your deployment. It is recommended that you do not use special characters in the client name. Dashes, underscores, and slashes are ok.
  • Client Password / Confirm… - enter a password for the FileWave Admin to connect to the client. This does not need to be an administrator password that you are using for that device locally. Note: You must provide a password in order for the Remote Control/VNC relay to function.

Edit Custom Data…



The custom fields consist of a series of optional Inventory data fields that can be used to provide more detailed information on any Client. This information cannot be set in the automated installer, and must be applied manually. The information provided will be displayed as part of the Client Info in the Clients pane of the main FileWave Admin window by right-clicking on any client and selecting the Client Info… menu item, as well as in Inventory queries.

Automating installation with a custom client installer

While the manual method of running the installer and entering all of the connection information works fine for small deployments, FileWave provides you with the ability to perform larger scale installations. A customized client installer is available through the FileWave website:

For macOS: https://custom.filewave.com/py/custom_client_mac.py
For Windows: https://custom.filewave.com/py/custom_client_win.py

The customized client for macOS required for MDM/DEP support and is required to be uploaded as part of the Mobile preferences in FileWave Admin.

The form is shown on the next page.


Many fields are required.

Note that the default port is 20015. If you want SSL, do not set it to 20017. SSL is now required and entering in 20015 will result in the client using SSL.

Advanced Options


The custom installer does not ask the user for any device specific information, and can be distributed through several means:

  • Apple's Device Enrollment Program (DEP) uses the custom installer to enroll institutionally purchased devices automatically with your FileWave server (See the DEP section later in this Chapter for more details).
  • Add the custom installer to an image set when doing direct or network mass imaging (See the Imaging Chapter of this manual for more details).
  • Use a remote installation tool, such as Apple Remote Desktop, to distribute the custom installer to large numbers of existing devices.
  • Use a 3rd party imaging tool, such as DeployStudio, to build a custom client set.

Note: FileWave provides "recipes" of possible deployment workflows for the custom installer in the KB.

Back to top