Deploy Linux Software with FileWave
FileWave 17.0 and later. Deploy one approved DEB application to an enrolled Linux device and verify that it works. Keep the Deployment in place while the application should remain managed; use the removal section when you need to remove it. This procedure uses a native DEB Fileset, installed through PackageKit—not the separate Linux Package APT catalog.
Complete the deployment once. If you started with Fileset Creation and Deployment, complete section 1 here, then return to step 2 there. Alternatively, finish this procedure here and use that page only as a checklist. In either case, use this page's Linux-specific verification instructions and its removal guidance when removal is needed. Do not create a second Deployment.
Before you start
- Complete Linux Client Pre-Requisites and Linux Enrollment. Use FileWave Server and Client 17.0 or later and a matching Central version. Confirm the intended Client is admitted, online and reporting recent inventory.
- Choose an administrator-approved
.debcompatible with the device's distribution, release and architecture. In this lesson,approved.debmeans your chosen installer, not a supplied download. Check its dependencies, unattended installation behavior, license and removal instructions. Avoid packages that require a restart or change networking/security for this first exercise. - Check whether the application is already installed and record its package name and version, the device identity and the current inventory baseline. Deploying the same package over an existing installation can bring it under FileWave's removal behavior; removing its assignment can remove that pre-existing application too. If you are trying an install-and-remove exercise on a pilot device, choose an application that was initially absent so the exercise does not remove software the user already had.
- Ensure the device can obtain required dependencies from its configured repositories. The Linux Client package includes PackageKit as a dependency; resolve package-management or dependency errors before continuing.
- Review other Deployments and group memberships that could install the same package. Use one known device, not a platform-wide group.
1. Create and inspect the DEB Fileset
- In FileWave Central, drag your approved
.debinto the Filesets view, or choose New Fileset > Linux > DEB and select the file. Wait for import/upload to finish. Do not deploy an incomplete upload. - Identify the new Fileset by its package name and version. Give it a recognizable test name if needed, and check that you imported the intended package rather than the FileWave Client enrollment installer.
- Open the Fileset's properties and review its Requirements. Confirm that the platform restriction includes Linux and excludes unrelated platforms. Native DEB import restricts the Fileset to Linux, but that does not establish compatibility with every Linux distribution or architecture. For this exercise, use the single device whose compatibility you checked beforehand. Do not use the inventory OS version as a Debian or Ubuntu distribution version: on Linux it reports the kernel release.
- Review the installer file's verification setting and Use uninstaller. If the application should be uninstalled when its assignment is removed, keep the installer set to Self Healing and Use uninstaller checked. New DEB Filesets created in Central 17.0 use Self Healing by default; existing Filesets retain their settings, so inspect rather than assume.
Removal behavior matters: on 17.0 Clients, Ignore At Verify (Left Behind) prevents the DEB uninstaller from running when the Fileset is removed, even if Use uninstaller is checked. Self Healing here is not a guarantee that an application removed manually will be reinstalled, or that damaged application files will be repaired.
2. Target only the test device
- Open Deployments in Central and create a Deployment with a clear name, such as
Linux: first DEB test. - Use + beside Clients to include the individual Linux device. Check the resulting target count and identity; do not select an entire group.
- Use + beside Filesets to include only the DEB Fileset you prepared.
- Expand Options and choose Direct Installation. Leave optional scheduling unset for this exercise.
- Select OK to save. Review the saved content and target before publishing. You do not need to create or convert a legacy Fileset Association.
3. Publish the model change
A Model Update publishes shared pending work, including changes from other administrators. Targeting one device does not make the update private. Review the exact device, Fileset, installation option and any other pending work with the other administrators before continuing.
- Select Update Model in Central's toolbar.
- In the Update Server Model confirmation dialog, select Update Model, or Cancel if you are not ready. This dialog does not display a pending-change preview.
- Check that the server model number changes. Keep the Linux device online while it receives and processes the work.
The model number confirms publication, not successful installation.
4. Verify FileWave status and the application
- Open the intended device's Client Info > Filesets Status and locate your DEB Fileset. Read its current state and any reported installation error. Check the available timestamps so you do not mistake an earlier result for this deployment.
- On the Linux device, independently confirm that the expected package/version is installed using its package-management information. Open the application and perform a simple, non-destructive check of its intended function.
- Record the device, Fileset, Deployment, model number, package/version and observed result. Active is FileWave's reported Fileset state, not an independent application-health test.
If installation does not complete, check the exact target, committed model, Client connection, Linux requirement, package compatibility and dependency/repository access before recreating anything. Read the Fileset error rather than repeatedly publishing the model. Verify/Refresh Inventory (Verify) can process pending device work; it is not just a screen refresh.
Deployment is complete when the intended application and version are installed and you have verified its function on the target device. Keep the Deployment in place if the application should remain managed. Removing it is a separate task, not a required final step.
Remove the application when needed
Use this procedure when the application is no longer needed on the target device and is safe to remove. Check for users or other applications that depend on it, and protect any data they need. For a disposable install-and-remove exercise, use an application that was absent before the exercise. Package removal is not a promise to erase user data, reverse every installer action, or remove every dependency.
- Recheck that the DEB installer file uses Self Healing with Use uninstaller checked. If you changed these settings after installation, save and publish that change with the shared-model review above, and let the device process it before testing removal.
- Confirm no other Deployment or applicable assignment still requires this Fileset on the device. Remove the dedicated test Deployment, leaving the Fileset available for inspection rather than deleting the package source as a substitute for cleanup.
- Review shared pending changes again, then select Update Model and confirm. Keep the device online so it can process removal. With the removable settings above, removing the Fileset's assignment causes its DEB uninstaller to run.
- Check FileWave's removal/status evidence and independently verify on the device that the test package is no longer installed. Confirm that the application is no longer available as an installed application. If it remains, check other assignments, the installer settings and package-removal errors before attempting any vendor-specific cleanup.
If you intentionally use Ignore At Verify (Left Behind), removing the Deployment leaves the package installed on a 17.0 Client. Use the package's documented removal method separately when removal is required.
If you remove the application, verify that removal achieved the intended result. Return to the shared deployment checklist without repeating the Deployment.
Alternative: the curated Linux Package catalog
New Fileset > Linux > Linux Package is a different workflow: select a package from FileWave's curated vendor APT catalog instead of uploading a .deb. The Client configures the vendor repository and signing key and installs through APT. Its Upgrade automatically at verify and Uninstall when made passive options are separate from the native DEB installer settings above. Review those options before using that route rather than applying this DEB exercise’s cleanup instructions.
No comments to display
No comments to display