Contents

Support this site


Configure MANAGED SETTINGS for Urmobo MDM

MANAGED SETTINGS can be set up quickly and easily through Urmobo EMM. This guide covers only policy configuration and does not extend to Entities.

Prerequisites:

  • Android Enterprise is bound
  • A policy exists, or will be created for this guide
  • Requirements are met
  • A licence key, if desired
Avoid blocking the Settings application

You'll note in the below configuration steps, nowhere is it mentioned to import or attempt to configure the native Settings application. For the Kiosk use case, blocking Settings (com.android.settings) through the install type of Blocked will prevent MANAGED SETTINGS from working.

It is not necessary. Native Settings needs not be present in the application list at all.

Add MANAGED SETTINGS to the policy

#

Head to Management > Policies from the left-hand navigation, and create or select a policy for editing.

Scroll down to Play Store and in the open window, search for BAYTON MANAGED SETTINGS, or org.bayton.managedsettings if the former returns no results.

Click the icon to select the app.

Select an appropriate Install Type. I have selected Force Installed however it is your choice. A type that prevents uninstallation is ideal.

Click Select

MANAGED SETTINGS will appear in the apps table above.

Configure MANAGED SETTINGS

#

Click the 3 dots menu icon to the left of the app icon, and select Managed Configuration.

In the below section, provide a configuration name, set the appropriate configs, and click Save.

Set kiosk customisation policies

#

Scroll up to Kiosk, and configure the kiosk environment. I have selected the native Android Kiosk, but you may prefer the Urmobo Kiosk.

Select Blocked for Device settings, and configure any additional kiosk settings as desired.

Save your policy, configuration is complete.

Further support or feature requests

Are you in need of further help, or would you like to raise a feature request? You can:

mail Reply by email | edit_note Edit this page.