Executing a Client-Side Script-Based Verification
What
The --verify option requests an immediate FileWave Client verification from a script. On current clients, run it with fwcld; the legacy fwGUI commands remain below for FileWave 15.5.x and earlier.
When/Why
Use this option when a deployment or troubleshooting script needs the client to report updated inventory without waiting for the next scheduled verification, which is every 24 hours by default. The command requests verification; confirm the result in FileWave rather than treating process exit alone as proof that inventory reached the server.
How
The verification is called as a command-line option to the fwcld app on either a Windows or macOS client as follows. The first table is for FileWave 16.0.4+ and the second table is for 15.5.x and below. Please note that 16.0.0 through 16.0.3 did not have this command.
| Windows Client | macOS Client | |
| Path to FileWave Client: | "C:\Program Files\FileWave\client\" |
/usr/local/sbin/FileWave.app/Contents/MacOS/ |
| App to call: | fwcld.exe | fwcld |
| Command Line options: | --verify Sends a verification w/o user notification |
--verify Sends a verification w/o user notification |
| Script examples: | Windows Batch Example
|
macOS Bash Example
|
FileWave 16.0.4 added --verify to fwcld after the older Kiosk-based command was removed. For FileWave 15.5.x and earlier, use the legacy fwGUI paths and include --silent when verification should run without a user dialog. The Windows path changed between FileWave 15.4.2 and 15.5.0, so match the command to the installed client version.
| Windows Client | macOS Client | |
| Path to fwGUI | "C:\Program Files\FileWave\client\kiosk\" | /usr/local/sbin/FileWave.app/Contents/Resources/ |
| App to call: | fwGUI.exe | fwGUI.app |
| Command Line options: | --verify Sends a verification (w/dialog by default...useful for troubleshooting) |
--verify Sends a verification (w/dialog by default...useful for troubleshooting) |
| --silent Used with --verify, sends verification without user dialog |
--silent Used with --verify, sends verification without user dialog |
|
| Script examples: | Windows Batch Example (FW 15.5.x)
|
macOS Bash Example
|
Verify the result
- Run the command on one test client and confirm that the script exits without an executable or path error.
- In FileWave, refresh the client's inventory and confirm that the expected changed value and recent verification time are visible.
- Only then add the command to the production Fileset or troubleshooting workflow.
Related Content
- You can change the default 24h by adjusting the "File Check Interval" in a Superprefs - Creating a Superprefs Fileset
No comments to display
No comments to display