# 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.

<p class="callout info">For standard FileWave Client retirement, see [Retiring a device from FileWave](https://kb.filewave.com/link/239). For Android Enterprise devices, see [Removing Android Devices](https://kb.filewave.com/link/924).</p>

## Choose the right ChromeOS removal path

<table id="bkmrk-situation-use-this-p" style="border-collapse:collapse;width:100%;"><tbody><tr><td>**Situation**</td><td>**Use this path**</td></tr><tr><td>Reassign a Chromebook to another student, staff member, or loaner user</td><td>Use [Wipe Users](https://kb.filewave.com/link/834) when the device should stay enrolled. Use Powerwash / Wipe Device when you need a full reset.</td></tr><tr><td>Retire, sell, dispose of, or permanently remove a Chromebook from management</td><td>Handle the device in Google Admin Console first, including [deprovisioning](https://support.google.com/chrome/a/answer/3523633) 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.</td></tr><tr><td>Wipe a device but keep it managed after reset</td><td>Review [Forcing wiped ChromeOS devices to re-enroll](https://kb.filewave.com/link/794) so the Google Admin enrollment setting matches your intent.</td></tr><tr><td>Stop ChromeOS management for the whole FileWave environment</td><td>Use [Disable Chrome OS in FileWave](https://kb.filewave.com/link/168). That removes the Google OAuth token and disables the ChromeOS integration for the environment.</td></tr></tbody></table>

## Remove or retire an individual Chromebook

1. Decide whether the Chromebook should remain managed after the work is complete.
2. If the device is being reassigned inside the organization, keep it provisioned in Google Admin Console and use [Wipe Users](https://kb.filewave.com/link/834) or Powerwash as appropriate.
3. 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.
4. Allow FileWave’s [Google Admin sync](https://kb.filewave.com/link/849) 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.
5. 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.

## Related Content

- [Chromebook Management](https://kb.filewave.com/link/459)
- [Google Admin Sync Interval for ChromeOS](https://kb.filewave.com/link/849)
- [Powerwash / Wipe Users on ChromeOS (15.3+)](https://kb.filewave.com/link/834)
- [Forcing wiped ChromeOS devices to re-enroll (15.3+)](https://kb.filewave.com/link/794)
- [Disable Chrome OS in FileWave](https://kb.filewave.com/link/168)
- [Retiring a device from FileWave](https://kb.filewave.com/link/239)
Situation	Use this path
Reassign a Chromebook to another student, staff member, or loaner user	Use [Wipe Users](https://kb.filewave.com/link/834) 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](https://support.google.com/chrome/a/answer/3523633) 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](https://kb.filewave.com/link/794) so the Google Admin enrollment setting matches your intent.
Stop ChromeOS management for the whole FileWave environment	Use [Disable Chrome OS in FileWave](https://kb.filewave.com/link/168). That removes the Google OAuth token and disables the ChromeOS integration for the environment.