Automatic updating of iOS/iPadOS Kiosk

What

FileWave 15.3.0Kiosk introducedon automatic deploymentiOS and updatingiPadOS ofis the iOS/iPadOSself-service Kioskapplication sothat administratorslets nousers longeropen neededKiosk, toview manuallyKiosk-associated managecontent, theinstall olderavailable Kioskitems, .ipaand workflow.trigger actions such as Verify.

Starting with FileWave 16.3.0, therethe iscurrent andelivery importantmethod change to how this works:

thefor iOS/iPadOS Kiosk is now delivered through the Apple App Store itversion isof the app, deployed as a VPP app/ Apps and Books app. As long as FileWave is correctly syncing with Apple School Manager (ASM) or Apple Business Manager (ABM) and the required FileWave Kiosk licenses have already been acquired there, the FileWave server will push the App Store appKiosk replacesto managed devices and replace the older Kiosk on managed devices when FileWave deploys it Kiosk.

App Store listing:

• FileWave Kiosk on the Apple App Store

When/Why

This change alignsis the iOS/iPadOScurrent and recommended behavior for FileWave 16.3.0 and later. The move to the App Store / VPP model aligns Kiosk deployment method with Apple's current best practices for managed app delivery.

It also brings FileWave in lineand with the way other MDM and UEM platforms typically deliver managed iOS and iPadOS applications.

The keymost important operational differencechange is that administrators mustshould nownot make suretreat the requiredKiosk Appupgrade Storeas /fully VPPself-contained licensesanymore. existBefore in Apple School Manager (ASM) or Apple Business Manager (ABM) before movingupgrading to FileWave 16.3.0 or later.later, make sure FileWave is connected to ASM/ABM for app-license sync and that enough free FileWave Kiosk licenses have already been obtained. If those preconditions are in place, the transition is straightforward. If they are not, Kiosk deployment can be delayed or fail to appear when expected.

How

The

FileWavesection below focuses on the current 16.3.0+ behavior first. A short reference section for 15.3.0 through 16.2.x

Foris FileWaveincluded 15.3.0 through 16.2.x:

FileWave automatically installs the new Kiosk on all managed iOS/iPadOS devices. The web clipafterward for thecustomers olderwho App Portal is removed from devices. Filesets of the previous native App Portal arehave not automaticallyupgraded removed,yet soor administratorswho canneed removehistorical thosecontext. associations if they only want the newer Kiosk present. New releases of the Kiosk are automatically deployed to managed iOS/iPadOS devices.

How

Current behavior in 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 beforeBefore upgrading

Important preparation before upgrading to 16.3.0+

Before moving to FileWave 16.3.0 or later:

• gomake tosure FileWave is syncing Apps and Books / VPP licenses from Apple School ManagerASM or Apple Business ManagerABM
• acquire free licenses for FileWave Kiosk in ASM/ABM before the upgrade
• obtain licenses for more devices than are currently managed so normal growth does not create aan avoidable shortage

Example:

A

practical example is to acquire about 1500 licenses if you currently manage 1000 devices, acquire something like 1500 licenses so you do not unexpectedly run over the available count .

If sufficientthe licenses are already present before the upgrade, devices remove the older enterprise Kiosk and install the new App Store Kiosk shortly afterward, typically within a few minutes.

If the licenses are only acquired after the upgrade, the change is less immediate. In that case, purchase the licenses, run a Model Update, and then Verify the affected devices. If some other model change is made and pushed, that should also trigger verification. Without that follow-up activity, devices may not available in ASM/ABM, deployment ofreceive the new Kiosk until their next normal verify cycle, which can be delayedup to 24 hours later.

There is currently no in-product warning that tells administrators they upgraded without the needed Kiosk licenses. If VPP is configured but the app has not been acquired in ASM/ABM, one useful clue is in filewave_django.log, which can show:

No VPP organizations have the App Store Kiosk purchased.

Permissions and profile updates

Because the App Store Kiosk is a new app, iOS/iPadOS treats it as a different application even though it serves the same purpose. Administrators should expect permission prompts such as notifications or blocked.

location TCCservices /to Notificationsappear profileagain updateafter

If you currently deploy a configuration profile that allows notifications for Kiosk, review it before or during your FileWave 16.3.0the transition.

The new iOS/iPadOS Kiosk app uses this bundle identifier:

• com.filewave.ios.app.kiosk3

If youryou notification-relateddeploy a configuration profile that forces notifications or uses any other app-specific payload referencesfor Kiosk, review and update that profile for the new bundle identifier before or during the FileWave 16.3.0 transition.

Reference: behavior in FileWave 15.3.0 through 16.2.x

From FileWave 15.3.0 through 16.2.x, FileWave automatically deployed the newer iOS/iPadOS Kiosk through the older Kioskbuilt-in bundleworkflow identifier,rather updatethan itthe toApp matchStore / VPP model used in 16.3.0 and later.

In that earlier behavior:

FileWave automatically installed the new app.Kiosk on managed iOS/iPadOS devices the older App Portal web clip was removed from devices filesets of the previous native App Portal were not automatically removed, so administrators could remove those associations if they wanted only the newer Kiosk present newer Kiosk releases continued to be deployed automatically through that same pre-16.3.0 workflow

Related Content

• Setting the Primary Colour, Name and Logo in Kiosk/App Portal (16.0+)
• Resolving SSL and Manifest Validation Errors with FileWave Kiosk Installation (15.3+)
• Default TCP and UDP Port Usage