IBM MaaS360

IBM MaaS360

Join this online user group to communicate across Security product users and IBM experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  Brand new Motorola E7 device not installing COSU Kiosk mode.

    Posted 10 days ago

    Hello, 

    I recently enrolled a brand-new Motorola E7 to MDM Control, everything works as expected. However, i cannot for some reason install kiosk mode on this particular device. The Kiosk mode Status is perpetually stuck on "Download queued", tried rebooting and re-applying the policy, it's still stuck in Download queued. 

    Is there a way i can manually cancel the download or maybe re-installing Kiosk? Any help would be appreciated. Thanks in advance!



    ------------------------------
    Túlio Dessoy
    ------------------------------


  • 2.  RE: Brand new Motorola E7 device not installing COSU Kiosk mode.

    Posted 7 days ago
    Edited by Vinayaka Hegde 7 days ago

    Hi Tulio,

    We can distribute our android kiosk app from app catalog and install app from play store. To force install  kiosk app.

    https://play.google.com/store/apps/details?id=com.fiberlink.maas360.android.kiosklauncher&hl=en_IN

    Another way is change device policy to non-kiosk policy and wait for policy to reach to device.

    Change policy back again to have the kiosk based policy, which will trigger app installation again.

     

    If above both work-around does not work please share us the maas360 logs via email or upload logs action in device-view we will check and find the root cause for this issue

    Thanks,



    ------------------------------
    Vinayaka Hegde
    MaaS360
    Bangalore

    ------------------------------



  • 3.  RE: Brand new Motorola E7 device not installing COSU Kiosk mode.

    Posted 6 days ago
    Edited by Eamonn O'Mahony 6 days ago

    Hi Tulio

    From experience you probably need to add some apps to your allow-list in your COSU mode configuration.

    This includes the MaaS360 app, the MaaS360 launcher app and any other apps (and helper apps) that the system might need to run the configuration correctly. 

    These are the app ID's for MaaS360 and launcher app: 

    MaaS360 app:            com.fiberlink.maas360.android.control

    Launcher app:             com.fiberlink.maas360.android.launcher

    If you add these to the policy, Publish and ensure the new policy version is received by the device, you are quite likely to have a different experience. 

    Please let me know how you get on. 

    Best regards



    ------------------------------
    Eamonn O'Mahony
    MaaS360 Tech Sales
    Dublin
    ------------------------------