ebe

Update: got it to work :) mode=explicit,broadcast=false,action=android.intent.action.MAIN,package=com.samsung.android.knox.efota,class=com.samsung.android.knox.efota.ui.StartActivity

Hi, Is it possible to start specific application using Intent in WS1? I want to create intent to start Samsung E-FOTA application in this case. https://docs.omnissa.com/sv-SE/bundle/WorkspaceONE-UEM-Product-ProvisioningVSaaS/page/RunIntentActionFileActionAndroid.html

@Sumanth Narayanapura Chandrashekhar Fully Managed / Device Owner. If this is the case, then Unattended Agent can't determine?

@Sumanth Narayanapura Chandrashekhar Thanks for great answer and clarification! "When using unattended agent, If a personal profile is found, the agent will switch to Attended mode for security reasons." - How will the agent look for a personal profile if we are only using Fully Managed devices? I need a good answer here to bring it up to management to switch to Unattended agent to resolve the permission issuse and to also use same agent to our dedicated and user devices.

@Saurabh Jhunjhunwala we don't want to use Unattended version to our employees due to integrity, therefore we use public version.

So there is no way to fix the issue with accessibility prompt for public Assist app? If no, can you please raise this issue with the responsible team about this?

Fully Managed. We are using both public Assist app and Unattended app. Accessibility prompt permissions is from the public app.

Exactly, this permissions in KSP will not resolve it.

@Kevin Murray Knox Remote Support does not have this limition..

I agree. Also that the app is provided by Omnissa and that users need to go to accessibilty to grant permissions is for we not good end user experience. We are considering moving from Assist because of this and use Knox Remote Support. I think we can maybe see this move from other customers as well if it doesn’t get fixed to set permissions.

Any change you know how to configure it in KnoxServicePlugin? I got following from Samsung: Knox Service Plugin (KSP) cannot directly grant accessibility permissions to a third-party app. However, KSP offers the ability to manage and assign certain special permissions to apps via the Permission Controls policy. The available permissions include "All file access", "Appear on top", "Change system settings", "Notification access", and "Usage data access", but accessibility permissions are among them. https://docs.samsungknox.com/admin/knox-platform-for-enterprise/knox-service-plugin/kbas/kba-1261-grant-special-permissions-for-an-app/ Also, it seems that the app doesn't have "android.permission.ACCESSIBILITY" in the list when inspecting the app so it seems when triggering a remote session, Assist somehow trigger the permission..

It is both Android and iOS. Do we also need to have Hub app running as well to get it from disconnected to connected? Thanks for the KB👍🏻

Single App Mode with tags worked perfect, thanks!

Hi, Is there a way to re-connect devices where MTD was activated in Hub app? In Lookout-portal, it says "Disconnected"

Hi, Is there a way to trigger to start Hub app on iOS after successful ADE enrollment? It seems that we can't send notifications or activate MTD unless a user opens Hub app - logins with credentials - then it works. How to resolve this issue somehow?