There's a new home for Articles. Find Articles on Our Product Support Page.
Dear Community! Please help me. I'd like to enroll a Zebra MC3300, but "Enrollment failed". Parameters: Android 8.1 - Build number: 02-32-04-.00-OG-U001-STD SOTI Android Enterprise Agent: GoogleMobiControl1444_1051 VERY IMPORTANT: the Remote Control feature is necessary!!! I have no idea how can I manage the correct enrollment, earlier I had some success enrollment with this MC3300 device but only with Work Profile, only Remote View feature. Thanks in advance. Regards: SN
Hello, has anyone problems with FileSync Rules after Upgrading to MC 15.3 ? I have already in two installations the issue that the AE Agent goes immediately offline if there is a filesync rule targeting the device. The FileSync Rule was already existing and working in MC 15.2.4 (transfering OSUpdates to Zebra Android Devices) Agent Versions tested: 14.4.3 and 14.4.4Devices: Zebra WT6000 (Android 7.1) and Zebra MC33 (Android 8.1) Devices connects with Server and immediatly closes the connection, and this is all couple of seconds. As soon as the FileSync Rule is disabled, the device agent connects and stays connected. greetingsMartin
Hey Guys, Can someone tell me the script to downgrade a MC93 from Android 10 to Android 8.1. The .zip files is already placed on the device. I need it for every Zebra device which is usable with Android 8.1 and Android 10. Thanks for your help! Looking forward to some answers :)
I do not believe there is a way at this time but I would like to see if we would be able to customize some of the settings when it comes to sending messages via SOTI. I have seen issues with a back log of device messages when the users are sending messages to devices as they are always using the "Until user presses OK" option. I would like to restrict some of those choices without loosing the ability to send messages. Additionally If I could restrict the "Queue message for delivery to offline devices" While I understand that this is solely user driven it would be a great help.
Hello, Our set up - Mobicontrol Enterprise, Agent Version: 14.4.4.1051, on Android OS for Galaxy A10e, A11, and A21. Issue: Display Timesout randomly. At the time of the screen display going unresponsive and goes black, mobicontrol's logs report device disconnected and then return connection once unlocked. Please note the phone locks when the screen times out during use of SOTI Surf, Email (Outlook), or any application. I've worked with the SOTI support team on this error since May. I have not found a resolution to this issue and it has affected every phone in production.Some fixes attempted: Go to group details - connection settings - set to max retry connection to 3600 s. Go to Authentication profile - select authetication policy - select user password policy - select maximum screen timeout to 99 Minutes Adjust mobicontrol settings manager to never. We've tried implementing all of these fixes in our current server and non of them have been reported as a working solution since the timeout error continues to occur. Please help as soon as possible. This is negatively affecting our employees. Thank you, Zahra
Hello all, I have the following scenario with a customer. He is using a MobiControl on premise installation, version 15.1.1, in his internal network. Currently every MC part is installed on one main server (Deployment Server, Management Server, SQL DB). He wants to add a second Deployment Server in his DMZ to make the SOTI MC environment externally available. I installed and configured a lot of SOTI MC servers in the past but never added a second Deployment Server to an existing one. The question is, are there any things to keep in mind while installing a second Deployment Server? I am aware of opening ports between the main server and the second server and installing the Deployment Server with the SOTI MC 15.1.1 installation setup on the second server (only with the Deployment Server checked in the setup). Thank you in advance for your answer!
I am attempting to configure SOTI to issue certificates to be utilized during 802.1x authentication. I am unable to create a certificate template within SOTI which would be a requirement to issue these certificates from our internal CA server via SCEP. I found a guide located at this url: https://www.soti.net/mc/help/v15.1/en/console/system/certificates/add.html , however this seems outdated as there is no "Certificate Authorities" section with a wrench next to it at the stated screen. Is there an updated guide to configure MobiControl cloud for this purpose?
There are several events on DS that reports the device to switch into user mode, without a previous switch to admin mode. Most of them looks as being reported early in the morning (probably on devices turning on) Is there a way to end user switch to admin mode and prevent to dispatch events or erase them before being sent to DS ?
There are 2 DS running on MC 14.4.4 that manages 4200 Android devices. According to Advanced configuration we have set DS server priorities different for a subset of devices. It guides half of devices to connect in DS1 and half in DS2. One of the DS is always with many itens queued (around 1000) and other is almost none. We have tried to invert the server priorities and the behavior of queue size follow it. Both subset of devices has rules and profiles locked by kiosks. Is there any way to see what kind of task is in the DS queue? In positive way, we would be able to review the rule/profile or split the subset in a different way.
Hello has anyone already upgraded to Mobicontrol 15.3? (on-premise)? There were some issues after installation, but were fixed in MCadmin. Main trouble is some menu items are unavailalble/blank -> e.g Rules,Reports.. its shown just empty window: like the older portal is not available at all (as it was in 15.2.3). Im considering a rollback. thanks Tomas
Good morning: Could some one explain me how this works? If i m press this buttons, nothing happens. Is a background process? How is configured? Thanks in advance
Hi all, I've read information from a previous post about AE Work Profiles, but I'm not sure if it applies to our context so I would need your feedback. https://discussions.soti.net/thread/android-enterprise-device-1/ We have a group of users that have Samsung S9 devices. These are corporate owned devices but can be used also as personal. We created a rule where those units will be ''Enroll fully managed with a work profile''. In this case, there's a Personal and Work container. When we wipe (with bypass factory reset protection) the device then re-enroll it, it ask us to enter the personal account of the user. That's were we don't understand, as there's already a Managed Google Play account in this rule, which should be mandatory to enter again into those corporate owned mobiles. We use afw#mobicontrol in the initial steps and our platform version is 15.3
I am trying to configure a Lockdown profile on MobiControlCloud version 15.1.2.1035, for a Samsung A20e (Android 10) that includes Launch://com.samsung.android.dialer as a home screen item. However when the profile is applied and the phone dialler appears on the screen, as I attempt to call the dialled number, nothing happens. If I do not have the lockdown profile applied, I can make the phone call without issue. Am I missing something? This process worked on MobiControl 13.3.0.3851 and a Samsung A20e with Android 9 Cheers
Can anyone tell me what the Script Command read_activities does?I've tried it on various packages, but no return in logs or so.AEDOAgent version : 14.4.4.1051Mobicontrol version : 15.2.5 Source : https://www.soti.net/mc/help/v15.2/en/scriptcmds/reference/androidplus_enterprise_do.html?hl=script%2Ccommands%2Candroid%2Centerprise%3A%2Cmanaged%2Cdevices
Hi Community! Anyone can help me set up a file sync rule on the Xiaomi Redmi 9AT? I use several rules like this: But it won't work on this phone. I've tried every options in the setup screen (%sdcard%...etc) but neither of them works. If i open file manager on the phone and check the files path, I see /storage/emulated/0/DCIM/Camera but that path won't work either: Any help is appreciated.
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.
New contributors starting their journey. Should have more than 250 points.
