One efficient way to deploy the FileWave Client is to use ARD. This posting will outline the necessary steps to mass-deploy the FileWave Client.pkg with the proper preferences. Depending on the client version you want to deploy, please follow the steps for your version:

FileWave Client version 5.7.x and newer:


   1. Create a custom Client Package that has your server details in this form
   2. Deploy the custom client pkg with ARD.

FileWave Client version 5.6.3 and older:


What you need:
-FileWave Client.pkg (you can find this on the FileWave dmg)
-The appropriate postflight script for your version of the FileWave Client: 5.x,4.1.x, or 3.7.x.

Procedure
1. Open the FileWave Client.pkg package contents (right-click on the pkg) and look in /Contents/Resources.

2. Replace the file, postflight with the postflight script you just downloaded.

3. Open the (new) postflight script with a text editor that supports UNIX line endings (TextWrangler, BBEdit, vi, etc.) and set your preferences by editing the variables at the top of the script. Here is an example before and after code:

Before: 
Code:
#Postflight script to use with PKG installer
#enter the values for the client prefs here
#leaving fwUserName field blank will automatically use the computer name

server='enterYourServer'
serverPort=20015
desktopOwner=yourUser
password='yourPassword'
booster1='no.booster.set'
booster1Port=0


After: 
Code:
server='filewaveserver.filewave.us'
serverPort=20015
desktopOwner=student
password='5h3Lfx9'
booster1='192.168.1.13'
booster1Port=20013


4. To ensure that the postflight script executes properly, make sure to save it as a "Unix" file in your text editor. Also, it's a good idea to check the permissions on the script (via the Terminal) and change the permissions to > root:admin rwx-r-xr-x (755)
Code:
sudo chown root:admin /path/to/package/FileWave Client.pkg/Contents/Resources/postflight

sudo chmod 755 /path/to/package/FileWave Client.pkg/Contents/Resources/postflight


The fwcld package is now ready for your ARD deployment.

Notes:

The fwUser setting is left blank. This causes FileWave XClient to use the computer name as the FileWave Client name.

As Always, test things out on one or two machines before you mass-deploy.

This deployment technique is only for first-time deployments -- for upgrades, use FileWave Upgrade Filesets.

TAGS :