Skip to main content

Client Monitor (16.0+)

What

Client Monitor shows live FileWave Client connectivity, status, model information, logs, and selected client settings. FileWave 16.0 introduced the current Central and Anywhere experience, using the server-mediated connection to reach supported clients across network boundaries. The current view combines connection health, model state, activity, and downloadable logs in one place, while Preferences exposes the settings an authorized administrator can modify.

FileWave 16.0 and later: The current Client Monitor does not use the legacy Client Preferences password when connecting to FileWave Clients running 16.0 or later.

When/Why

Use the Client Monitor to monitor and troubleshoot device connectivity, whether on local networks or remote environments. The enhancements in FileWave 16.0 improve:

  • NAT Compatibility – Visibility into devices across remote networks without additional configuration.

  • Security – Strengthened authentication and encryption for safer device management.

  • User Interface – A modernized layout for easier navigation and usability.

  • Troubleshooting – Detailed logs and insights for faster issue resolution.

Legacy targets: FileWave Central installations still include the standalone Client Monitor for macOS and Windows clients earlier than 16.0. It also remains the monitoring path for a FileWave IVS used for Windows Imaging in the documented 16.0 workflow.

How

The Modify Clients/Groups administrator permission controls whether Client Monitor can change client settings. Without it, an administrator can monitor the client but cannot save settings changes.

image.png

Open Client Monitor from either FileWave Central or FileWave Anywhere. In Central, use the Client Monitor toolbar button or open it from Client Info.

The current Client Monitor cannot connect to macOS or Windows clients earlier than 16.0. Use the standalone Client Monitor installed with FileWave Central for those older clients.

image.png

image.pngIn FileWave Anywhere you can select a client and then pick the "Client Monitor" button. In FileWave Anywhere you can also use the Device Actions menu when viewing a device to launch it. Both methods provide quick access to the Client Monitor. 

image.png

Client Monitor supports up to 50 devices in one monitoring session. For broader fleet checks, use inventory and reporting rather than opening simultaneous live sessions.

The Client Monitor has two main tabs—let’s take a closer look below.

Details & Logs

This tab provides real-time information about how the FileWave Client is performing on macOS or Windows devices.


One of the biggest improvements in the new Client Monitor is its use of a NATS connection, allowing you to monitor devices even if they are on a different network. This eliminates the need to manually enter an IP address and removes the limitation of only monitoring devices you can directly connect to within your local network.

 

Key features in this tab:

 

  • Last Successful Connection - Useful to determine when your monitored client last communicated with the server. Additionally, the green dot seen on the top left next to the client name indicates that the device is currently online and in contact. If the dot is red, it means the device is offline, and the dialog will reflect its disconnected status

  • Server Model Number vs. Client Model Number - Important for ensuring your client is receiving updated manifests.

  • Status - This updates live as the FileWave Client works through items that are assigned to it.

  • Logs - Displays various log files that can now be retrieved from macOS and Windows clients. The available logs differ by platform; for example, system.log and install.log are specific to macOS. Grabbing a log is as easy as clicking the download icon.

image.png
Preferences

This tab provides the client settings that the current administrator is allowed to change.

We’ve streamlined this section to make adjustments more intuitive and effective.

 

Key settings include:

 

  • Boosters - Displays only the Booster's DNS name and assumes the default port. If using a custom port, a Superpref is still the best way to configure it.

  • Debug Level - Select Normal, Debug, or Trace instead of the numeric levels used by older clients.

  • Verify, Free Space, and Heartbeat Interval - These function the same as before. The default Heartbeat (previously known as Tickle) Interval is 120 seconds and determines how often the client checks in with the server for new commands. In high-traffic environments, increasing this value could help to reduce server load. Previously called the tickle interval, rarely should it be set lower than the default.

  • Disable Personal Data Collection - Can be referenced here and can be set at the device level, but most admins configure this at the license level.

  • Location Refresh Interval - Defaults to 15 minutes and requires prerequisite setup to collect location data.

  • Enable TeamViewer Remote Control - Enables TeamViewer integration when the TeamViewer Agent is deployed to the device.

  • Prompt Client for Remote Control Access - If checked, the end user will be prompted to approve the remote session before it starts; if unchecked, the session may be started without prompting the end user.

image.png

Related Content

No comments to display

Back to top