Offboarding Clients
Use this chapter as the starting point for removing devices from FileWave management. Start with Retiring a device from FileWave to choose between archiving, deleting, wiping, uninstalling the FileWave Client, or using a platform-specific cleanup path. The sub-pages cover the managed platforms FileWave handles: macOS, Windows, Apple MDM, Android Enterprise, and ChromeOS/Chromebooks.
- Archiving Clients
- Retiring a device from FileWave
- Uninstall the FileWave Client on Windows
- Uninstall the FileWave Client on macOS
- Removing Android Devices
- Removing ChromeOS / Chromebook devices
Archiving Clients
Archive a client when you want to stop active management while keeping the device record and historical inventory in FileWave. Archived clients do not consume a FileWave license, are hidden from normal client views by default, and are removed from the active FileWave Model.
Archive is different from Delete. Delete removes the record from FileWave. Archive keeps the record as an inactive object that can be shown again or reinstated later.
What Archive does
- Removes the client from the active FileWave Model.
- Stops normal model and inventory updates for the archived record.
- Hides the client from normal views unless archived clients are shown.
- Frees the FileWave client license used by that record.
- Keeps the record available for historical review or later reinstatement.
A Model Update is required after changing client state.
Before you archive
If the device should stop communicating with FileWave permanently, remove the active management path before or during the archive workflow.
- For Windows computers, deploy the uninstall Fileset before archiving. See Uninstall the FileWave Client on Windows.
- For macOS computers, deploy the uninstall Fileset or run the standalone uninstaller before archiving if the FileWave Client should be removed. See Uninstall the FileWave Client on macOS.
- For Apple MDM-enrolled devices, review the MDM enrollment behavior below before archiving.
- For Android or ChromeOS devices, use the platform-specific removal article instead of treating the device as a normal FileWave Client. See Removing Android Devices and Removing ChromeOS / Chromebook devices.
Reinstating an archived client
Use Reinstate when a previously archived computer should return to active management. Reinstating only works if the device still has a working FileWave Client or enrollment path. If the FileWave Client was removed, reinstall the client before expecting the device to check in.
Apple MDM enrollment
When an MDM-enrolled Apple device is archived, FileWave may attempt to remove the MDM enrollment profile. Whether FileWave attempts that removal depends on the enrollment type and the setting in Preferences > Mobile.
After an MDM enrollment profile is removed, the device may no longer have a management channel to report success back to FileWave. Treat the command as a best-effort offboarding action and verify the device state separately.
For Automated Device Enrollment devices, Apple generally provides two supported ways to remove a non-removable enrollment profile: send the MDM command that removes the profile, or wipe the device. FileWave can trigger the MDM removal command through the archive workflow when the applicable setting and enrollment state allow it.
If MDM removal does not complete
If an Apple MDM profile is non-removable and the archive command did not reach the device, do not treat manual profile-file removal as a normal offboarding procedure. Wipe the device when appropriate, or contact FileWave Technical Support for guidance on the safest recovery path for that device.
If the goal is to repair a Mac that should still be managed but appears to have lost its MDM enrollment state, see Apple MDM Missing Enrolment Profile before using destructive recovery steps.
Related Content
- Retiring a device from FileWave
- Uninstall the FileWave Client on Windows
- Uninstall the FileWave Client on macOS
Retiring a device from FileWave
Use this article as the starting point when a device is leaving FileWave management, being reassigned, sold, disposed of, or preserved as an inactive record. The key rule is to remove or reset the device's management path before you delete the record from FileWave. If management is still active somewhere else, the device can check back in or be recreated by a platform sync.
If the Delete action is unavailable, confirm that you are viewing the original client record rather than a clone or grouped representation. Use Show Original from the client context menu when it is available, then remove or archive the original record after the relevant platform cleanup is complete.
If you only need to stop managing a device but keep its historical record, archive it instead of deleting it. See Archiving Clients.
Choose the right offboarding path
| Device or scenario | Primary cleanup path | Use these articles |
|---|---|---|
| macOS computer with FileWave Client | Uninstall the FileWave Client if the Mac should stop checking in. If the Mac is also MDM enrolled, remove the MDM profile or wipe the device as appropriate. | Uninstall the FileWave Client on macOS, Archiving Clients, Wipe Device for macOS |
| Windows computer with FileWave Client | Uninstall the FileWave Client while the device can still receive Filesets, then delete or archive the record after the uninstall has run. | Uninstall the FileWave Client on Windows |
| iPhone, iPad, or Apple TV | Remove MDM enrollment or wipe the device. If the device is leaving the organization and is assigned through Apple Business Manager or Apple School Manager, release it from Apple. | Archiving Clients, Apple release links below |
| Android Enterprise device | Use the Android wipe/removal path and wait for the Google synchronization state before deleting the FileWave record. | Removing Android Devices |
| ChromeOS / Chromebook | Handle the device in Google Admin Console first. FileWave syncs Chromebook records from Google Admin, so Chromebook offboarding is not a normal FileWave Client uninstall/delete workflow. | Removing ChromeOS / Chromebook devices |
| Inactive record you may need later | Archive the client instead of deleting it. Archived clients do not consume a FileWave license and are hidden from normal views. | Archiving Clients |
Before you delete a device
- Decide whether the device should be archived, wiped/reassigned, or permanently removed.
- Remove the active management path first. That might mean uninstalling the FileWave Client, removing an MDM profile, wiping the device, deprovisioning a Chromebook, or waiting for an Android/ChromeOS Google synchronization.
- If the device is leaving Apple Business Manager or Apple School Manager ownership, release it from Apple before reuse or resale.
- After the management path is removed or the wipe command has been sent, delete or archive the FileWave record and run Update Model.
- Verify the device does not return after the next check-in or platform synchronization.
Apple Business or School Manager
If devices are enrolled through Apple Business Manager or Apple School Manager and will no longer belong to the organization, release them from Apple. Releasing the device prevents future Automated Device Enrollment assignment by that organization.
After releasing a device, run the relevant FileWave Apple/DEP synchronization so the FileWave view reflects the change. If the device is not released and still has an Automated Device Enrollment profile assignment, wiping it can cause it to enroll again.
Delete from FileWave
Once enrollment, client software, or platform synchronization state has been handled, delete the record from FileWave if you no longer need the historical record.
- Open the FileWave Central Admin App.
- Select the device or devices in the Clients view.
- Right-click and choose Delete.
- Run Update Model.
If any enrollment configuration or client software remains active, the device may check back in or be recreated by a platform sync. In that case, fix the platform-specific cleanup first, then delete or archive again.
Related Content
- Archiving Clients
- Uninstall the FileWave Client on Windows
- Uninstall the FileWave Client on macOS
- Removing Android Devices
- Removing ChromeOS / Chromebook devices
Uninstall the FileWave Client on Windows
Use this Fileset when you need to uninstall the FileWave Client from Windows computers before archiving, deleting, selling, or otherwise removing those devices from FileWave management.
Deploy the uninstaller while the device can still receive Filesets. After the FileWave Client is removed, the device will no longer check in to the FileWave Server through the client.
Before you begin
- Test the uninstaller on a small pilot group before broad deployment.
- Make sure no required Filesets, scripts, or inventory actions still need to run on the device.
- Plan the follow-up state change: archive the client if you need to keep the record, or delete the record if it should be removed from FileWave.
Download
Windows-ClientUninstaller-registry-2026-07-03.fileset.zip
This updated Fileset reads the Windows uninstall registry entries and runs the FileWave Client uninstall command silently. It does not use wmic or the Win32_Product WMI class.
Directions
- Download the attached Fileset and unzip it.
- Drag the unzipped Fileset into the root level of the Filesets tab so it is not accidentally deployed from inside another folder.
- Associate the Fileset to the Windows computers that should be removed from FileWave management.
- Run a Model Update.
- Confirm the uninstall has had time to run on the targeted devices.
- Archive or delete the FileWave records as appropriate, then run another Model Update.
How the Fileset works
The Fileset uses PowerShell to inspect these uninstall registry locations:
HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\UninstallHKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall
When it finds the FileWave Client uninstall entry, it runs the matching MSI uninstall command with quiet/no-restart options. This avoids the deprecated WMIC command-line utility and avoids querying Win32_Product, which Microsoft documents as a class that can trigger Windows Installer consistency checks.
After uninstall
Once the FileWave Client is removed, the device cannot receive additional FileWave Client commands. If the record is only being kept for history, archive it. If the device should be removed from FileWave entirely, delete the record and run Update Model.
Related Content
- Retiring a device from FileWave
- Archiving Clients
- Uninstalling Filesets
- Microsoft: WMI command line (WMIC) utility deprecation
- Microsoft: Win32_Product can trigger Windows Installer reconfiguration checks
Uninstall the FileWave Client on macOS
Use these uninstallers when you need to remove the FileWave Client from macOS computers before archiving, deleting, selling, or otherwise removing those devices from FileWave management.
Remove the client while the Mac can still receive Filesets. After the FileWave Client is removed, the Mac will no longer check in to the FileWave Server through the client.
Before you begin
- Test the uninstaller on a small pilot group before broad deployment.
- Confirm whether the Mac is also MDM enrolled. Removing the FileWave Client does not remove the MDM enrollment profile.
- If the Mac should leave management entirely, handle the MDM enrollment separately. For Automated Device Enrollment devices with a non-removable MDM profile, the local FileWave Client uninstaller cannot remove that profile.
- Do not run this on a FileWave Server unless you understand what is installed on that Mac. The script is intended to remove the FileWave Client and client-side data.
Downloads
| Option | Download | Use when |
|---|---|---|
| Fileset | FileWaveUninstallermacOSv4.1.2-kiosk-process-fix-fileset.zip | You can still deploy Filesets to the Macs being removed. |
| Standalone script | FileWaveUninstallermacOSv4.1.2.sh.zip | You need to run the uninstaller locally or through another tool. |
Version 4.1.2 keeps the version 4.1 behavior for clients that no longer use FileWave VNC, corrects the FileWave Kiosk app path, and terminates the running FileWave Kiosk process before removing the app bundle.
Fileset directions
- Download the attached Fileset and unzip it.
- Drag the unzipped Fileset into the root level of the Filesets tab so it is not accidentally deployed from inside another folder.
- Associate the Fileset to the Macs that should be removed from FileWave management.
- Run a Model Update.
- Confirm the uninstall has had time to run on the targeted Macs.
- Archive or delete the FileWave records as appropriate, then run another Model Update.
Standalone script directions
- Download and unzip the standalone script.
- Run the script locally as root with
zsh:
sudo /bin/zsh ./FileWaveUninstallermacOSv4.1.2.shDo not run the script with sh. The script uses zsh process substitution. Running it with sh can produce this error:
syntax error near unexpected token `<'
done< <(pkgutil --files com.filewave.fwcld.pkg)If you see that error, run the current standalone script again using sudo /bin/zsh, not sh.
MDM enrollment note
This uninstalls the FileWave Client, but it does not remove an MDM enrollment profile. If the Mac is still MDM enrolled, FileWave may still have an MDM channel to the device, and a configured custom PKG can reinstall the FileWave Client during enrollment or later MDM-driven installation.
If the Mac is enrolled through Apple Business Manager or Apple School Manager using Automated Device Enrollment and the MDM profile is configured as non-removable, the user cannot remove that profile locally. Use one of the supported MDM/ADE offboarding paths instead:
- Send the MDM command to remove the enrollment profile while the device is powered on, online, and still enrolled. In FileWave, archiving an applicable Apple MDM device can send that removal command depending on the enrollment state and the setting in Preferences > Mobile.
- Wipe the Mac when the profile cannot be removed or when the device is being fully reset.
- If the Mac is leaving the organization, release it from Apple Business Manager or Apple School Manager. If it should remain owned by the organization but move to another MDM, change the Automated Device Enrollment assignment before wiping and re-enrolling.
Do not treat SIP-disable/manual profile-store deletion as a normal offboarding method. Use the MDM command, wipe workflow, or FileWave Technical Support for exceptional recovery cases. See Archiving Clients, Wipe Device for macOS, and Apple's device management profile removal guidance.
Uninstaller scope
The macOS uninstaller uses the FileWave Client package receipt, com.filewave.fwcld.pkg, to identify installed client components. That works best for a standard FileWave Client installation. It may not perfectly describe devices that were upgraded several times, modified manually, or changed by older upgrade Filesets. Those devices can have files or folders that are newer than the package receipt, or older files that are no longer part of the current client.
The script forgets the FileWave Client package receipt at the end of a successful run. If you run the script again after that, it may report that the package receipt is not found and exit without doing additional work.
You can check which FileWave package receipts macOS currently knows about with:
pkgutil --pkgs | awk '/com.filewave/ {print}'The client receipt is com.filewave.fwcld.pkg. FileWave Server, Booster, Admin, and other FileWave components may have their own package receipts. The uninstaller checks for some shared FileWave components before removing shared resources, but it is still a client uninstaller. Review FileWave Server or multi-role Macs carefully before using it.
If FileWave Kiosk remains visible
Version 4.1.2 removes /Applications/FileWave Kiosk.app and also attempts to terminate a running FileWave Kiosk process before removing the app bundle. If a menu bar icon remains immediately after uninstall, confirm that the device ran version 4.1.2 or newer, then log out or restart the Mac to clear any stale menu bar item that was already loaded in the user's session.
If the FileWave Kiosk app bundle or process remains after running version 4.1.2 and restarting, collect the uninstall output and contact FileWave Technical Support.
Related Content
- Retiring a device from FileWave
- Archiving Clients
- Wipe Device for macOS
- Apple: Intro to device management profiles
Removing Android Devices
Use this page when an Android Enterprise device should be wiped, reassigned, retired, or removed from FileWave. Android devices are synchronized through Google's Android Enterprise management path, so deleting the FileWave record alone is not enough if Google still considers the device managed.
Choose the right Android removal path
| Situation | Recommended path |
|---|---|
| Device is being retired, sold, disposed of, or fully reset | Send the wipe command, wait for the next Google sync/state change, then delete the device from FileWave and run Update Model. |
| Device was erased locally or disappeared before FileWave sent a wipe | Do not rely on deleting the FileWave record alone. Google may add it back during synchronization. Resolve the managed device state in Google/FileWave first, then delete it. |
| Device is being reassigned inside the organization | Wipe/reset the device as appropriate, but keep the management path active if the device should remain managed. |
Wipe and remove an Android device
- Send the Android wipe command to erase the device.
- Run Update Model if the command was sent from FileWave.
- Wait for the next Google synchronization. The device should turn red in FileWave when Google reports the changed state.
- Delete the device from FileWave.
- Run Update Model again.
If the device comes back
If the device is erased locally, the FileWave Client is removed, or the FileWave record is deleted before the Android Enterprise state is cleaned up, FileWave and Google may still consider the device managed. Deleting it from FileWave can look successful at first, but Google can add it back on the next synchronization.
Use the same cleanup path: resolve the Android Enterprise device state, send the wipe command when possible, wait for the Google synchronization state, then delete the device once FileWave shows it is ready to remove.
Related Content
Removing ChromeOS / Chromebook devices
Use this page when a Chromebook should be reassigned, retired, sold, disposed of, or removed from FileWave’s ChromeOS management view. ChromeOS devices are different from macOS, Windows, and FileWave Client devices because FileWave syncs Chromebook records from Google Admin Console.
For standard FileWave Client retirement, see Retiring a device from FileWave. For Android Enterprise devices, see Removing Android Devices.
Choose the right ChromeOS removal path
| Situation | Use this path |
| Reassign a Chromebook to another student, staff member, or loaner user | Use Wipe Users when the device should stay enrolled. Use Powerwash / Wipe Device when you need a full reset. |
| Retire, sell, dispose of, or permanently remove a Chromebook from management | Handle the device in Google Admin Console first, including deprovisioning when it will no longer be managed. FileWave syncs Chromebook records from Google Admin, so do not rely on deleting the record in FileWave alone. |
| Wipe a device but keep it managed after reset | Review Forcing wiped ChromeOS devices to re-enroll so the Google Admin enrollment setting matches your intent. |
| Stop ChromeOS management for the whole FileWave environment | Use Disable Chrome OS in FileWave. That removes the Google OAuth token and disables the ChromeOS integration for the environment. |
Remove or retire an individual Chromebook
- Decide whether the Chromebook should remain managed after the work is complete.
- If the device is being reassigned inside the organization, keep it provisioned in Google Admin Console and use Wipe Users or Powerwash as appropriate.
- If the device will no longer be managed by the organization, deprovision it in Google Admin Console. Google Admin is the source of truth for ChromeOS device management.
- Allow FileWave’s Google Admin sync to update the Chromebook record. If the device keeps returning to FileWave after you delete or reset it, check the Google Admin device state and forced re-enrollment settings.
- Update the model in FileWave after any FileWave-side action, such as sending a wipe command.
Important differences from normal client removal
- Chromebooks do not uninstall the FileWave Client like macOS or Windows devices.
- FileWave syncs Chromebook devices and groups from Google Admin Console, so the Google Admin device state controls whether the Chromebook should remain managed or return to FileWave after a sync.
- Powerwash resets the Chromebook. It does not automatically mean the device should leave management.
- Forced re-enrollment controls what happens after a wipe. If a Chromebook should not come back under management, deprovision it in Google Admin Console.