Kiosk

Self-Service Kiosk Overview

FileWave supports two methods of distributing content. The first is direct interaction from the FileWave Admin(s) where applications and other content are associated with devices or Groups of devices as part of a centrally managed deployment scheme. The second method is by using the self-service Kiosk and allowing the end user to choose the items to be installed on their device. Because the FileWave processes run at root level, the end user does not need to be a local administrator in order to install applications and content through the Kiosk.

The Kiosk is activated on computers by installing the FileWave client and having at least one Fileset configured as a Kiosk item associated with that Client. The Kiosk is activated on a mobile device when that device enrolls with the FileWave MDM.

Filesets can be configured as Kiosk items in FileWave Admin and can be added to unique categories, such as a specific department or class, or just by application type. You can even create a Kiosk Fileset of an iOS application from the App Store. The user gets the link to the store and the application or book would be downloaded from Apple when they request it. Kiosk items can be managed using Apple's VPP Managed Distribution model so that assigned applications can be installed by a user; but returned to the FileWave Admin for re-use at a later date.

Mobile Kiosk versus Desktop Kiosk

FileWave Kiosk for macOS and Windows overview (15.3+)

This article will explain the details of the refreshed Kiosk for macOS and Windows that is included in FileWave 15.3+.

Browse Payloads/Filesets

The "Browse Payloads/Filesets" screen is a central feature within the app that enables users to explore and discover a diverse array of payloads/filesets available for access or download. Much like the experience of browsing through the Android Play Store or the Apple App Store, this screen offers users an organized and visually appealing interface that showcases different payloads/filesets, each accompanied by relevant details and information.

Key components and elements commonly found on the "Browse Payloads/Filesets" screen include:

image.png

image.png

image.png

These enhancements not only simplify the user experience but also provide a comprehensive set of tools for effective payload/fileset management. By incorporating these features, we aim to empower users with a more personalized and efficient approach to navigating and managing their payloads/filesets within FileWave.

image.png

image.png

image.png

Payload/Fileset details view

We are excited to introduce significant enhancements to the Desktop Kiosk versions, mirroring the user-centric improvements made for iOS/iPadOS. With these updates, users can expect a more intuitive and informative experience when interacting with filesets and payloads on their desktop devices.

Key Features:

image.png

These enhancements aim to streamline the desktop browsing experience, aligning it closely with the intuitive interface seen on iOS/iPadOS. By providing users with comprehensive information and intuitive navigation, the Desktop Kiosk versions empower users to make informed decisions and maximize productivity.

Device Information view

We're thrilled to unveil enhancements to the Device Information view on Desktop Kiosk, paralleling the user-centric improvements made for iOS/iPadOS. This revamped interface provides users with a comprehensive overview of vital device details, fostering transparency and effective management within the app's ecosystem.

Key Features:

These enhancements bolster transparency and facilitate efficient device management within the Desktop Kiosk environment. By providing users with a holistic overview of device and server information, coupled with booster management capabilities, the Desktop Kiosk version empowers users to make informed decisions and optimize their workflows with ease.

image.png

Logo and primary color selection

The Adding Logo and Primary Color Selection feature enhances customization within the app by enabling users to personalize the visual representation of their profiles or entities. This feature allows users to define their brand identity and establish a cohesive look and feel throughout the app. Here's how the feature works:

The "Add Logo and Primary Color Selection" feature empowers users to infuse their identity into the app's interface, enhancing recognition, and contributing to a personalized and engaging experience for both users and their audiences.

FileWave Kiosk for iOS/iPadOS overview (15.3+)

What

The Self-Service Kiosk is how you can offer an easy way for your users to install approved software without the need for IT to specifically assign it to a iPad or iPhone. Instead, you can assign a collection of approved applications to your devices, and then your users can pick from that collection whatever apps they need. The FileWave App Portal is getting a major overhaul starting with FileWave Version 15.3. You'll automatically see this new Kiosk pushed out to your iPhones and iPads when you upgrade to any version of FileWave from 15.3 or higher as discussed in: Automatic updating of iOS/iPadOS Kiosk (15.3+)

When/Why

The transition from Technical Preview version 15.1 to the Production version 15.3 of our app signifies a major leap forward in terms of user experience and visual appeal, much like the transformation seen when comparing the Android Play Store and the App Store. In this upgrade, the primary focus has been on completely revamping the user interface (UI) to provide a sleek, modern, and highly intuitive platform that caters to our users' evolving expectations.

With version 15.3.1, the app undergoes a stunning visual makeover, drawing inspiration from the aesthetic excellence of both the Android Play Store and the App Store:

  1. Unified Design Paradigm: Our new UI design unifies elements from both the Android Play Store and the App Store, creating a harmonious blend of familiarity and innovation. This design consistency ensures that users across various platforms feel comfortable while navigating the app.

  2. Intuitive Navigation: Introduces a reimagined navigation system. Users can effortlessly explore and discover content thanks to intuitive menus, recognizable icons, and seamless navigation flows, akin to the ease of navigation in both app marketplaces.

  3. Visual Delight: The new UI is not just about functionality; it's a visual treat. Engaging animations, subtle transitions, and tastefully curated visuals combine to make every interaction with the app a delightful experience, echoing the immersive nature of the Android Play Store and the App Store.

  4. Enhanced Customization: Introduces enhanced customization options, allowing users to personalize their interface just as they would within the Android Play Store and the App Store. Users can arrange and prioritize content according to their preferences, granting them a sense of ownership over their app experience.

  5. Responsive Design: Much like the Android Play Store and the App Store's responsiveness across devices, our app now adapts seamlessly to various screen sizes and orientations. This ensures a consistent and optimized experience whether users are browsing on smartphones, tablets, or desktops.

By transitioning to the 15.3 release of the Kiosk, with a UI overhaul reminiscent of the Android Play Store and the App Store, our app solidifies its commitment to delivering an unparalleled user experience. This transformation isn't just about aesthetics; it's a testament to our dedication to meeting the evolving needs of our users in an engaging, intuitive, and visually striking manner. As we bridge the gap between the old and the new, version 15.3 sets the stage for a future where our app continues to evolve in tandem with user expectations and industry trends.

How

Browse Payloads/Filesets

The "Browse Payloads/Filesets" screen is a central feature within the app that enables users to explore and discover a diverse array of Payloads/Filesets available for access or download. Much like the experience of browsing through the Android Play Store or the Apple App Store, this screen offers users an organized and visually appealing interface that showcases different Payloads/Filesets, each accompanied by relevant details and information.

Key components and elements commonly found on the "Browse Payloads/Filesets" screen include:

iPhone iPad
image.png

image.png

iPhone iPad

image.png

image.png

The "Browse Payloads/Filesets" screen serves as a gateway for users to immerse themselves in the app's content ecosystem, allowing them to discover and access various Payloads/Filesets that align with their needs and interests. Its design, layout, and functionality play a crucial role in delivering a user-friendly and enjoyable browsing experience, reminiscent of the fluid exploration on the Android Play Store and the Apple App Store.

Payload/Fileset details view

The "Details View" is the screen that users encounter after clicking on a specific Payload/Fileset they wish to install or access. This screen provides comprehensive information about the selected Fileset, offering a deeper understanding of its features, functionality, and relevance. Much like the detailed view of an app in the Android Play Store or the Apple App Store, this interface is designed to empower users to make informed decisions about their installation or usage.

Key elements and components often present on the "Details View" include:

iPhone iPad

image.png

image.png

The "Details View" enriches the user's decision-making process by providing an in-depth look into the selected Fileset's attributes. By offering clear explanations, visuals, and relevant information, this interface ensures that users can confidently proceed with the installation or access of the chosen Fileset, enhancing their overall app experience.

Device Information view

The "Device Information" page provides a comprehensive overview of essential details about a specific device, enhancing transparency and management within the app's ecosystem. This page showcases crucial information related to the device and its integration, allowing users to make informed decisions and take necessary actions. The following information is displayed:

iPhone iPad

image.png

image.png

The "Device Information" page serves as a valuable tool for users to gain insights into the device's ownership, enrollment history, status, and app-related details. By presenting this information in a user-friendly manner, the page enhances user management and facilitates seamless interactions within the app's ecosystem.

Logo and primary color selection

The Adding Logo and Primary Color Selection feature enhances customization within the app by enabling users to personalize the visual representation of their profiles or entities. This feature allows users to define their brand identity and establish a cohesive look and feel throughout the app. Here's how the feature works:

The "Add Logo and Primary Color Selection" feature empowers users to infuse their identity into the app's interface, enhancing recognition, and contributing to a personalized and engaging experience for both users and their audiences.

image.png

image.png

How do I change the logo and primary color? It's easy if you follow this guide: Setting the Primary Color, Name and Logo in Kiosk/App Portal (15.3+) but if you are a Hosted customer, you will need Customer Technical Support to help you because you'll need to change files on the server itself.

App Portal / Kiosk v2 transition (15.3+)

Evolution of App Portal for iOS/iPadOS: Transition from Technical Preview to Official Release

In our commitment to continuous improvement and user-centric development, we are excited to announce a significant milestone in the journey of App Portal for iOS/iPadOS. Starting from version 15.3.0, App Portal has officially graduated from its technical preview phase, now standing as a fully realized and polished application.

Key Points:

  1. From Technical Preview to Real App:
    In previous releases, App Portal for iOS/iPadOS was introduced as a technical preview, allowing users to explore its functionalities and provide valuable feedback. With version 15.3.0, we are thrilled to elevate App Portal to the status of a fully-fledged, official application.

  2. Enhancements and Stability:
    The transition signifies not only the culmination of user feedback but also substantial enhancements and optimizations to ensure the stability, reliability, and performance of the App Portal for iOS/iPadOS.

  3. A Seamless User Experience:
    Users can now enjoy a seamless and refined experience with App Portal, harnessing its full potential for efficient and intuitive mobile application management.5.3.0 and beyond.

Desktop Kiosk for macOS and Windows

The transition from App Portal version 15.0.0 to version 15.3.0 represents a significant evolution, akin to the transformative experience observed when comparing the Android Play Store and the App Store. This upgrade places a primary emphasis on completely overhauling the user interface (UI) to provide a sleek, contemporary, and exceptionally intuitive platform, aligns with our users' evolving expectations.

While version 15.0.0 laid the groundwork for functionality, version 15.3.0 responds to user feedback and industry trends, recognizing the demand for a more sophisticated and streamlined UI. Here's how the new version draws inspiration from the design excellence of both the Android Play Store and the App Store:

  1. Unified Design Paradigm:
    The UI design seamlessly unifies elements from both the Android Play Store and the App Store, creating a harmonious blend of familiarity and innovation.

  2. Intuitive Navigation:
    Building on the success of version 15.0.0, version 15.3.0 introduces a reimagined navigation system with intuitive menus, recognizable icons, and seamless flows, akin to the ease of navigation in both app marketplaces.

  3. Visual Delight:
    The new UI isn't just functional; it's a visual delight with engaging animations, subtle transitions, and tastefully curated visuals, providing an immersive experience similar to the Android Play Store and the App Store.

  4. Enhanced Customization:
    Version 15.3.0 brings enhanced customization options, allowing users to personalize their interface similar to the Android Play Store and the App Store, fostering a sense of ownership over their app experience.

  5. Responsive Design:
    Like the responsiveness of the Android Play Store and the App Store across devices, our app now adapts seamlessly to various screen sizes, ensuring a consistent and optimized experience.

Additionally, with version 15.3.0, we've introduced some enhancements. Users will now receive clear indications when installing certain filesets that a reboot is required for optimal performance. This improvement ensures transparency and empowers users with the necessary information for a seamless experience. By incorporating these enhancements, App Portal solidifies its commitment to delivering a cutting-edge, user-friendly experience that aligns with evolving user expectations and industry trends. Version 15.3.0 sets the stage for a future where App Portal evolves dynamically, staying at the forefront of user-centric innovation.

Please note that there are some pre-15.3 customizations that no longer have any effect as well as one customization that can result in seeing both the old and new Kiosk on a macOS or Windows system. Please review the related content below.

FileWave App Portal for iOS (IPA Install)

For FileWave 15.3.0+ please note that the IPA is automatically deployed. Once 15.3.0 is released please see: Automatic updating of iOS/iPadOS Kiosk (15.3+)

Once an iOS/iPadOS device is enrolled, the FileWave App Portal will be automatically installed.  The version installed after enrollment is a Web Based Application, allowing users to self-install associated Applications, Profiles, and Books or trigger a Verify.

FileWave offers an Enterprise version of the App Portal, which is available from the FileWave Download pages (there should be a version to match the server release).  The Enterprise version additionally offers:

Location Tracking relies upon the user accepting both Location Tracking and allowing the FileWave App Portal access to the location data.  If users do not accept these, no Location Data will be received.  These are limitations imposed by Apple.

The IPA is signed for a year on creation.  The signature is renewed by FileWave for versions that are still supported.  It is therefore necessary to re-download the Enterprise version and redistribute it, prior to or at the time of expiry, for the App to continue to function.  The Web App version has no such consideration.

Installing the Enterprise FileWave App Portal

Requirements

Creating the Enterprise FileWave App Portal Fileset

From the FileWave Admin application, navigate to:

Two options are available:

ipa.png

Local File

The IPA may be downloaded from the FileWave downloads page.  Select the IPA version to match the FileWave Server version.

ios-downloads.png

From the Fileset creation window, browse to the location of the downloaded file, choose 'Import' and then 'Done'

Remote File

The file may be placed in a remote location.  This could be either a chosen server or directly from the FileWave Download site.

ipa-remotefile.png

Remote Server

If using a chosen server, download the IPA as above, import it into the chosen server, and add the URL path to the Fileset.

FileWave Download Site

If using the FileWave Download site, use the provided static path from the Downloads page as the URL

It is also possible to tick the box to 'Use FileWave MDM server to host the file'.  This is essentially the same as the local process.  FileWave will then pull the IPA from the download to create a local file for distribution from the FileWave Server.

Remote vs Local Considerations

Local

The FileWave server is used to host the IPA, the IPA is directly stored on the FileWave Server and delivered from the FileWave Server to devices.  

This option has the following considerations:

Remote

The FileWave Server does not store the IPA, but instead sends the device details of where to pull the IPA.  

Considerations in this instance are:

Deploying the Enterprise FileWave App Portal Fileset

Deployment of the IPA is as simple as creating an association, either directly or via a group.  On receipt of the IPA Fileset, the device will automatically remove the Web App Portal and it will be replaced with the IPA version.  Similarly, if providing an updated version, the new version may be associated and the old association removed.

User Experience

It should be expected the user will receive the following prompts, due to TeamViewer integration:

ipa-tvprompt1.pngipa-tvprompt2.png

They should also expect to receive the following due to Location Tracking:

ipa-locationprompt.png

Additionally, they should be prompted regarding the ability to continue Location Tracking when the App is not in use:

ipa-locationprompt2.png

Location Tracking also relies upon the device being configured as such, as highlighted in the KB: Location Tracking

App Portal IPA Removal

If it is chosen that the IPA is no longer a requirement, removal of the association for the IPA will not only remove the IPA but the Web App version will once again be automatically deployed to devices.

IPA Expiry

If the installed App Portal IPA is allowed to expire, the App will fail to launch and the users will be prompted:

ipa-expired.png

Deploying a newly downloaded IPA to devices should address this.

Automatic updating of iOS/iPadOS Kiosk (15.3+)

What

The New App Portal in FileWave 15.3.0 represents a significant upgrade designed to enhance the management and distribution of apps across iOS/iPadOS devices. This feature aims to simplify app deployment, allowing for a more streamlined and efficient process for administrators and end-users alike. By automatically installing the New App Portal on managed devices, FileWave ensures that users have access to the latest and most relevant applications required for their tasks, without the need for manual updates or installations.

When/Why

In order to simplify and ensure that the Kiosk is always current we have implemented a feature that will automatically handle the updates to the Kiosk so that you no longer need to worry about the .IPA on iOS or iPadOS.

How

FileWave Kiosk displays Company Information

Description

As an enhancement to the FileWave Kiosk / App Portal on macOS, Windows, and iPadOS/iOS, version 15.4 includes a view for Organisation Information.

Information

Details for the organisation may be filled out in the Preferences tab of FileWave Central for Organisation Info.  These details were already available for users to observe in the iOS Kiosk App.  Now, they are available also in the the computer Kiosk for a uniform experience. To edit what is shown simply go to Preferences -> Organization Info in FileWave Central and you can update the information.

image.png

macOS and Windows

image.png

Mobile like iOS and iPadOS

App Portal Comp Info.jpeg

Kiosk Package Updates Category (macOS PKG)

Description

Kiosk may show 'Package Updates' for associated PKG Filesets where older PKGs are already installed on the device.

KioskPackageUpdates.png

Information

When a PKG Fileset is associated, as a Kiosk item, to a device, the FileWave Client will check the PKG receipts on the device.  If a matching receipt is found and the version of this installation is older, the Kiosk will show this as a 'Package Update'.  This is an automated category and therefore will not be visible in either:

For example, a device that already has version 1.0 of My Awesome App, installed as a PKG.

MyAwesomeApp-1.0.png

Since installation was by PKG, there should be a receipt.  If you know the identifier of the PKG, you may use Terminal to confirm this:

# pkgutil --pkg-info com.myawesomeapp.pkg.app
package-id: com.myawesomeapp.pkg.app
version: 1.0

Upload and create a Kiosk association of a newer PKG version of the App

MyAwesomeAppFileset-1.1..png

When the device receives this new association, the Kiosk drop down menu will add an additional option 'Available Updates':

KioskAvailableUpdates.png

Clicking on this will open the Kiosk Installer window, showing the added 'Package Updates' category as shown above in the description.

It does not matter how the older PKG was initially installed, e.g. through FileWave or locally. This is particularly useful for warning users, who have the option to install their own PKG and can see that an update has been offered through FileWave.

PKG version is set within the PKG by the developer of the device. If the developer does not increase the number from prior versions, then the Fileset cannot be shown as a 'Package Update'.

PKG installers have their own version and this need not match the App version as shown in Finder.

Kiosk should show only Kiosk associated Apps (15.3+)

What

Before FileWave 15.3, apps that are directly deployed to the device and have the “Allow removal” option checked are shown in Kiosk. If the user decides to remove them from their device, that app is shown in Kiosk—in case the user changes their mind and wants to have them on their device again. 

When/Why

This was done before when there wasn’t Verify. Now, with Verify, this process is automated (the app will be installed again after Verify), so there is no sense in showing those apps in the Kiosk anymore.

How

In FileWave 15.3+, the Kiosk shows an item in the app list only if it is Kiosk-associated with the device. Non-kiosk-associated items do not appear on the list. This is more straightforward behavior, but it may be confusing for someone who was used to seeing apps in the Kiosk before that are now not showing. 

Setting the Primary Color, Name and Logo in Kiosk/App Portal (15.3+)

What

This article provides step-by-step instructions for configuring the new Kiosk2 and App Portal introduced in FileWave 15.3.0, including how to set a primary color, name, and logo for the App Portal / Kiosk on FileWave v15.3.0+.

When/Why

For brand consistency, options exist (depending on device type) for configuring:

When referring to a custom logo, the expected image should be: 112 x 96, 8-bit/color RGBA, non-interlaced
Some changes are server side.  If hosted, please contact Technical Support for assistance.

How

iOS & iPadOS

Devices of this nature use the App Portal.  As of FileWave 15.3, the App Portal IPA is automatically delivered to devices and will automatically update.

Customisation Options:

Logo Customisation

If you are a Hosted Customer then you will need Technical Support to assist with these changes for now.

Direct editing of the IPA is not feasible.  As such, the logo needs to be hosted from the FileWave Server.  The chosen image needs to be placed in the following location:

/usr/local/filewave/django/static/kiosk2/images/

For the IPA to utilise this image, edit the the following file:

/usr/local/filewave/django/filewave/settings_custom.py

The line may be added to the bottom of the custom settings file and needs to include the FQDN of the FileWave Server, along with the named image in the format:

KIOSK_LOGO_URL = 'https://[fully_qualified_domain_name]/filewave/static/kiosk2/images/[file name]'

For example, imagine those details are:

The line added will then appear as:

KIOSK_LOGO_URL = 'https://demo.filewave.ch/filewave/static/kiosk2/images/image.svg'

Supported file formats are:

- SVG
- JPEG
- PNG
- GIF
- Animated GIF
- WebP
- Animated WebP
- BMP
- WBMP

Customise Colour

Colour may be customised by editing the same custom settings file.  The colour should be presented in hex of either 6 or 8 characters.  The line to add (again this may be added to the bottom of the custom settings file), should be of the format:

KIOSK_PRIMARY_COLOR = '[hex colour]'

 For example:

KIOSK_PRIMARY_COLOR = '#e580ff'

or

KIOSK_PRIMARY_COLOR = '#FF0000CC'

The FileWave Server Service should be restarted after modification of the custom settings python file.

macOS

macOS access the Kiosk by way of the Menu Bar

macOS Kiosk App Logo

Customisation Options:

All 3 items can be specified through a single file:

macOS:

/usr/local/sbin/FileWave.app/Contents/MacOS/FileWave\ Kiosk.app/Contents/custom/settings.json

The contents should appear similar to:

{
   "logo_url": "https://my.company/logo.svg",
   "primary_color": "#0465DA",
   "kiosk_app_name": "My Kiosk"
}

Defined as:

Key Name Key Value Default
logo_url URL path to hosted custom image FileWave Logo
primary_color Colour in hex format, e.g. #RRGGBB #0465DA
kiosk_app_name Text Name of opened Kiosk Window FileWave Kiosk

 It may be necessary to reboot the computer before changes take effect; particularly if customisation of the older Kiosk was removed at the same time that the new Kiosk and customisation is added.

If the custom icon is added as per the instructions for i(Pad)OS devices, the same URL may be used in the above settings.

The above method requires a logo to be hosted.  However, it may be desirable to provide a local logo instead.  The following methods provide a pre-configured Fileset to achieve this. The logo in this case is the icon in the menu bar only.

FileWave Kiosk2 Menu Bar Icon.fileset.zip

The Fileset needs to be edited prior to deployment.  Out of the two files shown, the chosen custom image should be named to match the first png: 'tray-icon-macos.png'.  Leave the other file in place.

image.png

 Dragging the custom icon over the shown file should prompt a message as below.  Select Replace.

image.png

Associate with a test device, and once happy with the look, you can broaden the association.

The Fileset is designed to:

The new image will not show unit the FileWave Client is restarted.

Windows

Windows access the Kiosk by way of a System Tray item

Windows Kiosk App Logo

Customisation Options:

All 3 items can be specified through a single file:

Windows (32bit FileWave Client: 15.4-):

C:\Program Files (x86)\FileWave\kiosk\custom\settings.json

Windows (64bit FileWave Client: 15.5+):

C:\Program Files\FileWave\kiosk\custom\settings.json

The contents should appear similar to:

{
   "logo_url": "https://my.company/logo.svg",
   "primary_color": "#0465DA",
   "kiosk_app_name": "My Kiosk"
}

Defined as:

Key Name Key Value Default
logo_url URL path to hosted custom image FileWave Logo
primary_color Colour in hex format, e.g. #RRGGBB #0465DA
kiosk_app_name Text Name of opened Kiosk Window FileWave Kiosk

 It may be necessary to reboot the computer before changes take effect; particularly if customisation of the older Kiosk was removed at the same time that the new Kiosk and customisation is added.

If the custom icon is added as per the instructions for i(Pad)OS devices, the same URL may be used in the above settings.

Windows System Tray Logo

The above method requires a logo to be hosted.  However, it may be desirable to provide a local logo instead.  The following methods provide a pre-configured Fileset to achieve this. The logo in this case is the icon in the System Tray only.

FileWave KioskV2 Sytem Tray Icon.fileset.zip

The provided Fileset contains two revisions:

image.png

The Fileset needs to be edited prior to deployment.  Out of the four files shown, the chosen custom icon should be named to match the two icon files: 'tray-icon-dark.ico' and 'tray-icon-light.ico'.  Leave the other two files in place.

Unlike the other images, the Windows System Tray is using '.ico' files.  These need to be of equal size, e.g. 256x256, 128x128, etc.

Consider exporting the current 'ico' files, editing them with the chosen logo and then upload, if unsure how to create '.ico' files.

FileWave 15.4- (FileWave Client 32bit)

image.png

FileWave 15.5+ (FileWave Client 64bit)

image.png

Dragging the custom icon over the shown files should prompt a message as below.  Select Replace.

image.png

Associate the relevant revision with a test device and once happy broaden the association.

The new image will not show unit the FileWave Client is restarted.

App Portal on iOS/iPadOS devices that don't support the application (15.3+)

What

If you have an iOS/iPadOS device that is older than what is officially supported by FileWave and you are working ok but you can't get the Kiosk (App Portal) to install.

When/Why

You can revert for now to the old WebClip using the documented process here. This is a temporary workaround.

How

It is possible to activate Web Clip of an old App Portal on devices which don't support new App Portal.

  1. Create new Apple Profile → Web Clip Profile (can be done in both FileWave Central and Anywhere)

    image.png


  2. Fill in URL field with: https://fqdn:20443/ios/recommended_apps/%device_id%#apps replacing "fqdn" with your server's DNS name.
  3. Deploy profile to desired device(s).

Applications Preventing Reboot (macOS/Windows)

Description

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.

Some processes do not respond to FileWave Clients requests to quit when "Quit all" or "Quit Application" is being used, because they are being immediately restarted by LaunchDaemon after quitting, or do not respond properly to the signals sent to them by FileWave.  This can result in users being blocked from installing FileSets with the "Reboot" Flag set. 

Information

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.

Solution

Requirements to prevent this experience are:

A settings file may be configured to allow for certain apps.  Create a fileset containing the settings.ini and then associate it to the desired clients. The directory where the file should be placed depends on the operating system:

macOS
/usr/local/sbin/FileWave.app/Contents/Resources/fwGUI.app/Contents/custom
Windows (FW v15.4.2 or lower)
C:\Program Files (x86)\FileWave\custom
Windows (FW v15.5.0 or higher)
C:\Program Files\FileWave\kiosk\custom

The changes will only be visible in the desktop Kiosk after the user logs out and logs in again.

To exclude an unexpected process from being listed and preventing the reboot, first obtain the Bundle ID or process name of the listed App or Service.  

Obtain Bundle ID or Process Name

Windows

In this example, to exclude notepad you require: 'notepad.exe'

macOS

~/Library/Application\ Support/FileWave/FWGUI.log

There should be lines similar to the following, for each process that has prevented the reboot:

|DEBUG|INSTALLER|[addProcessInfo] new process added /Applications/Utilities/Terminal.app pid 67345 bundleID com.apple.Terminal
|DEBUG|INSTALLER|[addProcessInfo] new process added /Applications/Preview.app pid 73400 bundleID com.apple.Preview
|DEBUG|INSTALLER|[addProcessInfo] new process added /Applications/TextEdit.app pid 73718 bundleID com.apple.TextEdit

Configure 'settings.ini'

The 'settings.ini' file should be configured with the following format (Bundle IDs or processes being a comma separated list):

[General]
ignoredApplications=com.bar, com.foo

For the example of Windows Notepad, it should read:

[General]
ignoredApplications=notepad.exe

To avoid the newer default processes Microsoft now include, consider ignoring the following:

[General]
ignoredApplications=StartMenuExperienceHost.exe,SearchApp.exe,TextInputHost.exe

For the example of macOS TextEdit, it should read:

[General]
ignoredApplications=com.apple.TextEdit

Combining this with current generic settings, it may look something like:

show_top_downloads=false
window_title="My Customized Kiosk"
hide_system_tray=false

[General]
ignoredApplications=com.adobe.acc.AdobeDesktopService,com.apple.TextEdit

Deployment

Deploy the 'settings.ini' file to the following locations: 

macOS

/usr/local/sbin/FileWave.app/Contents/Resources/fwGUI.app/Contents/custom

Windows (FW 15.4.2 and lower)

C:\Program Files (x86)\FileWave\custom

Windows (FW 15.5.0 and higher)

C:\Program Files\FileWave\kiosk\custom

Troubleshooting

Troubleshooting

Checking what version of iOS/iPadOS App Portal is being pushed out (15.3+)

What

How do I know what version of App Portal (Kiosk) is being pushed out to iOS/iPadOS devices?

When/Why

After a FileWave upgrade, there likely will be a new version of the iOS/iPadsOS IPA pushed out through the automatic upgrade process. Because this process is a bit invisible, verifying what the server believes is the version it is pushing out is sometimes necessary.

How

In FileWave Central, go to Assistants -> Manage Administrators and then pick your user account, though depending on permissions, you may want to use fwadmin. Grab the base64 token seen below in the image, including the = at the end of it.

image.png

Now you can ask the server. Replace ezk5ODxxxmE0OyyyyyyyOX0= below with your token, and replace support2.filewave.net with your server's DNS name.  

Here is a command you can run in Terminal.app on a macOS system or any system that has curl installed:

curl -H "Authorization: ezk5ODxxxmE0OyyyyyyyOX0=" https://support2.filewave.net/filewave/api/kiosk/internal/kiosk-status

Here is a PowerShell example of the same command:

# Define the URL to make the request
$url = "https://support2.filewave.net/filewave/api/kiosk/internal/kiosk-status"

# Define the headers, including the Authorization token
$headers = @{
    "Authorization" = "ezk5ODxxxmE0OyyyyyyyOX0="
}

# Use Invoke-WebRequest to make the GET request with headers
$response = Invoke-WebRequest -Uri $url -Headers $headers -Method Get

# Output the content of the response
$response.Content

The output of the command will be something like below. 

{"installed":{"ipa_url":"https://fw-kiosk-v2-ipas.filewave.cloud/15.3.1/App_Portal_15.3.1.ipa","ipa_md5":"81628b83dad72e274ef93ea031db1484","build_date":"2024-03-27T20:08:49.192563Z","bundle_version":"15.3.1"},"latest":{"ipa_url":"https://fw-kiosk-v2-ipas.filewave.cloud/15.3.1/App_Portal_15.3.1.ipa","ipa_md5":"81628b83dad72e274ef93ea031db1484","build_date":"2024-03-27T20:08:49.192563Z","bundle_version":"15.3.1"},"available_versions":["15.3.1"]}%  
Troubleshooting

Removing pre-15.3 Kiosk Customizations (macOS/Windows)

Prior to FileWave 15.3 you had a method of customizing the Kiosk that is not used in 15.3 and beyond. Some of the customizations will be ignored with 15.3, but there are things you'll want to potentially remove and you may want to stop pushing out customizations that are no longer enforced. This article is a paired down version of the old article and simply contains information on what customizations you might have had in the past so you can look to potentially remove the files/edits. 

The look of the FileWave desktop Kiosk was customized using Qt Style Sheets. You would have had to create a file named fwGUI.qss and deploy it to clients in the right location. Several icons were also customizable by placing your custom icon in the right place with the right file name. All of this can be deployed via a Fileset.

Check out Setting the Primary Color, Name and Logo in Kiosk/App Portal (15.3+) and Applications Preventing Reboot (macOS/Windows) for the things that can be customized in FileWave 15.3 and beyond.

Deploy

fwGUI.qss -- You would have created a Fileset containing the fwGUI.qss and the icons, then associate it to the desired clients. The directory where these files was placed depends on the operating system. In 15.3 and beyond you don't want to push the qss file or icons out as they will have no effect on the Kiosk.

macOS
/usr/local/sbin/FileWave.app/Contents/Resources/fwGUI.app/Contents/custom
Windows
C:\Program Files\FileWave\custom (might be "Program Files (x86)", depending on the platform)

The changes will only be visible in the desktop Kiosk after the user logs out and logs in again.

Menu Bar/System Tray Settings

settings.ini -- contained generic kiosk ui settings. Especially important is that if hide_system_tray = false that you will end up with 2 icons for the Kiosk where one is the old Kiosk if you are on FileWave 15.3.

Example
window_title = "Your New Window Title"
show_top_downloads = true
hide_system_tray = false

Customizable icons

You might have included icon files that you used to replace them in Kiosk before 15.3. These icons will not appear in 15.3 or newer.

File name Description Example Pixel Size
action_back.png Icon for the "Back" action in the Software Installation dialog DesktopKiosk-back.png 48x48
action_forward.png Icon for the "Forward" action in the Software Installation dialog DesktopKiosk-fwd.png 48x48
background_icon.png Icon used for the watermark (FileWave icon) 512x512
rating_star_half.png Icon for half a rating star DesktopKiosk-star_half.png 40x40
rating_star_off.png Icon for a rating star that is off DesktopKiosk-star_off.png 40x40
rating_star_on.png Icon for a rating star that is on DesktopKiosk-star_on.png 40x40
tray_icon.png System tray icon. If missing, the background_icon.png is used. (FileWave icon) 16x16
warning.png Warning icon, displayed when a fileset has problems (e.g. missing VPP user) DesktopKiosk-error_red-cir_status.png 64x64



Troubleshooting

Kiosk with macOS in a VM: Enabling Metal support

Description

The new Kiosk requires 'Metal' support.  VMware does not support metal by default.  It is possible to add support, however the details provided are Beta and not only may the VM become unstable, but the host may also Kernel Panic.

Use cautiously

Without the necessary configuration, the new Kiosk will not show and the user logs will show something like:

2024-05-13 10:40:15.324 FileWave Kiosk[1241:5674] Could not acquire Metal device.
2024-05-13 10:40:25.936 FileWave Kiosk[1241:5674] Unable to create FlutterView; no MTLDevice or MTLCommandQueue available.

Configuration

The following configuration requires the VM to be shutdown (not paused) prior to editing.

Locate the containing folder of the VM.  Within this will be a .vmx file.  For example, if the containing VM Folder were called 'macOS 12.vmware, the file to edit should be called 'macOS 12.vmx':

/Users/sholden/Documents/Virtual\ Machines/macOS\ 12.vmwarevm/macOS\ 12.vmx

Add the following two lines:

appleGPU0.present = "TRUE"
svga.present = "FALSE"

Once added, the VM may then be booted.  To remove this configuration, again shutdown the VM, edit the file, this time removing these two entries.

It may also be necessary to define the aspect ratio in the same file with the following two lines.  1920 x 1080 used as an example:

appleGPU0.screenWidth="1920"
appleGPU0.screenHeight="1080"

Although this may work, in practice the VM crashed too often or became seemingly unusable.  Since the host may also Kernel Panic, recommendation would be to avoid configuring this on VMware test devices, unless absolutely necessary.  Even then, consider undoing this once the test has been completed.

Troubleshooting

Resolving SSL and Manifest Validation Errors with FileWave Kiosk Installation (15.3+)

What

This article addresses an issue encountered during the installation of the new FileWave Kiosk v.15.3.1 on macOS and Windows devices. Users may encounter SSL errors and manifest validation failures that prevent the Kiosk from installing correctly.

When/Why

These installation errors typically occur when upgrading to FileWave v.15.3.1 and are primarily due to conflicts with certain content filters or proxy settings that block or misclassify necessary URLs. This is particularly relevant for organizations using content filtering solutions like Lightspeed, which may categorize essential URLs as unknown, thus blocking them.

"InstallApplication	command error		2024-04-22T07:36:38	2024-04-22T07:36:38				Could not validate manifest..An SSL error has occurred and a secure connection to the server cannot be made.	com.filewave.ios.app.kiosk2	"

How

To resolve these installation issues, follow the steps below:

  1. Check Proxy and Firewall Settings: Ensure that your organization's proxy or firewall settings are not blocking access to FileWave URLs.

  2. Whitelist Necessary URLs: Add the following URLs to the whitelist in your content filter or proxy settings:

    • https://fw-kiosk-v2-ipas.filewave.cloud/
    • *.filewave.cloud

    This change allows devices to communicate securely with FileWave servers and access the necessary resources for installing the Kiosk.

  3. Reattempt Installation: After updating your settings, reattempt the installation of the FileWave Kiosk on the affected devices.

# Example command to verify if the URL is accessible from your network
curl -Iv https://fw-kiosk-v2-ipas.filewave.cloud/

If the issue persists, check your SSL certificate settings and network configuration for any discrepancies that might be interfering with secure connections.

Related Links

Digging Deeper

The SSL error typically indicates an underlying issue with the secure connection setup between the client device and FileWave servers. This can be caused by SSL certificate verification failures, misconfigured proxies, or stringent network security policies that incorrectly classify or block legitimate URLs required for FileWave operations. Adjusting content filtering policies or proxy settings often resolves these issues, but further investigation into SSL trust settings may be required for complex network environments. 

FileWave End-User Notifications

FileWave End-User Notifications

FileWave End-User Notifications (15.5+)

What

With the release of FileWave version 15.5.0 and onward, administrators can now send custom messages to enrolled devices directly from FileWave Anywhere, FileWave Central, or through API calls. These messages appear as system notifications on users’ devices, allowing administrators to communicate important information efficiently and effectively, thereby enhancing user engagement and experience.

Key Functionality

Send Notification requires Permissions granted within the Managed Administrator view.  'fwadmin' account will automatically be granted such permissions, but other accounts or groups should be enabled as desired.

When/Why

When to Use

Why Use This Feature

How

Sending a Notification

  1. In FileWave Central right click on a Client, Group or Smart Group and pick Send Notification...
  2. Ensure that all of the options are set how you want. 
    Author: Your name
    Title: The title of the notification dialog
    Text: The detailed text to display
    Add Link: This allows you to have a clickable link on the notification
    Expiration date: After this date and time the system will not continue to try to get the notification to the selected devices.

    image.png

  3. A confirmation dialog will ask you to confirm sending and tell you the number of devices being messaged. Check that the number reflects what you think it should be. If it says 500 but you meant to message 5 devices then click Back and then Cancel if you want to try to pick devices again. Once you click the final Send button on the confirmation dialog there is no canceling it.

If you selected a Group or Smart Group it is important to know that the targets will be the devices that were in that group at the time you sent the message. If a device enters the group tomorrow it will not get the message even if the message has not expired yet. Similarly if a device leaves the group after you already sent the message it will still receive the message when it comes online.

User Experience

Digging Deeper

Important Considerations

General (All Platforms)
Platform-Specific Behaviors

Troubleshooting: When Devices Will Not Receive Notifications

FileWave End-User Notifications

Force Enable Notifications on macOS for FileWave Kiosk

What

To ensure that notifications from the FileWave Kiosk and End User Notifications are consistently displayed on macOS devices, administrators can deploy an Apple Profile that forces notifications for the com.filewave.kiosk2 application. This profile enforces the display of notifications and prevents end users from disabling them, ensuring important messages and alerts are always visible to users.

Please note that in 15.5.0 the TCC profile that is built in to FileWave will handle this. You no longer need to create this Fileset and notifications will be enabled. We will archive this article after 16.0 releases.

When/Why

When to Use

Why Use This Feature

How

You can either use our premade Fileset: Profile - Force Allow Kiosk Notifications (macOS).fileset.zip or you can create it yourself using the below steps.

In FileWave Central or Anywhere you can create the profile. The images that follow are from Central, but the process is the same in Anywhere. 

image.png

image.png

Type in the Bundle Identifier and then select it and click Next
Bundle Identifier for Kiosk app
: com.filewave.kiosk2

image.png

    • Set up behavior for the notifications and click Save

image.png

Device Behavior