Manual Trigger of FileWave Kiosk for macOS and Windows (15.3+)

What

By default, the Kiosk icon is only shown when one or more assignments between Filesets and Devices are created; set as Kiosk installation.  

It may be desirable to view the Kiosk even where Kiosk assignments do not exist, since the Kiosk also shows other details, which may be useful to the user, e.g. device information.  

The following provides information for triggering the Kiosk manually.

When

Prior to Kiosk v2, it was possible to provide a custom file to show the Kiosk icon, regardless of assignments.  Currently Kiosk v2 has no similar option.

How

For both macOS and Windows, the executable file may be targeted directly from a shell:

macOS (shell):

/usr/local/sbin/FileWave.app/Contents/MacOS/FileWave\ Kiosk.app/Contents/MacOS/FileWave\ Kiosk

Windows (PowerShell):

& "C:\Program Files\FileWave\client\kiosk\FileWaveKiosk.exe"

GUI

As a script line, this isn't the most user friendly method for users to execute and of course the obvious place to have something for users to self trigger would be in the FileWave Kiosk, but clearly that is nonsensical.  There are alternatives though.

macOS

There is already a KB on integration of the amazing 3rd party tool: 'Hello-IT'

• Hello-IT

Through this tool, it could be possible to provide users with another method to open the Kiosk, where Kiosk assignments do not exist:

By following the provided guide on Hello-IT, the small one-liner script could be added as one of the sub menu items.  When clicked, FileWave Kiosk would launch.

Windows

A similar trick could be used on Windows with another amazing 3rd party tool: 'About My Device'

• About My Device Instructions
• About My Device Repo

Although it doesn't immediately offer the option to add scripts in the way Hello-IT does, it can be hijacked to do so.  One of the features is an option to trigger a script to provide logs:

However, by editing the configuration and script files, this could be renamed and the script altered to include the PowerShell one-liner from above:

AboutMyDevice_Systray.ps1

Collect_Logs.ps1

Example

Of course, it might be desirable to keep the option to send logs, so choose the best method for adaption to suit requirements.

Additionally, there may be other 3rd party tools that could be of consideration.  Do please let other FileWavers know if other tools could be considered as appropriate or better.