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.
Hi everyone, We are currently automating the management of profile permissions, but we can’t seem to find an official API endpoint for this. After reviewing how this is handled from the console, we noticed the following call, which appears to work: https://${HOST}/MobiControl/WebConsole/api/security/principal/catalogueItems/${PROFILE_REFERENCE_ID}/rights Does anyone know if there is an official API call for granting permissions to a profile, or if this endpoint is the correct and supported way to do it? Thanks in advance for your help.
How can I disable Google Play Protect? I receive a warning when installing apps from SOTI. I want automatic installation.
We're starting from the lockdown a internal website via Sot Surf on the device. But sometimes the page keeps loading, and the screen stays white. When we're trying other browsers (chrome, on the device), the page will start without issues. When killing Soti surf, we sometimes needs 3 effords killing and starting the app to get the site loaded. A little workaround is stting the autorefresh on 30 second, then it will time out and Soti will handle a close message. But both is very annoying for the user experience. Anyone got any tips!
I want to create a script to be able to pull down OS update files to devices from my one drive, can anyone help me on this? do i just copy the path and put it in my script? do i need to add anything to the script at all? httpget https:"location of the file" /sdcard/"File Name"
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
Hi Having an odd problem, with the newst version of Microsoft Warehouse App 4.0.26.0 its breaking Mobi Device Remote control and only way to get it back is to restart, but then when you start the app it breaks it again.... So, we control the version of Microsoft's Warehouse Management app by using Profile, then packages to specify which version we use. I have been trying to test the latest version 4.0.26.0. so I setup my profile with the new version and then assign to push it out to my test devices. everything goes as it should, I remote to my test devices and start up the new version of the app, at this point the App forces a screen rotation and then freezes in the remote control window. On the device its phyically fine, but the remote window is frozen and even disconnecting/reconnecting I can't get it back. I have to do a soft reset to get remote control back, but then once I start the app, it freezes again. Wondering if anyone else is running into this? we are using Honeywell VM1A and Honeywell CK65 devices. I would like to be able to upgrade the app with outhaving to physically touch the devices as we have several buildings in different areas. Thanks, Shawn
Hello, until now we used the barcode from this thread Pulse | Community Support to enroll non-GMS Zebra devices in China, which worked well. However, with MX14 it does not work anymore. Is there a new code or is there a describe how to create one by ourselves? We tried to create one following WS50: Registrierung bei SOTI MobiControl mit StageNow, but still does not work. Best regards, Eduard
Hello there, I have a common issue with Company portal stealing token from MS Authenticator, which results in MS Authenticator being unable to register device as shared device. However I alraedy set Authenticator as "high-priority" and "open after installation". Also placed company portal in same app policy and gave it "postpone" priority and a bunch of MS apps in between. Still every other device I have to fix manualy by removing both apps and clearing cache and metadata of Authenticator and re-installing just it first. Side note: I can not avoid Company portal, as it is required by my mother company policy to run any MS stuff (Intune MAM). Thank you in advance for your best practices.Detail:Enrollment type: Work managed (fully managed device in kiosk mode)Device: Any (mainly Samsung & Zebra)Server version: 2025.1 (MC cloud)Android version: 15
We're in a transistion to get off the Honeywell Enterprise browser to Soti Surf. We're working with SAP IT's mobile with SAP Netweaver in front of it. We're not allowed to have double sessions active. So when a user picks op an new scanner and tries to login. We get a message to log off the old session on the first scanner. Despite of all, the logoff isn't working, the session won't cut off. This is working within the Honeywell Enterprise Browser. Any tips or tricks I can suggest?
Hello. We have configured Microsoft integration on our Soti Mobicontrol on-prem instance last year. Integration was done straight up from the Mobicontrol console, following SOTI's documentation. Since the end of the last month, we have this integration in error state. Checking intune adiministration, partner status is in Connection lost status. We checked the Soti enterprise apps on our tenant ( SOTI MobiControl Device Compliance and SOTI MobiControl App Protection) Both have the right permissions. I assume it's about cert/secret client expired. Since these apps are not in app registrations, we cannot renew them (or maybe i missed something?) I have an open case with Soti for this, but wanted to check if someone else had this issue, or if someone knows a fix for this. MC version: 2025.1.2 Thanks in advance.
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.
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.
Good day, SOTI Community. I've configured a Wi-Fi profile for my iPads so they should automatically join a specific network. The profile deploys successfully, and the devices show the SSID and credentials as expected. However, the iPads don't actually connect to the network on their own; they only join once I manually tap the SSID. After that first manual connection, they auto-connect normally.Has anyone else seen this or know what might cause the first auto-join to fail? Or is this by Apple's design for security/privacy measures?iPadOS v26.0.1MobiAgent v2025.1.0.2051SOTI MobiControl v2025.1.0.1010Thanks, MDel
Hallo, we are having issues with automatically naming our devices.Atm, we enroll devices and rename them manually. This is an issue since it needs time, prone to human errors and our automatisms for device certificates > So i want to automate. Idea was simple: Android: A-%AUTONUM:4% IOS: I-%AUTONUM:4% Problem:%Autonum% Counter is not global on the server.Each Enrollment profile has its own counter. So the numbering is as following:- Android: %Autonum% at ~10 atm- iOS: %Autonum% at ~75 atm- Rename via GUI ~140 atmIssue:- There is a danger of duplicate naming when the enrollment counter reaches the counter of the existing devices. SOTI Support says:Can't do anything about thatAny ideas for a naming concept which is easily readable by user (Shown on lockdown template) and automateable?
Hello, does anybody have an idea how to prevent enrolling of private devices as Work Profile devices into our environment? We have set the Device Type option in our Enrollment Policy to "Work Managed" as we only want fully managed devices in our MDM. Unfortunately with the same Enrollmend ID a user is able to enroll his private device by downloading the SOTI Agent from Google Play and entering this Enrollment ID. Shouldn't the option "Work Managed" prevent the users from doing so? If this is not possible, why are both options available in the GUI?
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.
