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.
Device (samsung tablet) has been enrolled in a group(warehouse location) with that groups own policies and app rules. Device is need else where at another warehouse so the tablet is moved to another group (new warehouse) on the View Devices screen. How do I get the (old warehouse) old group's rules, polies and enrollment removed from the device and the new group's (new warehouse) access transferred to the device without having to factory reset and start over with correct enrollment id? These groups/warehouses also have their own google play accounts. Right now everything is working except the app policies. The new group's applications state "package not found." When looking at the config, the app policy is missing even though it has been reassigned. version 15.4
Hi all,At the moment I am working on our Honeywell CK65's where I am trying to use the mcsetup.ini file to envoke the enrollment URL after provisioning it with Honeywell Provisioner. Is there a way to get this working so that the device can be setup in a one step process ? We have transfered mcsetup.ini /sd/download using honeywell provisioner can we specify the enrollment in honeywell or in the mcsetup.ini we cannot use enrollment ID as our enviorment is fully isolated from the internet.Thanks in advance.
Hi We are using the zero touch configuration to enroll our TC21 devices. Unfortunately lately, this is causing problems. We have to manually un-enroll & enroll a device first before it will receice any profiles. OS Version: 11 Agent Version: 15.3.3 (doesn't change when enrolling again) Management Type: First enrollment -> "Unknown", second enrollment ->Work Managed device (as it should be) Whenever the Management Type is on Unknown, the device will not receive profiles as there is no communication. Another thing I notice when doing the enrollment the second time is that "Mobicontrol A+ Service" is immediately installed. (This doesn't happen on first enrollment) and then everything is working properly. The config that is used at the zero touch; (wasn't changed for the last years...) {"android.app.extra.PROVISIONING_LEAVE_ALL_SYSTEM_APPS_ENABLED":true,"android.app.extra.PROVISIONING_ADMIN_EXTRAS_BUNDLE":{ "enrollmentId": "" }}
Hello community,The Enrollment certificate was valid until 09/25/2022 and I don't get any info about it expiring.To find under Global Setting / Certificate Authority-> "my-sotimc_server.com/MobiControl/WebConsole/home/global-settings/CertificateAuthority"1st problem - How do I get an info about the expiration of the certificate? 2nd problem - How can I exchange it here it comes again and again to errors.
Hello, Our android terminals do not appear in the soti management console, but they are present in the enrollment server logs. The soti agent indeed displays a green rolled-up status, with the correct domain information. In the Mobicontrol server reports, it is clearly displayed that a new terminal is enrolled, but this one does not appear in the management console. Also the configuration does not apply to the terminal which is however noted as being enrolled. We have already managed to enroll terminals in the past but it no longer works. We tried with an android 12 version (samsung galaxy s22) and a Zebra mc93 terminal with android 10 without success Our instance of MobiControl, is on-premises. SOTI mobicontrol : Version: 15.1.2.1035 Can you help us?Thanks !
Hi Everyone, I have a problem when I enroll device to soti mobicontrol. Enroll is successful but the profile that we push does not enter the device. and I also check the device details, there is no information on supported apis. may i know why?
Hello, I would like to know how would you prevent users from deleting SOTI profiles in Apple devices? This is in an effort to avoid device unenrollment. Kind regards, Kevin O.
Hi. So what's the purpose of assigning a Deactivation Date to an Enrollment Policy? I am testing it and it did deactivate as expected but the device still functions properly. Can someone provide a quick usecase for using this feature? Thanks for your time.
Hi, has anyone experienced difficulties in enrolling a device such that it becomes "Non-Compliant"? This is a Zebra TC21, running Android 10, MX 10.4. Enrollment fails, the device DOES end up in the device list however, but cannot be controlled via Soti at all. The enrollment process on the device gives an error. We've tried to enroll on the latest version of the Soti Mobicontrol server, as well as on 15.4. Regards,Daníel
Hello guys, I have a little question. We are enrolling old MC92 with WinCE to a MobiControl 15.5 server on premise. Everything works fine but lately we got one device which doesn´t connect to the server. I got the following logs: Can somebody explain to me what this line means: 2022-07-08 10:26:23,939 (0x00001f48) [ERROR] No Device found with device Id: 73E65B7606490108000A-08C074620600Thanks for your help!
Hello @All, as stated in the article below, there are a few more restrictions with Android 11: https://discussions.soti.net/articles/impact-of-android-11-scoped-storage-restrictions-on-android-agent The main one that really hinders our staging process is that you arent able to use mcsetup.ini anymore. Has anyone gotten the agent Version 15.1.2 on Android 11 to accept mcsetup.ini? Any additional manual step i.e. scanning or putting in the enrollment id is "annoying" in the whole staging process. Combining Honeywell Enterprise Provisioner or Zebra MX with mcsetup.ini was a nearly 1 step process to enroll and stage a device for us. Any ideas appreciated.
Hi All, Accidentally deleted my original post when trying to post a fix... so apologies to all that was following my other post Quick Background Since upgrading MobiControl to v15.4 we notice an issue with direct downloading the agent when trying to enroll a device. We would constantly get the following error when we hit the download button on the mobile device when enrolling and it would fail This is a fix for that issue that worked for me. So use this at your own risk. I will summarise the fix, so if you need a bit more info let me know as it can get technical For this fix, you will need to be able to access and edit your SQL database for MobiControl
I am looking for a good method to enroll my ZEBRA VC8300 terminal to a SOTI Mobicontrol console. Currently my method does not seem optimized, after a FactoryReset, I pass all the first steps manually (human action) Once started under the "Home" Android menu, I have to activate the serial port of the machine from the APP "VC Setting" in order to use a scanner and thus the StageNow application to finish my enrollment. The two problems that block the usual method, from the first menu after a FactoryReset : The Google enrollment menu (7 taps from the start menu) does not seem to work, due to the fact that the machine does not have a camera. If I connect a scanner in USB, the reading of the QrCode "ByPass GMS Setup Wizard" which allows me to pass the first steps and launch StageNow does not work. an idea?
hello, we are using mc to manage round 15.000 zebra devices for our drivers and warehouse emplyees. our consumer products like apple iphone or samsung galaxy smartphones are managed by mobileiron. there its possible to enroll the devices user based, the user got an activation link and have to login with his ldap or azure ad credentials to start the enrollment, after this the device is enrolled and assigned directly to the user. for the future it's planned to use only one management plattform but i cant found this option in MC. is it possible to enroll devices user based or not ? thx in advance mark
We are taking on a ne group of devices which are currently on Airwatch. The customer does not want to do any interaction with thedevice to enroll Mobi. They want to setup a package on Airwatch and then have teh APK auto install and activate all options required. Basically they don't want the device user to have to be involved in anyway, There are 2 parts to this.1. Creating a package on Airwatch that will install the mobi apk (Samsung ELM). I believe the best way for this may be using the .apk and the .ini. We don't currently have access to or any experience with Airwatch so that is probably not a question for here.2. Have the apk launched from Airwatch and then run through the install process. We can't have any questions from either the os or the app. Using the .ini this should eliminate the need to input the enrolment id. We still have to accept all permissions and run though a lit of settings on the device. Is there any way around this so that the apk will install, pickup what it needs from the ini and just run and activate silently? Can anyone help with either part but really part 2. Please and thank you. EDIT: We are using Android Plus classic, not enterprise.
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.
