Device Details - Booster Client Preferences Reporting

What

Use these Custom Fields when you need inventory visibility into FileWave Client Booster settings, including configured Booster connections, tickle interval, current upstream server, and whether Route server messages via boosters is enabled.

When/Why

After deploying Boosters, these fields help you confirm which clients are using them and which clients are still talking directly to the FileWave Server. They can also expose check-in timing, route-server-message state, upstream server, and memory-usage details for reporting or troubleshooting.

How

Below are the custom fields that may be imported into FileWave Central (native admin). Navigate to Assistants > Custom Fields > Edit Custom Fields… > Import and select the custom fields file to import.

FileWave Download.png

Once imported, you will see listed Client Config fields ready to be assigned to your devices.

ClientConfigs.png

After importing, highlight the Client Configuration fields you want to assign. Assigning them broadly is useful when you want a fleet-wide view of Booster use and tickle-interval settings. After selecting the desired fields, click Save.

Give the devices time to check in and acquire the new custom fields to report their data values.

As each device checks in, view these values in FileWave Client Info > Device Details. Scroll to Client Config Booster1, Booster2, and related fields to see what the client reported. The screenshot below shows an example Inventory Report (formerly Query) for routing messages, Booster upstream connections, and tickle interval.

BoosterConfigQuery.png

After the fields populate, build Reports to show which devices are connected to each Booster and which clients are still going to the FileWave Server when you expected them to use a Booster.

Digging Deeper

These custom fields report the .plist data from the FileWave Client directly so the values will be accurate unless a device has not submitted inventory. Check when it last connected to see if it has and use Verify to ask a device to check in now.


Revision #3
Created 2023-06-21 21:29:12 UTC by Josh Levitsky
Updated 2026-06-29 12:57:16 UTC by Josh Levitsky