# 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:
**Windows Client** | **macOS Client** | |
**Path to fwGUI:** | "C:\\Program Files (x86)\\FileWave" | /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** ```powershell @echo off "C:\Program Files (x86)\FileWave\fwGUI.exe" --verify --silent exit 0 ``` | **macOS Bash Example** ```shell #!/bin/bash /usr/local/sbin/FileWave.app/Contents/Resources/fwGUI.app/Contents/MacOS/fwGUI --verify --silent exit 0 ``` |