There's a new home for Articles. Find Articles on Our Product Support Page.
Hi there, We are using MobiControl version 15.0.2.1049, with two type of Android devices (Urovo DT50 Android 9 and Honeywell Scanpal EDA50 Android 4.4) and there is a strange issue about location services with both kind of devices. If I login web console as a built-in MobiControl user and request a device location, I got back the location and it appears on Bing Maps. But if I login as an Active Directory user with the same permission and request a location, nothing happens. There is a "Device located" entry in the logs but nothing appears on Bing Maps. Can you give me some idea what happens when I request a device location? What kind of request goes where, what kind of data come back from where, etc.? Thanks for your help!
hello, we have 8500 zebra tc77 enrolled as android enterprise work managed devices. on all devices gms are active and the google account is activated. i forgot to add the managed google play configuration in our lockdown profile and add this afterwards. we add updates allowed only by wifi in the playstore config. but the installation is so slow.... i assigned it 2 days ago and now only 920 devices have installed the new configuration. if i remove the managed google play configuration the update is installed within max. 1 hour. all other profiles are installed very fast. android 8.1 mc agent: 14.5.4 mc version: 15.3.3 any idea thx mark
Hello,We are interested to enroll Windows 10 devices to make troubleshooting & installation somewhat easier.However everyone has their own laptop and we don't want to intrude on their privacy.Is there a way to only allow remote control when they allow it? (Like pressing a YES/Allow button)Thanks!
I'm writing a python script to automate the process of uploading our packages to SOTI. However, I am having difficulty sending the request to upload an Android APK file. here is my code for reference; file_name = 'com.aviagen.trapping.apk'encoded_file = ''with open(file_name, 'rb') as f: data = f.read() encoded_file = base64.b64encode(data)encoded_file = str(encoded_file, "utf-8")boundary = "mobicontrol_boundary"#part 1 - body parametersbody = f"--{boundary}\r\n"body = body + f"Content-Type: application/vnd.soti.mobicontrol.package.metadata+json\r\n\r\n"body = body + "{ 'DeviceFamily': 'AndroidPlus' }\r\n"#part 2 - file detailsbody = body + f"--{boundary}\r\n"body = body + f"Content-Type: application/vnd.soti.mobicontrol.package\r\n"body = body + f"Content-Type-Encoding: base64\r\n"body = body + "Content-Disposition: attachment; filename='com.aviagen.trapping.apk'\r\n"body = body + "\r\n"#part 3 - file contentbody = body + encoded_filebody = body + f"\r\n--{boundary}--\r\n"print(body)body = body.encode('utf-8')request = urllib.request.Request(f'{BASE_URL}/packages', data=body)request.add_header('Authorization', f'Bearer {token}')request.add_header('Content-Type', 'multipart/related; boundary=mobicontrol_boundary')response = urllib.request.urlopen(request)data = json.loads(response.read())response.close() This is resulting in an error - 422 (Unprocessable Entity).I have checked the file and can confirm that it is a valid signed apk which installs on my device. Is there something wrong with my request body? I saw a couple other examples of Package uploading, however they all use Powershell and I would very much like to avoid powershell at all costs.
Hello, Actually i'm facing an issue, i have install an application on my Android device but when I try to launch it for the first time it required some right that i need to add manually. I saw some topics that talk about that but it's not really detail : https://discussions.soti.net/tagged/app-permissions/ https://discussions.soti.net/thread/android-permission-script-afw_set_permission_policy/ https://discussions.soti.net/thread/differnt-behaviour-when-installing-with-mxconfig-and-app-permissions/ In this topic they talk about renaming an apk like tellnext.apk to tellnext.apk_ but they don't share us the command line to did that. I'm working on Zebra WT6000 android 7.1.1 lifeguard 19 - Android classic profile Do you know a command line to grant persmissions to access files/microphones/caméra/etc.. ? I saw some command line for android enterprise like that but it doesn't work on android classic : I don't want to enable access manually on each devices. Some have a solution maybe ? Thanks in advance,
Hello We are looking at using onedrive business to deliver documents to our tablets, the issue with this is that it prompt us to login to an account on each device. Ideally we would like to automate this process. Would it be possible to use a script to log in each device to an account?
Hi, We are on MobiControl 15.1.2.1035 and the connected Zebra devices (Android 10) does occationally loose the Remote Control option. We can get the Remote Control option back, by Sending this script to the devices: retryrcdetection The goal for me is to avoid having to send this script, as it generates a lot of service desk tickets from end users.
Is there a report that will simply list the users and which security groups they are a member of, or even the reverse that shows the security groups and the users that are members of each? I can find the user report showing the Granted/Denied permissions for each user, but nothing less granular that would show just the security groups memberships. Thank You, Jeff H.
I recently set up a MobiControl server and didn't see the option to set the server name so it set it as SOTI and I'm looking to change it to soti.companyname.com so that the devices can access the server and I'm attempting to do it in the admin utility under Deployment server but when I change the Management Service FQDN it tells me "The Management Service FQDN is invalid or can't be resolved to local address" Do I need to make any changes to the server, maybe a change to the Hosts file?
Looking to be able to wipe a device from the Soti MobiControl portal. Can someone point me in the right direction.
I have currently the strange Problem that when i enable feature control on our TC8300, and someone pulls out the battery or it gets empty the device gets somehow stuck and wont boot again for another 10-15 minutes until all energy from the circuits depleted. I think its a power management issue correlated to the hibernation possibilitys (supercapacitor) to change the battery without shutting the device down. If i remove feature control and reboot the device i can not reproduce the issue at all. Has anyone run into the same issue or not , and if so what featurecontrol settings have you enabled? Running on: Agent: 14.5.3.1017 MC: 15.3.1
Hi Guy's, how can i setup the gmail app (or any other app) with one User for alle Devices. I want to Use Username an Password, but i can't type in anywhre the password on SOTI.
HI, After an MobiControl Upgrade for an OnPremise installation from V. 13.4 -> 14.4.9.1034 we get this error when we are trying to perform a device agent upgrade for a Intermec CK3. The current agent version is 13.4.0.4164. The log says: Error sending file (Error sending file "\Temp\PPC_ARM_1449M_SIGN.CAB", Timed out waiting for response) Device disconnected Invalid device software version (Upgrading the device agent on [::ffff:10.41.139.143]:58424) Device (Agent) checked-in Any idea on how to resolve this. Regards Dan
We have a selection of devices (Samsung SM-T295) which cannot be enrolled. I have tried using our server (on prem) provided Samsung ELM agent and we get the error "This device agent is incompatible with your device. Please contact your administrator". We've also tried the SOTI provided ELM agent from soti.net/oem and we get the same message. We also tried the non-ELM agent but as expected that didn't work either. Has anyone any idea what is going on and how can I enroll these devices? Our server version is v14.4.1.1195, the agent version is v14.5.4.1016. Our server has SHA2 certs. The tablets are running Android 11.
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.
