Skip to main content

Legacy Windows Client Mass Deployment Scripts

What these legacy tools do

This page preserves two older helper scripts for converting a Windows FileWave Client installer to MSI and writing initial client preferences. Use the current Group Policy workflow linked below for new deployments; keep these scripts for environments that have already validated and depend on them.

For a current domain deployment, start with Deploying FileWave Client with Group Policy (GPO).

Download the Windows FileWave Client installer that matches the FileWave Server release. The attached conversion and preference-writer scripts are legacy artifacts; inspect and test them against the exact client installer before using them.

generatefwwinclientmsi.vbs.zip

This is an example on how you would run it:
cscript C:\path\generatefwwinclientmsi.vbs C:\path\FileWaveClient.exe

Edit the preferences script with your own FileWave Server, client password, optional Booster, port, and client-name values. Do not copy the sample credentials into a deployment.

Before:

 
Code:
set serverName=no.server.set 
set serverAddress="no.server.address" 
set clientPassword="filewave" 

set booster1="no.booster.set" 
set booster1Port="0" 

::: 

set clientName=""

After:

Code:
set serverAddress="fwserver.filewave.us" 
set clientPassword="jelly" 

set booster1IP="fwbooster.filewave.us" 
set booster1Port="20013" 

::: 

set clientName=""

Test both artifacts on a disposable Windows device. In the deployment sequence, install the MSI first and run the preferences script only after the installation succeeds.

For command-line installation, use the installer's documented silent option. Confirm the accepted arguments against the generated MSI before broad deployment rather than assuming every package uses the same switch set.

   
FWClientPrefsWriter.zip
 668 B

No comments to display

Back to top