Automatic updating of iOS/iPadOS Kiosk
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 15.3.0 willintroduced automatic deployment and updating of the iOS/iPadOS Kiosk so administrators no longer needed to manually manage the older Kiosk .ipa workflow.
Starting with FileWave 16.3.0, there is an important change to how this works:
App Store listing:
When/Why
This change aligns the iOS/iPadOS Kiosk deployment method with Apple's current best practices for managed app delivery.
It also brings FileWave in line with the way other MDM and UEM platforms typically deliver managed iOS and iPadOS applications.
The key operational difference is that administrators must now make sure the required App Store / VPP licenses exist in Apple School Manager (ASM) or Apple Business Manager (ABM) before moving to FileWave 16.3.0 or later.
How
FileWave 15.3.0 through 16.2.x
For FileWave 15.3.0 through 16.2.x:
The Webclipweb toclip for the oldolder App Portal will beis removed from the devices.
Filesets of the previous native App Portal willare not beautomatically impactedremoved, byso this change, they will still be installed on associated devices. Administratorsadministrators can remove thesethose associations if they only want the newer Kiosk present.
FileWave 16.3.0 and later
For FileWave 16.3.0 and later:
Important preparation before upgrading to 16.3.0+
EveryBefore upcomingmoving releaseto FileWave 16.3.0 or later:
Example:
If sufficient licenses are not available in ASM/ABM, deployment of the new AppKiosk Portal willcan be automaticallydelayed deployedor toblocked.
TCC / Notifications profile update
If you currently deploy a configuration profile that allows notifications for Kiosk, review it before or during your FileWave 16.3.0 transition.
The new iOS/iPadOS devices.Kiosk app uses this bundle identifier:
com.filewave.ios.app.kiosk3
If your notification-related profile or any other app-specific payload references the older Kiosk bundle identifier, update it to match the new app.