Mass deploy the FileWave Client with Deploy Studio

Summary (this white paper is for Deploy Studio users)

The traditional methods to mass deploy FileWave Client to Mac OSX machines are to include the client in the base image or mass install the pkg from ARD. The former method is not convenient because you need to create as many images as the OS versions you want to use and it is not flexible in case you want to change the FileWave client version or configuration which are hardcoded into the image. The later method requires repetitive tasks to do the install from ARD. If you utilise Deploy Studio in your environment, you can use a Workflow to achieve the goal easily with a good flexibility.

There are two ways to integrate the Filewave Client into Deploystudio - the first method is faster if you have only one booster configuration for all clients, the second method takes more time for initial setup but lets you update the integrated filewave client with less effort and gives you more flexibility for different booster configurations. 

1. Procedure with configuration embedded into Filewave Client.pkg

For this, you need to have the FileWave Client package ready for remote deployment ->  Read this.

Now you need to create a Deploy Studio Workflow that incude two main tasks:

• restore a disk image on a machine
• install a package

1. First, copy your FileWave Client pkg to Deploy Studio repository at "/DeployStudio/Packages/" (Img.1)
2. Start your Deploy Studio Admin and browse to the WORKFLOW tab.
3. Create and name a Workflow from the little "+" button at the bottom.
4. Click the "+" next to the square labeled "Drop tasks here"
5. Drag&Drop the task "Restore a disk image"
6. If your image has one single partition check "Restore image on the first drive available" or just name the Target volume.
7. Select your image from the list and check "Automate" at the bottom (Img.2)(not checked in screenshot).
8. Drag&Drop the task "Install a package"
9. Check "Install on the last restored volume" and select the Client pkg from the list (if the pkg is not visible and it is in the Packages folder of DeployStudio, go ahead and restart Deploy Studio Admin).
10. Check "Automate" (Img.3)(not checked in screenshot).
11. Save.

Img.1

Img.2

Img.3

Your Workflow is ready, boot your client machines to Deploy Studio and select your Workflow.

2. Procedure using a script to configure fwcld

You need to create a Deploy Studio Workflow that incudes three main tasks:

• restore a disk image on a machine

• install a package

• run a custom script

Configure and Upload the files you need 

1. Copy the unmodified FileWave Client.pkg you downloaded from filewave.org to the Deploy Studio repository at "/DeployStudio/Packages/" (Img.1)

2. Copy the the attached script to the Deploy Studio repository at "/DeployStudio/Scripts/"

3. Insert your server information into the by replacing the value called this.is.my. ...  . Please make sure the " " remain around the server name. (Img. 4)

   

   Img 4.

Configure the new workflow

1. Start your Deploy Studio Admin and browse to the WORKFLOW tab.

2. Create and name a Workflow from the little "+" button at the bottom.

3. Click the "+" next to the square labeled "Drop tasks here"

4. Drag&Drop the task "Restore a disk image" into your workflow

5. If your image has one single partition check "Restore image on the first drive available" or just name the Target volume.

6. Select your image from the list and check "Automate" at the bottom (Img.2)(not checked in screenshot).

7. Drag&Drop the task "Install a package" at the end of your workflow 

8. Check "Install on the last restored volume" and select the Client pkg from the list (if the pkg is not visible and it is in the Packages folder of DeployStudio, go ahead and restart Deploy Studio Admin).

9. Check "Automate" (Img.3)(not checked in screenshot).

10. Drag&Drop the task "Run a custom script" at the end of your workflow ( Img. 5 )

11. Select the script called "configure-fwcld-plist.sh", and check "Automate" at the bottom
     

12. Specify the Parameters as follows : Booster1Name BoosterPort Booster2Name Booster2Port etc.

    

    Img 5.
     

13. Save and test the workflow