Skip to main content

Managing Client States via the FileWave API

What

This article explains how to manage client device states in FileWave, specifically focusing on how to archive and reinstate clients using the FileWave API. The client state can be defined as Tracked, Archived, Missing, or Untracked, each represented by a numerical value.

When/Why

Changing the state of a client may be necessary during device management tasks such as inventory control, security audits, or when a device is no longer in active use but needs to be retained in the system for record-keeping. Archiving clients helps in decluttering the active management list without permanently deleting the device record, allowing for easy reinstatement if needed.

How

To change the state of a device, you can use the FileWave API to send a PATCH request that updates the device state. Below is an optimized script using zsh to change the state of a device and ensure the model is updated to reflect this change:

 

Tips:

  • Ensure that the Token variable contains a valid authorization token.
  • Replace DeviceID and NewState with the appropriate values according to your needs.

Related Links

Digging Deeper

Understanding the model update process is crucial for ensuring that changes made via the API are reflected in the FileWave management interface. The update_model API call triggers the FileWave server to reprocess its internal data models, ensuring that any state changes are accurately shown in the admin console. This is especially important after bulk changes to device states to maintain consistency across the system.

Please replace placeholders like your_token_here with actual data as needed. If there are any more specific features or details you want included, just let me know!

Back to top