Executing a Client-Side Script-Based Verification

What

The "verify" option of the fwGUI client application allows you to run a "verify" from the client programmatically.

When/Why

We are going to use this option whenever we want to get "immediate" feedback from a client.  For instance, as a post-installation script, calling a verify would immediately make the client report updated inventory rather than waiting (up to 24 hours, default) for the next "regular" verify.

How

The verification is called as a command-line option to the fwGUI app on either a Windows or macOS client as follows. The first table is for FileWave 16.0.3+ and the second table is for 15.5.x and below. Please note that 16.0.1 and 16.0.2 did not have this command.

@echo off
 
"C:\Program Files\FileWave\client\kiosk\FileWaveKiosk.exe" --verify --silent
 
exit 0

#!/bin/bash
 
/usr/local/bin/FileWave.app/Contents/MacOS/FileWave\ Kiosk.app/Contents/MacOS/FileWave\ Kiosk --verify --silent
 
exit 0

On FileWave version 15.5.x or lower these are the paths and executables. This is being left here so to document that the command changed on Windows between 15.4.2 and 15.5.0 and then in 16.0.0 the old Kiosk was removed and so in 16.0.3 the verify command was brought in to the new Kiosk as mentioned above;

@echo off
 
"C:\Program Files\FileWave\client\fwGUI.exe" --verify --silent
 
exit 0

#!/bin/bash
 
/usr/local/sbin/FileWave.app/Contents/Resources/fwGUI.app/Contents/MacOS/fwGUI --verify --silent
 
exit 0

Related Content

• You can change the default 24h by adjusting the "File Check Interval" in a Superprefs - Creating a Superprefs Fileset