No Matches Found!
Try with a different search term
No Matches Found!
Try with a different search term
There's a new home for Articles. Find Articles on Our Product Support Page.
Hey guys, we have a problem an no idea what's the reason... I cofigured an enrollment policy for android devices. This policy is made for Legamaster android TVs. With our first order of this TVs (android 11) everything works fine. The devices were enrolled with type "work managed". With our second order (newer Type of TVs with android 13), every device I try to enroll with the same policy, will be enrolled as "work profile". We can't use the TVs with a work profile because we need a lockdown there. Have anyone any idea how I can solve that issue? Tank you and best regards!
I've been grappling with this issue for some time, and have posted about it before but I'm starting a fresh thread as suggested by Soti and following confirmation from them that this is an Android OS issue which cannot be fixed by Soti. The issue is that in-house apps cannot be successfully deployed to Android devices automatically, when using BYOD or COPE profiles. In work managed enrolments, updates to the in-house app deploy seamlessly without problem. In work profile (BYOD) and COPE enrolments, MobiControl attempts to deploy the app but Android requires user permission, and no notification or request is displayed. A silent notification does appear in the notification tray if the user looks for it, but they need to seek it within 30 minutes of the update being pushed out, otherwise MobiControl abandons the update attempt. I would have expected that, with a COPE (company owned, personal profile) device, the app deployment would be automatic, and that with a BYOD profile the user would be asked for permission to update. But the actual behaviour is the same with both BYOD and COPE profiles, and requires each user to be personally asked to deploy the update within 30 minutes. There are no notifications displayed under any circumstances. The behaviour is the same regardless of whether deploying the app via an app policy or a profile. It is also the case that, in order even to get to this point, the "Allow installation of apps from unknown sources" permission must be given to MobiControl in the work profile (undocumented), AND a similar permission must be expressly enabled in the Restrictions -> Security section of the device profile on the MobiControl server. After 10 months of troubleshooting, Soti have finally told me that this is the 'expected behaviour' according to Google. Has anyone else experience this and, more importantly, found a way to work around it? Thank you James MobiControl server 15.6.3.1018
Hello all, first sorry, we discover Android Entreprise and we are little lost when we enroll devices .. server mobicontrol is on version: 15 5 1 1010 We have some new device Zebra TC58 under android 11. If i take new device OUT OF the box, i follow the step to initialize the device and type afw#mobicontrol and the agent google entreprise is well downloaded and after i enter the code to enroll device to mobicontrol, The result is, device is enroll into management type -> Work Managed device -> PERFECT All seems to work, remote connexion, install profile, rules, and so on ... If i take an other new device OUT of the box, take the same agent from mobicontrol (v 15.4.4.1063), copy paste the agent, install agent, enroll device into mobicontrol. The result device is enroll into management type -> Work managed profile -> BAD Because, we notice there is two " path " on the device (professionnel / personnel), if we starts a remote control (name is remote view), end user need to ACCEPT the permission before the remote , problem with rules, ... We don t want to enroll device as a work profile ..because we notice, this mode can be too much restrictif for us and perhaps lose time when we meet some incident .. My question is, is it possible to enroll device into management type Work Managed device when the device has been initialize ? Because if i copy paste the agent soti 15.4.4.1063 , install it, the device is enroll into work profile .. a command exist perhpas or something else ? thanks for your time
I have a TC70x GMS device on Oreo. Installed MobiControl using StageNow, but it is always enrolled as Work Profile. How do I make sure it's enrolled as Work Managed? Enrollment ID has previously worked in the past. We use on-premise server, but we currently have this device at home using a VPN that has access to the on-premise server. Could it be why it keeps enrolling as Work Profile now?
Hi everyone, since there's no possibility to configure native VPN on Work Profile devices (COPE), we let the users configure their VPN settings on their own. We are pushing a device certificate via MobiControl. On fully managed (COBO) devices, the user is able to select this certificate in the VPN settings. Unfortunately, the user cannot do this on COPE devices, because the work profile has its own certificate store where the user doesn't have access to. Does anybody know how we can solve this problem?
Top-tier experts who are delivering outstanding content. Should have more than 7000 points.
Experts who are consistent with great content. Should have more than 1000 points
Highly experienced members with valuable inputs. Should have more than 700 points
Beginners taking the initiative. Should have more than 500 points
