There's a new home for Articles. Find Articles on Our Product Support Page.
Greetings, So for the last couple of months we have noticed that some of our TC72 (Android 11) just stops checking in on the agent, and therefore we will not see the device online in SOTI MobiControl anymore, or atleast until the device has been rebooted. From what I can see on the logs of our devices, most of them disconnect around the same timeframe (02:05 at midnight) and will first check in again after a reboot. What could cause this? We have only seen this happen after we have upgraded all of our TC72 to Android 11 from Android 10. The devices are connected to the network and can use websites in our lockdown state without issue. On active use our devices only use around 50% of the RAM and still has 14GB storage free.Thanks in advance.
Hi all, I'm getting a meesage that says 'No apps can perform this action' when I try to install apps from the catalogue in MobiControl. Honeywell CT-60 Agent 15.4.4 Build 1063 Active MDM API - AAP 1.18, 1.19 It's strange as it worked fine whilst on a call, then it worked one one device afterwards but now nothing. Thanks, Karl.
On A13 (Zebra TC73) its always on and we observe that its slowing down the device. Is there a way/script to make it disabled?
Hello, is there a device script to execute a lifeguard OTA update if one is available?
Hello, all of our devices disconnect and connect at 1am. Why is this? Best, Eduard
It seems that MC APIs use swagger. I was able to locate the swagger.json config file at ``/MobiControl/api/swagger/v2/swagger.json`` however I'm struggling to compile the client libraries for Kotlin. I'm using: swagger-codegen generate -l kotlin-client -v -i swagger.json --api-package dev.antoniocalabrese.mobicontrol.api --model-package dev.antoniocalabrese.mobicontrol.data Also tried: openapi-generator generate -i ./swagger.json -g kotlin With the second command I get some errors with the config validation: org.openapitools.codegen.SpecValidationException: There were issues with the specification. The option can be disabled via validateSpec (Maven/Gradle) or --skip-validate-spec (CLI). | Error count: 3, Warning count: 297Errors: -attribute paths.'/devices/{deviceId}/profiles/{profileId}/actions'(post).[action].x-enumType is unexpected -attribute paths.'/security/currentUser/eulaStatus'(put).[eulaStatus].x-enumType is unexpected -attribute paths.'/devicegroups/{path}/icon'(put).[newIcon].x-enumType is unexpected The first command executes but then gradle fails to build the library. Has anyone ever successfully tried to do something similar?
Hi, we use Android 13 on TC21 and 53. Now we want roll out an WIfi profile. Our system use an MAC filter. Now we have the problem that after run the profile with the correct wifi settings the Android system is used randomized mac adress. Is there an possibility to change the settings in the profile to : "use Device Mac" as default?
Hi All,We have 600 brand new Samsung Galaxy A14 devices. I need to enroll them in SOTI like all our other devices however are not having much luck. We have staged these device types before with no issues however we are having a great deal of trouble at the moment.Issue;When we scan a QR code generated via Stage Programmer app the device will show "Getting your device ready..." or "Just a sec..." this will sit for 3 - 5 minutes before finally showing only a white screen with a little black arrow bottom left hand corner.When you press this arrow you only have a reset device option and nothing more.Resolution attempts;I've tried pointing the device to different WIFI networks / using cellular / using different enrolment ID's / enrolment direct URL / using no enrolment what so ever. Any help here would be appreciatedThanks
How do i create a deployment rule and package for a CK65? For all other device types / OS i have the "add device" option but not for Android. Due to how my corporate network is configured, i have to be able to deploy without accessing the play store.
Hello everyone, I recently discovered something on our Android 8 Zebra devices. I observed it on the TC56 and MC3300 models. There's a floating Home button on the screen, present with and without the EHS lockdown. I have other Android 8 devices that don't have that button, If i click that button, mobicontrol crash and i lost connection for couples seconde on the device and i can log back with soti. I'm not sure if the agent is the problem, but it's the only difference in my configuration. All other profiles are the same. Is it possible that the agent is the source of my problem? How can I get rid of the icon? Thanks for any suggestion !
Hello, If we enroll the CK75 with the APK "IntermecMobiControlIntermec-15.2.0.1025.apk" after finiching we get an error "Unforunately mobicontrol has stopped". Actually we are installing the agent version 14.5.5.1023 then making the upgrade of the agent to the version 15.2.0.1025 and it works fine (very rarely we get the error mentioned above) do you have a solution to enroll the devices with the latest version without getting such issue Thanks Amine
Hi, Has anyone experienced the same thing, some of our Samsung devices that use the latest agent version 15.4.4.1063 can't connect to the server and after I check the device details it appears like this.
I am looking for to get details of unenrolled devices. is there any log or report to get this information use case: after unenroll and delete a device from the console there are no way to check the existed device name.
Hello, We would avoid to swipe up the screen when you open the device and also when the device is on hold. From our side we are able to disable the SWIPE UP with Stage Now in the TC57, but the question is how to disbale the SWIPE UP with SOTI like a script or anything else. Device is ZEBRA TC57 managed by SOTI 14 Thank you for your assist. Regards, François
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.
