Hello Everyone, 

That script work to remove the icon :

writeprivateprofstring Kiosk HideFloatingHomeButton 1 refreshlockdownrestrictions

reset /s

Thanks for the info and the help

Are you also applying a SOTI Lockdown configuration on top of using EHS for lockdown? You should realistically only be using one or the other. 

With the SOTI Lockdown if you are using a Native Mode lockdown then it will render a floating home button on Android 8 devices. If you switch this to Activity Suppression instead of Native Mode the floating home button should go away. 

As the floating home button is present with or without the EHS lockdown, I don't think it is likely related to the MobiControl device agent or policy.  Don't overestimate the power of the device agent, as most features has to be implemented in the OEM firmware first.  An MDM device agent may be able to control it if there is related MDM API's callable by the device agent.  Zebra is famous for supporting lots of configurable features not found in most other device brands/models.  If I were you, I would first check the documentations of your Zebra device models to see if there are such configurable feature implemented/controllable in either device's SETTINGS, Zebra MX, or other means. If so, check if there is any mechanism(s) in the MDM solution to configure such feature, e.g. parameter in GUI of particular profile/adv-configuration policy,  MX XML file deployed via MobiControl script command, parameter(s) in Zebra's OEMConfig compliant app, etc. 

When debugging problems like yours, please see if you can find CONSISTENT pattern(s) between functional and problematic devices.  For examples, you can check the following:

Is the floating home button present in ALL your TC56 and MC3300 models? Or just in SOME of them?

Are ALL problematic device running the same device agent version different from ALL functional devices of the same model+firmware  running other device agent version(s)?.

etc.

Following similar logic of the above questions/tests, one could often narrow down the root cause if the device sample size is big enough and the test/analysis is systematic.

Hi,
Have observed this issue also, have updated the agent on some Zebra TC51 for test which is on same Atlas platform as TC56 and MC3300.
No Soti Lockdown payload is assigned to the devices and the issue is consistent on all TC51 devices i tested on and starts from Agent version 15.4.2.1025 and still persist on latest agent 15.4.4.1063.

The 15.4.2.1025 agent have this in release notes, maybe that fix broke something else?

I don´t have any case for it yet but seems to be time for it or if someone from Soti can confirm there is already an known issue?

Were all your problematic devices using v15.4.4.1063  device agent right after device-factory-reset & device enrollment?  Or had they been running an earlier device agent version earlier, and were just upgraded to use v15.4.4.1063 device recently? 

If it's the latter case for your devices,  were there any particular reasons  [e.g. any particular new feature(s) or bug fix(es)] that force you to perform such device agent upgrade?

If there is no strong reason to justify an upgrade, then until a newly released device agent with the bug fixed is thoroughly tested on your platform, you have the option to use the older functional device agent for newly enrolled production devices, and disallowing currently enrolled devices to upgrade to this buggy v15.4.4.1063 version.

Hi Mathieu,

Thanks for posting on SOTI Pulse, thanks Raymond, and Matt for responding to the post.

We are pleased to hear that you have found a solution to your query.

If you have any further issues or queries, please feel free to ask. We are here to assist you.

Kind regards,

Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net |