Community - SOTI MobiControl

Community - SOTI MobiControl

There's a new home for Articles. Find Articles on Our Product Support Page.

SOTI MobiControl Discussions


  • 1 votes 2 answers

    Zebra OEM Config causing Wifi to drop repeatedly every time settings are applied

    My Mobicontrol server is offline and so I have no enterprise binding. Using Mobicontrol I have deployed Zebra OEM config (com.zebra.oemconfig.release) to Android 13-14 Zebra scanners in my enviroment specifically to apply Datawedge settings as it was recomended by Zebra since using  MXCONFIG with a StageNow XML is deprecated.The managed configuration transaction items inlclude downloading the datawedge.db and applying it.  All other configuration items are left blank or "do not change" is set.  This feature is working just fine. I am seeing a serious issue with all devices that I have deployed OEM config to.  Every time the device re-applies OEM Config's transactions it is repeatedly disconnected from Wifi.  Once it is finished applying the connection is stable again for an hour or so.  Then the issue loops.  Has anyone encountered this issue or have any recomendations?

    SOTI MobiControl
    24 days ago
  • 0 votes 5 answers

    Shared Device - Autologout on Reboot

    Hi all,  we have set a new shared device group and it is needed that the Devices will log off the user automatically on restart / reboot the device.  Gives there any option to set it in Mobicontrol? (standard logout scheduler after a period or on inactivity is not practical) Gives a command or intend to app to force logoff via script? Gives an MX / Stagenow / XML command? Background is, we fear that users will forget their device password and will no longer be able to unlock their device and log themselves out. This way, users have the option to help themselves, restart their device, log in again, and create a new password.  Server is MC 2024.1.1.1058, Agent is 2025.0.2.1045, Device ET65 Thanks Henry

    Android Scripting
    a month ago
  • 0 votes 5 answers

    SOTI Shared Device - Device not returning to Pre-Lockdown group

    Hello,We are piloting the Shared Device mode in SOTIThe device group has Shared Device configuration enabled.It is set to Move to the Post-Lockdown Group, and when signed out it returns to the Pre-lockdown group.Timeout for logged in user is 13 hours (After which the user is forced logout).Timeout for inactivity is set to 4 hours (After which the user is forced logout).Data to clear on signout.This is generally working fineHowever have noticed the following:Somehow, the user on the device is logged out, but the device did not move back to the Pre-lockdown group. The device is still in the Post-Lockdown group which means its showing the main app screen, not signed in, no PIN (cleared). Allowing anyone to walk by and use the device.How can this happen if the configuration specifies that, when logged out, it should return to the Pre-Lockdown folder?Restarting the device does not move it back.Log Out Shared Device device action does nothing becaue there is no logged in user.The only way to solve this, is if I manually move the device back into the Pre-Lockdown folder.  We have a lot of devices and this seems like it will become a bigger issue down the line.I have raised a case with SOTI support, but though I might reachout here also to see if there is anything else I can do from my end.

    SOTI MobiControl
    a month ago
  • 0 votes 3 answers

    Issues with the /packages/v2 API when uploading APKs

    Hi all, We are trying to upload an APK to a SOTI MobiControl package, but we are unable to do so. We are using the following script: ####### #!/bin/bash SERVER_URL="https://<SERVER_HERE>.mobicontrol.cloud/MobiControl/api/packages/v2" API_TOKEN="TOKEN_HERE" PACKAGE_NAME="0_APK_Package" PACKAGE_VERSION="1.0.0" PACKAGE_PLATFORM="AndroidPlus" APK_FILE="App1.apk" BOUNDARY="test" # Check if the APK file exists if [ ! -f "$APK_FILE" ]; then echo "ERROR: File $APK_FILE not found in the current directory." exit 1 fi echo "Uploading package to SOTI MobiControl..." # Build the multipart body and pass it directly to curl ( # 1. Part: JSON metadata printf -- "--%s\r\n" "$BOUNDARY" printf "Content-Type: application/vnd.soti.mobicontrol.packagearchive.metadata+json\r\n\r\n"   cat <<END_JSON { "PackageName": "$PACKAGE_NAME", "PackageVersion": "$PACKAGE_VERSION", "PackagePlatform": "$PACKAGE_PLATFORM", "PackageFiles": [ { "FileName": "$APK_FILE", "FileSourceType": "Binary", "Destination": "%sdcard%", "FileFlags": "DoNotUninstall, AllowUserUninstall" } ] } END_JSON # 2. Part: APK file (binary) printf -- "\r\n--%s\r\n" "$BOUNDARY" printf "Content-Type: application/octet-stream\r\n" printf "Content-Transfer-Encoding: binary\r\n" printf 'Content-Disposition: attachment; filename="%s"\r\n\r\n' "$APK_FILE"   # Inject the actual binary content of the APK cat "$APK_FILE"   # 3. Close the multipart printf -- "\r\n--%s--\r\n" "$BOUNDARY" ) | curl -v -X POST "$SERVER_URL" \ -H "Accept: application/json" \ -H "Authorization: Bearer $API_TOKEN" \ -H "Content-Type: multipart/related; boundary=$BOUNDARY" \ --data-binary @- echo echo "Process completed." ####### When we execute it, the request returns HTTP/2 200. However, when we check the package in MobiControl, the Files tab does not show the uploaded APK: Do you have any idea why this might be happening? Thanks in advance.

    SOTI MobiControl
    a month ago
  • 0 votes 4 answers

    SOTI Shared Device - Dynamic Android Template - Badge Notifications

    Hi all,Has anyone managed to get badge notifications to work on their Lockdown screens? Is this feature supported?  

    SOTI MobiControl
    a month ago
  • 0 votes 3 answers

    Issues with package/v2 api and post-install script Solved

    Hi everyone, I am currently on MobiControl version 2025.1.0.1007. I am strictly an Android Shop with devices ranging from OS 10-15. Device Agent version(s) 2024.1.4.1149 through 2026.0.0.1104. I am attemping to use a python script to make the POST packages/v2 api call. I have no issue with the creation and upload of the created package. I am running into an issue when trying to get the files in the package copied to the correct folder/folders on the Samsung device. I have tried using a post-install script (I referenced the Android Agent JavaScript documentation) but for whatever reason, I can not get the files on the device. I find it strange that this isn't working since the profile status states that the package was installed successfully. When I check the file structure, no files are copied into the specified directories. I have even tried adding the PackageGroupFile and PackageFileFlags parameters in the script but still no luck. I was wondering if anyone else had any luck using this API call to build -> upload ->deploy successfully. The files in question are files that are generated in ESI. Building the same package in Pack Studio works without fail. I am wondering if I am missing something crucial. Any help would be greatly appriciated. Thank you. If any other information is needed, I would be happy to discuss.

    SOTI MobiControl
    a month ago
  • 2 votes 5 answers

    SOTI Shared Device - Login Transition

    Hello, Currently we are trialing the Shared Device mode in SOTI using Samsung android tablets. We have set up both Login Pre-lockdown and Post-lockdown profiles. And configured the Shared Device mode details using Entra SSO etc. When you click the Login icon, it brings up the O365 username and password screen. After entering your details for SSO and signing in, the screen disappears and briefly shows the Login screen again. Then, you are prompted to enter your session PIN. Once you enter the PIN, it returns to the Login screen. The main issue is that it takes about 5 to 10 seconds for the device to sign in and switch to the Post-lockdown profile. Our staff are getting confused because sometimes the session PIN prompt doesn’t appear, or after entering the PIN, there’s a 5-10 second delay, making them think nothing is happening, so they click Login again. Is it possible to add a transition screen after setting a PIN, such as a “Loading” or “Please wait” message?Thanks

    SOTI MobiControl
    a month ago
  • 0 votes 6 answers

    Possibility to force OTA installation

    Hello,   is there an possibility to force the download and installation of OTA via Soti 2024.1.2.1046. With force i mean The OTA process on the device start immediately with download and installation and not "12h" later..  only Zebra Enterprise devices. Kind regards   Günter

    SOTI MobiControl
    2 months ago
  • 0 votes 3 answers

    Custom log (Mx OTA failed- trying to update Android 11 Device

    Hi, I've got a Zebra MC3300ax devices with the Version 11-20-18.00-RG-U00-STD-HEL-04 that i am trying to update up to 14-32-12.00-UG-U03-STD-HEL-04   Version, i have copied the file with File sync to a set location and once it is done i have sent the script (Type Legacy) : install_system_update /sdcard/update/HE_FULL_UPDATE_14-32-12.00-UG-U03-STD-HEL-04.zip to which i get the log error Custom log (Mx OTA failed:  Any idea what could be the cause of this? i have tried moving the file to diffrent locations and even diffrent update files to slightly lower versions but it always give the same error. Best Regards, Bar

    Android
    2 months ago
  • 0 votes 3 answers

    Hostname for Android device without OEM config Solved Locked

    Hello, we have certain devices, which does not have a OEM configuration profile available in the SOTI profile. Is there a way to set the hostname of the device via script or any other means? Best, Eduard

    SOTI MobiControl
    3 months ago
  • 0 votes 6 answers

    allow sideloaded app updates in kiosk mode Solved Locked

    Hey there, I've got a problem with a single-app Kiosk Mode profile on Soti MobiControl. I've set up a profile to lock a device down to a single, custom Android app. This app was manually installed via an APK file, not from the Google Play Store. The app has its own built-in self-update feature. However, the Kiosk Mode profile seems to be blocking these updates. The app on the device remains on the original version that was installed and never gets updated, even when it tries to update itself. I need to find a way to allow this self-updating process for the app while the device remains in Kiosk Mode. My question is: What specific configuration or script is needed in Soti MobiControl to allow an internally self-updating APK to function correctly while in a single-app Kiosk Mode profile? I'm looking for a solution that avoids disabling Kiosk Mode or manually updating the APK every time. Any insights or workarounds would be greatly appreciated. Thanks for the help!

    SOTI MobiControl
    3 months ago
  • 0 votes 3 answers

    PowerBI on Lockdown Solved

    What is the simplest way to setup a PowerBI report on the lockscreen?  The report cannot be published to the web The report must be set to open directly through the PowerBI application App must launnchwithout constant login Report must be displayed in the mobile display version within PowerBI This would be for a Samsung Android tablet running latest versions of SOTI and PBI.  I have used locked down actions of intent, browser, http, launch, custom, etc as well as the basic template html, but do not hit all four criteria above. 

    SOTI MobiControl
    4 months ago
  • 0 votes 3 answers

    Phone book on Android devices Solved

    Hello everyone, there is a way to create a phone book in Mobicontrol that is then installed on multiple phones. I don't want to do this with a vfc file, because I have to exchange it again and again with every new contact. It is best if I have an app with which the contacts are then also displayed in the contacts app of the mobile phone. I would then also like to maintain the contacts in this app and use it to synchronise all devices. We are still on Mobicontrol 2024.0 and I would like to set it up for Samsung devices that are Worked Managed. Many thanks in advance Translated with DeepL.com (free version)

    Android
    5 months ago
  • 0 votes 6 answers

    Javascript to push an application to the forefront if not locked

    Hi all, I'm looking for a javascript that I can run trough the task scheduler to a device that pushes an application to the forefront of the device every 5 minutes when the device is unlocked. (device is Android 14 / Xcover 6 pro Samsung) I have a task scheduler running now with a legacy script that brings the app to the forefront every 5 min (script is: start package.name). The problem with this is, even when the user locks the device, the script will bring the app before the unlockscreen. So i'm looking for a script that says: If PDA locked     no push application else if pda unlocked     start application every 5 min (bringing the application to the foreground every 5 min) else    no push application end Thank you for you help!

    SOTI MobiControl
    6 months ago
  • 0 votes 5 answers

    Zero Touch configuration of VPN app Solved

    Hello, we are using a third-party VPN app on our devices and I would like to enroll it with zero touch, meaning that with the installation of app the VPN profile should be installed on Android automatically, too. I tried to tweak the instructions described here: https://www.soti.net/mc/help/v2025.1/en/scriptcmds/reference/configuring_native_VPN_AE.html?hl=native%2Cvpn But I am not able to find the right configuration. Most important is to set the "always-on VPN" option of the VPN profile. When I open the app, the VPN profile is installed automatically, but the always-on VPN option is disabled. Other MDMs, like MobileIron or ManageEngine do have the option to set this flag for a specific app via profiles. For me it would be OK to use writeprivateprofstring, if no other option is available with MobiControl. As less important, but optimal solution would be to install the VPN profile completely without opening the VPN app. This would mean that the script needs to contain the app-id etc. Any ideas? 

    SOTI MobiControl
    6 months ago

Top 3 Contributors of The Week

View All

Earn Contributor Badge

More info
  • Diamond
    Diamond New

    Top-tier experts who are delivering outstanding content. Should have more than 7000 points.

  • Platinum
    Platinum

    Experts who are consistent with great content. Should have more than 1000 points.

  • Gold
    Gold

    Highly experienced members with valuable inputs. Should have more than 700 points.

  • Silver
    Silver

    Beginners taking the initiative. Should have more than 500 points.

  • Bronze
    Bronze New

    New contributors starting their journey. Should have more than 250 points.