There's a new home for Articles. Find Articles on Our Product Support Page.
Operation Steps: 1. Create a new driver registration policy A. 2. In Apple Business Manager, select an MDM server and register policy A as the default driver registration policy. 3. Return to the registration policy list and download the JSON file for policy A. 4. Place the JSON file in a discoverable endpoint that is the same as the domain name of policy A's AppleID account. 5. On your Apple phone: General > VPN & Device Management > Sign in to your work or school account > Enter the AppleID of policy A to log in. 6. Return: Sorry! Your device couldn't be enrolled. Unexpected error occurred.
I've read the instructions on adding a SMTP server with Basic authentication but I have not been able to do that with a 365 service account and I believe it is because Microsoft has blocked Basic authentation. So do I need to setup Modern Authentiation, create a client secret and select negotiate as the Authentation type?
Hello everybody,I am new to SOTI MobiControl. We are using Zebra TC27 devices running Android 14. These devices do not have an internet connection, but we need voice input functionality on them. Offline packages are available for this purpose, and I can install them successfully when doing so manually. How can I deploy these language packages to the Android devices using SOTI? Many thanks!
Hi, maybe we did something wrong because remote control from MobiControl is not working for Samsung devices. We have models SM-T636B, SM-X356B The devices are enrolled with knox EMM (one with afw#mobicontrol) Supported API is showing: Samsung MDM V5.7, Samsung RC V1, Samsung KNOX v3.3, Work Managed Device Knox Service Plugin is installed v1.5.64 (26.05) Our onprem mobicontrol is 2026.1.0.11865 RC works with another manufacturer. Trying to open RC to any one of the Samsung device shows: Connection lost! WebSocket closed without sending a close frame. We have a running support case open but no solution yet, so i thought i might ask the community for any hint that might lead to a wrong configuration or enrollment process from our end. Thanks, BD
Hi all, Lookign through posts I can see this has been asked a lot however, have we ever found a clear cache app script for a samsung tablet, I've got an app that's holding 4GB of data in the cache and needs clearing weekly
I am running into issues trying to grant the permissions using the Profile for Zebra OEM Config: Is there a prerequisite to using this funcitionality or something I am missing. I don't want to go through the Play store and download the app, I find that the changes are not instant and I have to wait for the PS to push them down to the device. I have used the article here: https://pulse.soti.net/support/soti-mobicontrol/articles/ka2OF0000001nNDYAY But the permissions are not allowing. I have tried two devices and revoked, restarted the device and reinstalled the profile and it is not setting the permissions for: usage access, notification access, system alert window, manage external access These devices are TC78's, A14, running 2025.0.4 SOTI Agent Version.
Hi, i am a bit confused. We do not have google binding and are enrolling couple honeywell devices with the honeywell provissioner. This works well. The question popped because of the recent updates soti published (agent & plugin) we enrolled the devices with the AE agent (GoogleMobiControl-2026.0.1.1158.apk) Did we do something wrong choosing the AE generic Agent? The OEM version seems much older (2025.1.2.1214)?
Hi all, I would like to update Zebra TC77s via a file sync rule linked to a dynamic group in SOTI. I've done this in the past by setting the rule to "download from server" and entering the filepath into the "Server File / Folder Name" field. This is not possible to me as of now, as the rule expects me to use %ROOT% before the actual filepath. The MobiControl Version is 2025.1.2.1007, I last created a filesync rule in January, without this problem. All old filesync rules still work, there are 18 rules active right now. MobiControl was last updated in February, from Version 2025.0 to the mentioned 2025.1. After the update we tested only the functionality of the already present rules, not the creation of new one. The server is set up in a way, that Windows and all the programms are on one disk (C) and all data is on the other (D). For some reason I can't upload images to this discussion so I will just describe it further. Under "File Settings" I am selecting "Download from Server". The field "Server File / Folder Name" is prefilled with the input "%ROOT%". When deleting the input the field gets a red egde and is marked "Required". The inside of the field now states: "Use "%ROOT%\" followed by path". The path used before was D:\Folderexample\Folderexample\, when I enter this after %ROOT%\ (like this: %ROOT%\D:\Folder\Folder\) I get an error while saving the profile. The error is quite generic: ERROR, Could not update 'A14_HEL_FULL_14-38-04_LAN' policy. The path behind %ROOT% is "C:\MobiControl", I have tested this folder and it works, but sadly this is no option, as I mentioned above we split data and OS/programms and the OS disk is quite small. Can I somehow change the default ROOT without moving or updating Mobicontrol?I have found a draft for the new 2026 Version (Link: SOTI MobiControl Product Support) but I just don't understand why this worked before with our current version and the ones before.
Hi everyone, Is there any way to execute and export MobiControl reports via an API? Regards.
This was posted by me some time ago and we are having the same issue, I referred someone here and all we get is the question and can't see any of the replies. Pulse | Community Support. Any suggestions?
Hello! We're currently experimenting with bluetooth connectivity with some of our devices but no matter what I try. The popup to confirm the bluetooth pairing never shows up. We're testing on a Zebra KC50 device in kiosk lockdown mode. What we're trying to achive is using Soti's own Settings Manager and from there pair different perephirals like a Zebra scanner and different brands of bluetooth keyboards. It can "pair" but it never completes the pairing process as the bluetooth pairing popup doesn't show. The settings manager has access to turn on/off bluetooth, scan and pair. Then we're also using Zebra OEMConfig powered by MX which we have enabled pairing popup from but the popup never actually shows on the device while in kiosk mode. Any advice on how to solve this or if it is possible?
Hello Everyone,When connecting remotely to Windows and Android devices, can I enable a user accept prompt before the connection is established? I would like the user to approve the connection instead of allowing direct access.
Hi all, We are in a bit of a pickle regarding Shared Device mode using EntraID Currently we have this setup:User Logs into device using their EntraID and passwordSet Session PIN is promptedOnce connection to Entra is made, device moves to Post-Lockdown screen folder.I have configured the Post-Lockdown screen so users cannot shut down the device without signing out first. This ensures the user signs out, the PIN is cleared, and the device is ready for the next user tomorrow.Here is the problemThere have been instances where devices have powered off due to battery depletion or similar issues. As a result, the device shut down while the previous user was still logged in.When the device is then charged and turned on, some users have forgotten the PIN they used, or its another user whos grabed the device and they do not know the PIN.Because the Device PIN initiates BEFORE the SOTI MDM, it shows the device as Offline and I am unable to clear the passcodeThis is a big issue and is basically bricking devicesHas anyone found a way around this?
Is it possible to retrieve the devices that have a profile installed / not installed via API? We need to collect their DeviceIDs in order to perform actions on them afterwards. In the console, we can correctly filter the devices. However, we cannot find any endpoint like /profile/{referenceId}/* that provides this information. We have also tried using the /devices and /devices/search endpoints with the filter field, but we have not been able to make it work. This test returned KO (copy/paste the console filter and codifiy it): curl --location 'https://{HOST}/MobiControl/api/devices/search?filter=Profile%2520HasWith%2520%257B%2520ReferenceId%2520Equal%2520%2522776bfd88-339a-42f4-83c0-3abfa99f582f%2522%2520AND%2520Status%2520Equal%2520%2522Installed%2522%2520%257D%2520' \ --header 'accept: application/json' \ --header 'Authorization: Bearer xxx' { "$type": "ErrorDetails", "ErrorCode": 2058, "Message": "Device filter is invalid: 'Profile HasWith { ReferenceId Equal \"776bfd88-339a-42f4-83c0-3abfa99f582f\" AND Status Equal \"Installed\" } '.", "Data": [ "Profile HasWith { ReferenceId Equal \"776bfd88-339a-42f4-83c0-3abfa99f582f\" AND Status Equal \"Installed\" } " ], "HelpLink": null } Is it possible to obtain this information? Thanks!
Hello. We started to have issues with Microsoft apps sign-in on our devices (Teasm, outlook, etc) which are managed in Mobicontrol. MS integration looks fine in Mobicontrol. In intune SOTI is configured as 3rd party compliance partner, and active I've checked Azure logs, all sign ins are failing due to missing app protection policies (We have a CAP configured to require app protection policies). The policy is configured in intune, assigned with a filter, which excludes all app.deviceManagementType, except "Unmanaged", and adds a manufacturer filter. It was working fine for our enviorment, untill last Friday. There was an interuption of the service from Microsoft (related to filters). We spotted the issue on byod devices enrolled in intune first, but was fixed with the patch from Microsoft. As we saw, this issue was affecting multiple tenants. Unfortunately, the devices managed in SOTI are still affected by this. Wonder if someone has similar problems, and if you found a resolution. Currently waiting for a reply from Microsoft.
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.