Applying and removing Kiosk
The profile, the list of recipients, and the apply command are separate stages. In the table, open the “…” menu of the required profile. Do not start applying until the mode, applications, and set of devices have been checked.
Assigning recipients
- Select “Assign to devices”.
- Specify a device group or one physical Android phone.
- Check the current and new recipients, including devices that belong to the group.
- Confirm the assignment. It defines the scope of the profile; by itself it does not confirm that Kiosk is enabled on the phones.
One test phone can be in a group or have no group. For the first check, select it explicitly so as not to accidentally cover the whole work group.
Checking on a single device
- In the profile menu, select “Check and apply”.
- Select the device for the initial check and verify the scope shown.
- Click “Start check”. This step sends a command to the test recipient; it is already an action on the phone.
- Wait for the command confirmation. If there is no response, check the power, the network, and the connection to MDM.
- On the device itself, make sure the work application has opened, sign-in is complete, and there are no pending permission prompts.
- Select “The application opened on the device without a permission prompt” only after a physical check.
For SingleApp, check that the single application launches and that undesired exit is impossible. For MultiApp, check the start screen, switching between all work applications, notifications, and external transitions. For both modes, check the orientation, the network, a reboot, and the availability of the agreed maintenance method.
Command confirmation does not replace this check. Even a command without errors can leave the application on the sign-in screen or on a permission prompt.
Applying to all recipients
After a successful check, click “Apply Kiosk”. Verify the full list of recipients once more. Follow the progress of the operation and the device confirmations; the status screen refreshes automatically about every five seconds.
If some devices did not respond, separate them from those that completed the action successfully. Check the connection and the errors shown, then repeat the action only in the available interface for the required recipients. Do not create a new profile to resolve an ordinary delivery delay.
Status information is also available on the device card: profile mode, Lock Task lock, start screen, permitted applications, apply error, and delivery. If the DPC has not yet sent the state, the absence of information does not mean that the mode was successfully removed or enabled.
Stopping, pausing, and removing
| Action | Result |
|---|---|
| Stop applying | Stops execution of new commands of this operation. Kiosk already applied on devices remains. |
| Pause the profile | Disables the profile for further use. Do not use the “Disabled” status as confirmation that restrictions have been removed from every phone. |
| Remove from devices / Remove Kiosk | Removes the restrictions of this profile from the devices where it was applied. The profile is kept for reuse. Wait for the device responses. |
| Remove Kiosk from previous recipients | Used to clean up the previous scope after assignment changes. Check this scope before confirming. |
| Emergency exit | A separate temporary maintenance operation; it does not replace permanent profile removal. See the exit instructions for details. |
For permanent removal, select “Remove from devices”, check the recipients, and confirm the action. If applying is still in progress, it will be stopped, after which removal from the previous recipients is started. Wait for the confirmations and check the regular interface of the phones.
If the state changed during the operation
If the profile or recipients change, the form may require you to refresh the list and confirm the action again. First compare the new mode and scope. If the assignments may have been saved partially, refresh the table before repeating, so as not to send extra commands.
If the server did not return an operation identifier, consider the action neither successful nor definitely not performed: refresh the result and check the history. To look for confirmations, use client events.