Skip to main content

Automatic updating of iOS/iPadOS Kiosk

What

FileWave 15.3.0 introduced 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:

  • the iOS/iPadOS Kiosk is now delivered through the Apple App Store
  • it is deployed as a VPP app
  • the App Store app replaces the older Kiosk on managed devices when FileWave deploys it

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:

  • FileWave automatically installs the new Kiosk on all managed iOS/iPadOS devices.
  • The web clip for the older App Portal is removed from devices.
  • Filesets of the previous native App Portal are not automatically removed, so administrators can remove those associations if they only want the newer Kiosk present.
  • New releases of the Kiosk are automatically deployed to managed iOS/iPadOS devices.

FileWave 16.3.0 and later

For FileWave 16.3.0 and later:

  • the iOS/iPadOS Kiosk is deployed from the Apple App Store as a VPP app
  • FileWave will push the install request for the new Kiosk and it will replace the older Kiosk on managed devices
  • administrators must ensure that enough free VPP licenses have been obtained in ASM/ABM before upgrading

Important preparation before upgrading to 16.3.0+

Before moving to FileWave 16.3.0 or later:

  • go to Apple School Manager or Apple Business Manager
  • acquire free licenses for FileWave Kiosk
  • obtain licenses for more devices than are currently managed so normal growth does not create a shortage

Example:

  • if you manage 1000 devices, acquire something like 1500 licenses so you do not unexpectedly run over the available count

If sufficient licenses are not available in ASM/ABM, deployment of the new Kiosk can be delayed or blocked.

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 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.

Related Content

Back to top