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.
Hello, I'm unable to enroll my TC72 on Android 11 to SOTI. After StageNow auto populated the enrollment ID, it returned "Enrollment Failed" message. We have used the same process and enrollment ID for our other devices, A10 and below. I'm wondering if there are known issues with Android 11 enrollment? Our current MC version is rather old (14.3.4.1087) and I'm wondering if A11 is just not compatible with older console version? I'm thinking of downgrading from A11 to A10. However, I'm still unsure if this is the best approach?
I'm trying to install SOTI MobiControl as a fully managed device to my new Zebra TC72 Android 11. We have to be connected to the company's network/wifi in order to enroll SOTI in the past and we used StageNow to install. However, this time I'm doing this remotely from home. So, I had to install Cisco AnyConnect first to connect to VPN out of the box then install SOTI using an external SD card. It was installed successfully, but I was prompted to create a work profile. Is there a way to install it as a work managed while connected to VPN? Or was it me installing AnyConnect that was causing the work profile? Note: Our SOTI MobiControl version is: 14.3.4.1087
Hello everyone, After upgrading a couple of our Zebra TC8300 scanners to Android 11, we've encountered an issue with the Zebra RDP (Remote Desktop Protocol) application on one of the devices. when we opening the application, getting an error "unable to read config file". Typically, the config file is located at "/sdcard/Android/data/com.symbol.remotedesktop/files/MotoRDP.xml". i did the manual verification, and unable to locate the "com.symbol.remotedesktop" folder on the affected device. even tried a factory reset, but the issue persists. Interestingly, other scanners of the same model and version that underwent the upgrade are working fine, and we i can see the folder and config file on those devices. Has anyone else experienced a similar issue or have any thoughts on how to resolve it? Any help or suggestions would be greatly appreciated. Thank you.
Hi, Do we have a script that can run a delta os downgrade. Scenario for example, if a May release of android 11 made one of my application problematic and I need to rollback to an April delta update while I investigate the issue. I have copied over a OS file via filesync and ran the script install_system_update /sdcard/Downgrade.zip - I get the message failed to install. I tried install_system_downgrade /sdcard/Downgrade.zip - nothing happens. I tried sendintent -b "intent:#Intent;action=com.symbol.intent.action.UPDATE_PACKAGE;S.file=/sdcard/Downgrade.zip;end" nothing happens LIFEGUARD UPDATE 11-35-05.00-RG-U00 + Full UpdateRelease Date: May 2023+ Delta Update (Applicable To 11-31-27.00-RG-U06)Release Date: May 2023 LIFEGUARD UPDATE 11-31-27.00-RG-U06 + Full UpdateRelease Date: April 2023+ Delta Update (Applicable To 11-31-27.00-RG-U02)
HiI've noticed that some devices that I've enrolled recently do not show the MAC address of the device in the Mobicontrol device details. I use this information to be displayed on the Lockdown screen for support reasons since the MAC address is used in the firewall.MAC randomization is off. Both are running the same Agent version (15.3.3.1069) and are the same OEM version (11-20-18.00-RG-U00-STD-HEL-04) Mobicontrol version: 15.6
Hi all, We've a customer who had a couple of TC21 devices sent to Zebra for repair, when it left it was an Android 10, and when it returned, an Android 11. Before it left the time and battery percentage were displayed in the notification bar, see image with.png. But now it is not displayed, see image without.png. We've also lost the Home and Recent Apps soft buttons. The devices are all in the same folder and so have the same lock down settings/feature control etc. And when switching to Admin Mode (out of the lockdown) everything displayed as expected. Agent Version 15.3.0. Build 1006 * Have to use imagination, image upload not working
Hello, Since update HE_FULL_UPDATE_11-20-18.00-RG-U00-STD-HEL-04 the “BEAM” is not working within the Soti lockscreen. Before with HE_FULL_UPDATE_11-16-05.00-RG-U11-STD-HEL-04 the “beam” is working in the Soti lockscreen. Outside the lockscreen the “beam” is working fine. Situation: Our scanners are rolled out in Mobicontrol (Version: 15.4.1.4828). The scanners have 2 applications 1 APK and 1 SAAS application (webapplication) the Webapplication is configured with https:// in the lockscreen In the APK application the scanner beam works fine. But when we open our https application we can’t trigger the scanner. The keyboard pops up when you press an input field. (still not able to scan something) Hope someone over here know how to solve this issue. now we are downgrading the scanners Kr, Robbert
I am demoing a Zebra VC8300/VC83x that shipped with Android 11. I can't say it's going as well as any previous new device. I've used StageNow to generate barcodes and xml files to adjust screen time outs, wifi preferences etc and NOTHING is changing. If I send this legacyt script things do change immediately - do I need to migrate EVERYTHING to writesecuresetting on Android11 or is this device just acting up. To match the fun, if I type the wifi password wrong during initial setup, it boot loops for almost 3 hours before it recovers itself - so it's possible the OS build on this device is just not right - and there are no updates available for it since May 2021. Here is what is working so far. writesecuresetting -sys SCREEN_BRIGHTNESS_MODE_MANUAL 1writesecuresetting -sys SCREEN_BRIGHTNESS 255writesecuresetting -sys screen_off_timeout 1800000
Hi there, I`m facing a issue regarding Samsung Galaxy Xcover 5. I`ve installed an application that monitor the fleet but the users find a way to exit from it and now they have access to google search bar(marked withe the red line) and some apps like google play, google, setting and it`s not ok. I didn`t find a way to block this security breach. As you may find in the picture below, the term "Cautare" means "Google search bar" and "Inchidere totala" means "Close All". The user should`nt have the possibility to leave the app and see these options(search bar and apps). Agent version: 14.5.5, but I`ve tried even with older agent versions but I`m facing the same issue. OS version it`s Android 11, One UI 3.1. Please let me know what to do in order to block the user to leave the main application. Thank you very much for your support.
Can anyone verify if Mobicontrol v13.4 supports Android 11 devices? We're currently running a mix of 7.1 and 8.1 Android devices. One of our sites is pressed for devices and are looking at Zebra TC72s running Android 11. We're unsure if there are any upper limits on what Mobi v13.4 supports. I don't foresee any issues with Android 11 devices using the same AFW profiles that our 8.1 devices use, but it's always nice to get a confirmation.
Hello, has anyone encounter the issue where the backbround service & agent only start if the device was once unlocked after a restart?
Good Morning, Our company is in the process of upgrading our employee's devices. The current tablets we use are the Samsung SMT387 & M-T378. We enroll them with Android Plus and push out a profile with Kiosk screen and several packaged APK's for the approved apps. We recently ordered the Samsung A7 lite devices SM-T227U. These come with Android 11 out of the box. I was able to enroll the device with Android Plus. When I went to push our test profile (Exact clone of Production Profile) the entire profile failed. All my packages failed to install with the message being "Failed to Install (Incompatible Platform)". Is there something different I will need to do with the enrollment to get these new Android 11 devices to work with our current profile? MobiControl version: 14.4.6.1047 Agent Version: 14.1.4.1010
hello, we are trying to install the lockdown menu on an samsung tablet with android 11 but i allways get the message "pending action" "please give draw over other apps permission". when i try to set the permission by pressing the message nothing happens. i tried it by script with afw_set_permission_grant_state net.soti.mobicontrol.androidwork net.soti.mobicontrol.permission.SYSTEM_ALERT_WINDOW allow afw_set_permission_grant_state net.soti.mobicontrol.androidwork android.permission.DRAW_OVER_PERMISSION allow no effect. i changed the parameters in the add device rule.... no effect. any idea ? thx mark
Hi everyone, Currently i deploy around 200 A01 device for my client, and i just found out that after 2 device update to Android 11, we no longer can Remote Control the device (A01 not supported by Knox, only ELM). We can only do Remote View. Since RC is integral feature for my client, is there a proper way to prevent or completely disable Update in Samsung A01 device? Currently i se postpone feature in Profile to prevent update, but the postpone option only can postpone for 60 days. Any help is welcome :) Thanks & regards, Randy Saputra
We have received some A32 to be enrolled in our MC 14.4.4.1045. After we set the afw#mobicontrol it starts to download the MC Agent (now it is 14.5.3.....) At this time we receive a message telling the Operational System is not original. (It is not possible to create the work profile. The security policies denies to create a managed work device, because a customized Operational System is or has been installed on this device). The OEM Version of it looks as original (RP1A.200720.012.A325FXXU1AUF2) The mobile is just out of the box. As it is Android 11, we are enforced to grant permissions individually to the Agent, before it goes on (access any file, manage system and so on). If we go forward the Agent install but at the time to create the google account, it hangs on the PlayStore account requesting to recreate account by identity confirmation: (Confirm who yo are. You log off google account , please log in to continue). On the next screen it does not allow to type in any entry. And Click on next, it fails. After hanging in this screen, we have tried to go by download the MC Agent from the server. Then we have proceed by a factory reset and skip google account. Installed the agent by our server. The issue starts as it comes as Android instead of Android Enterprise(the download agent was Enterprise). And again, it does not create the google account, presenting the screen as pending action to create a work profile in the device. (Work Profile Provisioning. Click Here to configure a work profile). It never creates the work profile as the click had no effect. Has anyone had a good installation for Samsung A32 ?
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
