Linux Client Pre-Requisites
Linux Client management is available in FileWave 17.0 and later. Prepare one Linux computer and the FileWave environment before installing the Client. This is the native FileWave Client route, not MDM enrollment or FileWave Imaging.
Choose the test device
- Use an amd64 (x86-64) device supported by the selected FileWave release. Check FileWave Clients Platform Support on that release's Software Downloads page, not the Server or Central requirements. Debian 13 amd64 is a fully QA-tested Client platform for FileWave 17.0.
- Use a backed-up device that you are authorized to manage. Have local administrator access for installing the DEB package and access to its distribution repositories so APT can obtain dependencies.
- For the FileWave Kiosk, use GNOME or KDE Plasma in a Wayland session. In FileWave 17.0, an X11 session is not supported for the Kiosk; Client inventory and logged-on user reporting can still work in X11. Do not confuse Kiosk desktop requirements with the Client's inventory capabilities.
- Record the device's hostname and another available identifier, such as its serial number or network-interface MAC address. The Client Name reported to FileWave depends on the enrollment package's naming settings and may differ from the hostname.
If the device already has a FileWave Client, check its Server and enrollment state before reinstalling. Follow Upgrading FileWave Clients for an existing Client; do not remove a working Client to repeat an initial-enrollment exercise.
Prepare FileWave
- Have FileWave Server 17.0 or later and a matching version of Central. Complete Central Setup and Central Preferences, or verify the existing setup.
- Confirm desktop-client license coverage and administrator permissions to build or download the Linux Client package and admit the device.
- Confirm the Server's FQDN, trusted certificate and reachability from the test-device network. Use Default TCP and UDP Port Usage for Client, Server and any configured Booster connections. The device also needs access to its configured Linux package repositories.
- Review automatic admission, the intended device group and existing Deployments, including broader groups and Smart Groups. Installing the Client can lead to automatic admission and assigned work. Choose a test scope whose software, policies and scripts you have reviewed; you do not need to enable automatic admission for this exercise.
You can administer a Linux Client from Central on a supported Mac, Windows or Linux workstation. You do not need to install Linux Central on the test device, move the FileWave Server to Linux, configure Apple or Google services, or set up IVS imaging for this route.
Choose how to install the Client
The enrollment lesson starts with the administrator-driven route: build or download the configured Linux Client DEB in Central > Preferences > Enrollment > Linux, transfer it to the device and install it. The package contains the intended Server settings; the device still follows that Server's admission rules. This route does not require the user to sign in to the Linux enrollment website.
For user-driven enrollment, the Server also needs an authenticated enrollment route. The user signs in at the Linux enrollment page and receives a command tied to that account. Enrollment credentials are distinct from a Central administrator login. Have the Server administrator prepare the authentication route before choosing this option; do not disable a working policy or change hosted-server files yourself.
Early Access: if your environment uses a Beta build, arrange the matching package channel before building the Client. Enable Early Access (Beta) Package URLs covers the server-side prerequisite; FileWave Operations handles it for hosted environments.
Ready to enroll: the device is supported and identifiable, the Server is reachable, license and administrator access are confirmed, and you know what work can apply when it is admitted.
Next: follow Linux Enrollment to install the configured Client, admit the device and verify its first inventory.
No comments to display
No comments to display