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.
On Zebra TC75x and TC56 devices running on Android 7.1.2 Nougat with Lifeguard updates 11 and up, we noticed the MobiControl agent disconnecting from the server whilst the devices do have an active internet connection. When the device reboots, MobiControl does as well and stays connected for a few minutes but it'll disconnect soon after. During the staging process of these devices, we add MobiControl to the battery optimization whitelist. We've tested this thoroughly and this works fine. Further testing proved that, once the device reboots, the setting will revert and MobiControl will be submitted to battery optimization and thus will be killed by Android to save power in x minutes, if not in use. Not maintaining this setting is problem 1. Problem 2 is that the MobiControl agent will not reconnect after being killed by the battery optmimization process, unless you reboot the device. I must say we always have a Lockdown screen in place, that might have got something to do with it. Any ideas how we can add the MobiControl agent to the battery optimization whitelist permanently? Devices: Zebra TC75x, Zebra TC56 OS: Android 7.1.2 Nougat OEM: 01-01-49.00-NN-U11-STD, 01-01-49.00-NN-U12-STD, 01-01-49.00-NN-U13-STD, 01-01-49.00-NN-U14-STD MobiControl agent v13.5.1 Build 1234 MobiControl cloud version 14.2.0.2894
Hi everyone I've noticed the settings icon disappears from the app menu on a few, not all, Zebra TC56 devices running M/N GMS, anytime after enrolling it into MobiControl. It is not possible to access settings from the pulldown menu either. Has anyone else seen this issue? Devices: Zebra TC56 OS: Marshmallow and Nougat with GMS MobiControl: 13.4 Agent: 13.5.0.1496
We are using some Zebra RF guns in our warehouse. Per a recommendation from Cisco we have turned off Fast Transition on the wireless network, which basically means that the clients stay connected longer. We would like to see if there is anything we can set in Soti to force the client to roam when it reaches a signal threshold.
First off my ultimate intentions is to have one barcode that loads all Zebra devices. Doesn't matter if it is a ET50, TC70X, or a TC50. With that in mind I have setup the add rule to drop all devices into a Stage folder. My goal is to setup a device relocation based on the device model. Unfortunately IP and Custom Data are the only option to trigger relocation rules (Soti PLEASE make this more flexible in future!). I could use the Custom Data, but the only way to fill a custom data feild is through an INI or XML file off of the device (again FLEXIBILITY please...). So at this point i'm thinking a file sync rule with a custom script post file sync that will take the %MODEL% and write it to an ini file on the android device. Then I can tie the custom attribute to that file and pull back what was written into that ini. FYI - I have this working on WinMobile devices since there are ini files built in that include the device model. I am very weak at writing soti scripts and am wondering if i'm on the right track before I spend a bunch of time writing the script. Is there an easier way? Will this work at all?
I want to automate assigning 3000 devices on their specific group. I want to do it via rest api with my script.
It doesn't look like it's possible outside of building a package to deliver a .zpl file containing zpl code to a Zebra printer but I am wondering if it has been mentioned to possibly add the capability of sending raw ZPL, almost like sending a script to Android+, to ZPL enabled printers versus the native config profiles and packages. It appears the native printer config profile options are doing this anyway being that there is no agent installed on printers.
We recently downgraded a number of Zebra WT6000s running N back to L and re-enrolled the devices back into the same MobiControl instance as part of that process. The devices were not deleted from the inventory during the process and seemed to, for the most part, reconnect to the MC server just fine. There are a portion of the devices however that are showing up in a Non-Compliant status which is now seemingly preventing them from receiving their full configuration. How can I clear out or get rid of this Non-Compliant status. The Help guide goes into some minor detail on what Non-Compliant could mean, but does not provide any help on what you can do to address this. Other details: - Zebra WT6000 - Android L, 5.1.1 (downgrade from N) - Android+, DA - Agent 13.5.0.1677 - MC 14.1.7 (now), upgraded from MC14.1.0 when we first saw the issue. Still persists after the upgrade
I'm trying to install 2 OS updates on my Zebra TC51 devices running Android 6.0.1 I used StageNow to get the xml file to accomplish that task. On some of my devices I get the following error when trying to execute the mxconfig command on the device after the package got downloaded: 2018-07-25 16:42:27.836|pool-1-thread-1|D|AP|[LegacyScriptExecutor][execute]script command: mxconfig - begin|2018-07-25 16:42:27.836|pool-1-thread-1|D|AP|[ZebraXmlStageCommand][execute] xmlPath: /sdcard/TC51_OS_Update_MX6.3.xml|2018-07-25 16:42:27.839|pool-1-thread-1|D|AP|[ZebraXmlStageCommand][execute] (/sdcard/TC51_OS_Update_MX6.3.xml) Response: <wap-provisioningdoc><characteristic-error type="Permission Error" desc="MxFrameworkService: [net.soti.mobicontrol.motorola.shared:10130] is NOT allowed to access MX Framework!"></characteristic-error></wap-provisioningdoc>|2018-07-25 16:42:27.839|pool-1-thread-1|D|AP|[ZebraXmlStageCommand][execute] (/sdcard/TC51_OS_Update_MX6.3.xml) Process xml successful|2018-07-25 16:42:27.839|pool-1-thread-1|D|AP|[LegacyScriptExecutor][execute]script command: mxconfig [/sdcard/TC51_OS_Update_MX6.3.xml], result: ScriptResult{description='OK', resultType=OK} The installation of the package gets reportet as successful back to the MobiControl server but the OS update never took place. Sometimes a restart of the device fixes this permission error. Does anybody know where I need to change permission settings or what could cause this error? Thank you! Regards, Michael
Hi;My Zebra TC75 device "Agent Status" still waiting "Connected, waiting for server response" and the device seems to be Offline on the console.Other Samsung Android devices "Agent Status" section just writes "connected" (green color) and devices online. I tried to wipe the device. I re-enrolled the device but the result did not change. Have you encountered a similar problem before?
Hello there; do you have any idea how I can upgrade the RC version on my devices? All devices are the same brand and model. In older versions, RC does not work.
I am trying to trigger an app to update an ini file. I can start the app via MobiControl script. The problem seems to be that when Android is sleeping, it seems to interface differently with the file system and it does not update the file. Is there a way to wake up the device before triggering the app? Any other suggestion would be helpful. MobiControl 13.3 on Zebra MC67s.
I am having issues with the MobiControl Stage app when attempting to stage via bar-codes for Motorola/Symbol scanners. I have created a Fusion profile with all of the correct settings in the Mobicontrol stage app to connect to our AP however, I consistently get the error "Failed to configure Fusion Wireless" when finishing scanning bar-codes. Scanning the bar-codes does install the certificate I imported in the stage app but will not set the profile in Fusion before failing. I am able to set Fusion Global settings, Fusion password, Radio on, and Radio off fine through bar-codes and have confirmed these settings work. I also can create a profile in Fusion manually with identical settings to what I put in the Mobicontrol stage app and it works fine to connect. Does anyone have any experience with Fusion Wireless and Mobicontrol stage app? I can hardly find any documentation on the bar-code staging subject other than extremely basic SOTI overview documentation, so if anyone could shed some light on this I would greatly appreciate it. My model of scanner is Zebra\Symbol MC32N0 and MC3190 both with supported versions of Fusion according to the document I found on this forum. Here are a few more details: Mobicontrol VER: 13.0.0.33766 Mobicontrol Stage Ver 13.2.0 Build: 3247 Device Model: MC32N0 OS: Windows Embedded 7.0 build 2824 Device Model: MC3190 OS: Windows Embedded Handheld 6.5 Classic At this point I only need to be able to get bar-codes to set a wireless profile in Fusion and I'll be golden. Thanks again in advanced for any help provided.
This was on a (multiple) Zebra WT6000 non-GMS running the latest of Lollipop/MX. Right after enrollment into 14.1, my device would startup the MobiControl Agent app on the device and then the app would close, showing "MobiControl has stopped". I've been getting this consistently on all of my WT6000s. Sometimes relaunching the Agent will work but I had one instance where the device showed the agent and the stage app still installed and I had to uninstall the agent and re-enroll the device using stage. Anyone see this before? Upgraded Agent is 13.5.0 Build 1327 Thanks, Ben
I'm using a Zebra TC75x device. I created an mxconfig file using the Stage Now app (sets the screen timeout setting) and exported the xml file for MDM. I took the xml file and created a package with MCStudio. The file is placed in /sdcard/Download/ and the package has a post-install script that runs the command "mxconfig /sdcard/Download/<filename>.xml. I put the package in a profile and assigned the profile to the device. After doing so, I check the logs for the device and see that the package and profile both log as installed. However, I also see an error log that says "Custom log (Mxconfig -/storage/emulated/0/\Download\<filename>.xml was not found.)". Now, the settings that were part of the xml file were applied successfully (screen timeout and lock screen). So my question is why does it show the error log even though the settings were applied successfully?
Hi, Installed and enrolled the MC33 to my Soti v13.4 with Android+. The device is encrypted and when i try to install applications to it it says: Error message received from device (Internal storage decryption not supported) Tried to decrypt the device it but it is not possible in Android 7.1.4? (Factory reset done). I have not done any decryption settings in Soti..
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.
.jpg)
