Before the FileWave client reboots a computer, where the Fileset properties are set to reboot, a warning can be expected to 'Quit All Running Processes' with a list for the user to address.
Although this warning is usual, there are instances where certain apps or processes can appear in the queue that are unexpected, for example:
As a service, this can show even though the user is not using Adobe Apps at the time.
Requirements to prevent this experience are:
- Customised Kiosk Fileset
- Bundle ID of the App or Service to exclude
A settings file may be configured to allow for certain apps. Please see Client Kiosk Customization, for details regarding location of the settings file: 'settings.ini'
To exclude an unexpected process from being listed and preventing the reboot, first obtain the Bundle ID of the listed App or Service. If unsure how to obtain this, it may be retrieved from FileWave logs
Obtain Bundle ID
- Change a test device's Debug Level to 99 through the Client Monitor
- Send any Fileset that has its Fileset Properties set to 'Requires Reboot' to the test machine
Once device prompts to quit applications, open the the FWGUI.log found in the users Application Support directory. There should be a lines similar to the following, for each process that has prevented the reboot:
The 'settings.ini' file should be configured with the following format (Bundle IDs being a comma separated list):
For the example of Adobe Desktop Service, it should read:
Deploy the 'settings.ini' file as set out in the Client Kiosk Customization