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.
Hello, not sure if anybody already run into this but Google added new "feature" that will add and activate (problably only in case you have all other input methods disabled) new input method - Google Autofill (com.google.android.gms/.autofill.service.AutofillInputMethodServiceProxy). At the moment only (and quick) way to disable it was to add whole com.google.android.gms to the Blocklist. In this first case customer is not using anything by google or from playstore so it's not a problem but I'm sure in many cases it would be. If anyone has better idea how to block/disable/prevent/uninstall/etc it I'll be grateful but I just wanted to give you heads up
I've just begun my Zero Touch journey and I'm unclear on this. I have enrolled 4 devices in Zero Touch and set my Soti configuration as default and all device are showing MobiControl and the current config. I've only copied the config settings from Soti's support site and I don't know/can't find anything more on the subject from Soti's docs. The problem is, when I factory reset the phone it doesn't pick up on the Soti enrollment which is what I am expecting/want. The phone just sets up without the MDM.
Running on Android Enterprise, mostly Zebra handhelds. Agent version 2026.0.1. As part of an OS upgrade workflow, we have our devices in Lockdown mode with a "Device upgrade in progress" screen. After the upgrade completes, we remove the profile that puts it in Lockdown mode, and want to bring it to the app launcher. However, my experience is that the Agent app will launch, and either show the Device Configuration screen, or (if there is a Shared Device configuration) launch them into the Log In screen we have configured. This ends up creating confusion, especially if they're greeted with a Log In screen rather than their app list. Is there a way to configure/suppress this? I'm looking at ways to work around it (by explicitly launching the Home app) but would prefer to suppress it at the source.
We have multiple APKs from different Companys that do development for us, we can not longer upload due to mobicontrol not recognizing them as valid application Files.We are on Version 2026.0.0.58828 when we first encountered the issue, recreating what mobicontrol would do automatically with the package studio solves the problem and we can update these apps.Anyelse encountering these issues? Solution?Long time no posting here :)!
How can a user access the Second Screen setting in the drop down from a Samsung Tablet while in Lockdown mode? There is no setting for this in the Settings Manager?
Feature Request: Date Operators (Older Than) for "Android Security Patch Level" in Compliance Policies & Filters Problem: Currently, the property Android Security Patch Level is treated as a String in Compliance Policies and Virtual Groups. Users only have operators like "Equals", "Contains", or "Starts With". Requirement: Administrators need to set automated compliance rules based on the age of the patch (e.g., "Block devices with Security Patch older than 60 days"). Current Limitations: Text filters (e.g., "does not start with 2026") require manual maintenance every month/year. Workarounds using Scripts (to write os.securityPatchLevel into a Custom Attribute of type Date) are often blocked by Android Enterprise restrictions (e.g., on Zebra devices with strict policies), leading to script errors. Goal: Please change the data type of Android Security Patch Level to Date or add a specific compliance criterion "OS Patch Age" that allows numerical comparison. SOTI Version: 2025.0.0.1 Greetings,M. Klein
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.
I am trying to see if we can use SOTI for some of our android tablet and have them use intune company portal app to access our comnpany apps? The app requires the creation of a managed work profile, and when i tried it says it is not able to set up a work profile. I see that there is work profile that SOTI creates on the device, is that why and is there a way around that?
How can I reinstall a package that failed using a script? Is it possible?
We are working to intergrate OKTA as our IDP to move towards SSO and we are wanting to pull several fields (most importantly the phone number field) from the devices detail page when a user logs into any of the OKTA driven apps on the device, so we can then pass it into our 3rd party Workday app (also leveraging OKTA). Could we use the mapping attributes here to grab the Phone Number ( I didn't see it in the list) and pass it into OKTA? Or would we need to use an API to handle this?
Hi, Can anyone advise what the endpoint needs to be / look like for MobiControl to download an APK from a URL? I have a URL, which when browsed to, will auto-download the APK. If I use this same URL in the Enterprise URL field I get the message 'URL is not Accessible'. Thanks
I have an app which is being used on a number of devices which are in Lockdown via Soti Mobicontrol. I've noticed that when left unattended for some time (probably 20 minutes or so), my app that was previously in the foreground will be shut down and the Lockdown screen will be brought to the foreground. This wouldn't be that much of an issue if I wasn't relying on my app running also when noone is using the handheld, as the app will perform routine background tasks at certain time of the day. Is there a way to ensure that if my app is active, that the Lockdown screen won't take over?
Hey, I wanted to reply yesterday, but for some reason I couldn't reply. I clicked on “Post,” but nothing happened. That's why I created a new post. Pulse | Community Support @Raymond Chan Unfortunately, it didn't work. Here is the error code.
Use Case: We are wanting our custom attribute to update with the user everytime a new user logs into velocity. I have this working manually but trying to automate the js file using file sync. Velocity needs to read in the MAC address for each device. I have the .js script, that when sent manually will create the folder sdcard/com.wavelink.velocity and put the file into it containing the mac address (DeviceInfo.txt). Velocity file assisant will move it from there. I saved the js in a file (GetMAC.js) and have the file syncing to my device but i am unsure how to execute the file so it will do what I have already done manually. How do I execute this file. or is there a better way to do this altogether? should i put this script in the file sync itself? what would i specify for folder paths is there is none? JSScript: var folderPath = '/sdcard/com.wavelink.velocity'; var deviceMAC = mobicontrol.device.macAddress; // ----- Folder check with logging ----- var foldercheck = new mobicontrol.io.File(folderPath); if (foldercheck.exists) { mobicontrol.log.info('Folder exists'); } else { mobicontrol.log.info('Folder does not exist, writing folder to sdcard'); new mobicontrol.io.File(folderPath).createDirectory(); } // ----- Write txt ----- var txtFile = new mobicontrol.io.File(folderPath + '/DeviceInfo.txt'); txtFile.writeText(deviceMAC); mobicontrol.log.info('DeviceInfo.txt written successfully');
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.
