Fileset Scripts Overview

FileWave can run scripts at seven stages of Fileset deployment, called activation states:

• Requirements
• Preflight
• Activation
• Postflight
• Verification
• Pre-Uninstallation
• Post-Uninstallation

In FileWave Admin, open the Filesets view, select the Fileset you want to edit, and click the Scripts toolbar icon. The Scripts dialog shows each script and the activation state where it will run.

Scripts in the same activation state run from top to bottom as shown in the list. Drag scripts to change their execution order.

Use the create or import buttons to add scripts. You can also edit a script, or drag a script from Finder into the dialog to import it.

Click OK to save changes to the Fileset. Click Cancel to discard the changes.

Double-clicking a script opens the file properties dialog. Most script attributes can be changed in the same way as files in an open Fileset, but some settings are locked because the Fileset workflow depends on them. For example, the Execute flag cannot be cleared. Requirement scripts also cannot be changed between interactive and non-interactive execution because the client must be able to use the script exit code to decide whether the Fileset should download.

The checkbox Re-run requirement scripts on change and uninstall active Fileset if they failed controls the same internal setting as Evaluate requirements on change and uninstall active Fileset if they failed in the Requirements tab of the Fileset properties. When this option is enabled and the Fileset changes, the client re-evaluates the Fileset requirements, including requirement scripts. If any requirement or requirement script fails, the Fileset is uninstalled.

Fileset script types

• Requirements Scripts – Run before the Fileset or its dependencies are downloaded. If any requirement script returns a non-zero exit code, the Fileset and its dependencies are not downloaded or installed.
• Preflight Scripts – Run after dependencies are installed, but before the Fileset downloads. If any preflight script returns a non-zero exit code, the Fileset is not downloaded or installed.
• Activation Scripts – Run when the Fileset is activated.
• Postflight Scripts – Run after the Fileset installation has completed.
• Verification Scripts – Run after postflight scripts and during each verification of the Fileset.
• Pre-Uninstallation Scripts – Run when a Fileset is inactivated, immediately before the Fileset is uninstalled. Use this state when the script needs access to files that self-healing will remove during uninstall.
• Post-Uninstallation Scripts – Run immediately after the Fileset and its dependencies have been uninstalled or removed from the client.

Related Content

• Fileset / Payload Script Exit Code Status
• Script Best Practices
• How the Client Communicates