Skip to main content

Automated Booster Configuration for Dynamic Network Environments


There are setups where automated Booster configuration is desirable; for example devices that may move in and out of the business or between offices.  Covered here is an example method allowing clients to automatically adapt their Booster settings based upon certain criteria.


The following provides an example setup for macOS.  Similar functionality could be achieved on Windows and some ideas of this are shown also in this KB.


The Fileset contains the following items:


  • Activation Script:
  • Pre-Uninstallation Script:
  • LaunchDaemon: com.filewave.networkwatch.plist
  • Script:
  • Plist file: booster_list.plist

The Fileset will place the LaunchDaemon which is set to be triggered on load and any network change.  Where a network change has occurred, the provided script will run, reconfigure the Booster settings if required and then restart the FileWave client.  By providing an additional plist file for booster settings per domain, the file may be updated without the requirement to reload the LaunchDaemon to react to the updated settings.

LaunchDaemon Verification
The verification settings of the LaunchDaemon are set to 'Download if missing'. The script triggered by the daemon will read and write to this file, preventing unnecessary re-runs. Therefore, the file should not be changed to Self-Healing.


  • Download and import the Fileset into FileWave Admin
  • Edit the 'booster_list.plist' file to meet requirements

The example provided utilises the domain name from the device and based upon the booster plist file, the relevant dictionary of items is read into the client settings and then the client is restarted.  The LaunchDaemon script uses the 'hostname' command to achieve this.

For example, if the command returned the following:


$ hostname

The script would look in the booster_list.plist file for a dictionary called '' and configure the client to match this dictionary.  The example file has been provided with 3 dictionaries for the following domains:

  • ''
  • 'local'
  • 'home'

The example dictionary from the 'booster_list.plist' for '' is:



Edit the name of the domain, booster names and settings for each dictionary to meet requirements.  Note, if no booster is required for any of the five boosters, 'use no.booster.set' as in the above example for booster5.

If the device reports a domain that is not in the list, a default domain will be used.  Specify which default domain should be used within the 'booster_list.plist' file.  The example provided is set to use 'local' as the default domain and if implemented, the values of the 'local' dictionary keys will be read from the 'booster_list.plist' file.

Default Domain


Once all domains have been set, with relevant criteria for each dictionary, the Fileset may be associated, tested and then implemented.


Windows has a similar option to LaunchDaemons, 'Task Scheduler'.  Powershell may be used to import scheduled tasks:

As such, in theory a Scheduled task could be created based upon network event IDs

  • Log: Microsoft-Windows-NetworkProfile/Operational
  • Source: NetworkProfile
  • Event ID 10000 Connection to a network
  • Event ID 10001  Disconnection from a network

This task could trigger a script.  Once created, it may then be exported, added to a Fileset with an appropriate script to be triggered by the task, designed to update the booster configuration of the client, and installed using an Activation script by the register-scheduledtask Powershell command.


The above is an example of how boosters could be configured automatically.  Similar could be used to specify IP ranges, however it is more likely that IP ranges can overlap between networks which could cause unexpected configurations.  It may therefore be necessary to adapt the script to allow for both domain and IP ranges, depending upon network topology.

Each setup is unique and as such it is not possible to provide a Fileset that is a 'one-fit-for-all'.  Whichever method is chosen, try to identify something that will distinguish device locations to ensure settings are delivered as intended.

Incorrect Configuration
If devices receive configurations that do not match the location of the device, it may be possible that device management is lost until the mis-configuration is addressed. Thorough testing should be applied before implementation.