There's a new home for Articles. Find Articles on Our Product Support Page.
When using StageNow xml Config scripts in packages I sometimes get this error:Script command is not supported by device (xmlconfig) Sometimes I don't get this error and it processes correctly. Most of the time when I get the error the changes still go into effect so the XMLCONFIG must be processed. Other times it does not and I have to remove and re-add the package to get the StageNow profile to take. Is there a reason this is happening? It works most of the time, but there is no good way for me to know when it doesn't work and I get devices out in the field that are not fully setup. My package has a simple TimeZone (Clock) setting from StageNow, and the script command is "mxconfig /sdcard/TimeZone_Eastern.xml". The devices are Zebra TC70X and they are running Agent version 13.7.0.1031 on the devices.
I have a 14.2.3.1069 instance with Zebra MC93s enrolling with AEDO via StageNow on agent version 13.7.6 Build 1004. The devices are running the latest public Oreo BSP from Zebra (01-21-18.00-OG-U00-STD) for the Helios devices and have the Zebra OEM Plugin (Zebra_Hawkeye_RC_AE_1.6.0.102) installed. On just about 1 out of 3 of the devices I enroll I get a prompt to manually enable the modify system settings permission. The other devices never prompt for this and install all packages and profiles without issue. The devices that prompt for this actually fail to install any packages containing APKs, citing storage/permission issues. After granting the permission manually and then forcing a package reinstallation the installation is successful. Any idea on what might be going on here?
Hey Guys, I just want to know how you handle Updates of Chrome, Playservices, ... in your environment? We're using many Zebra TC20 for internal use only. We have a few Apps which only needs internal access to our Servers, so the Zebras are configured with a Proxy for internet access, just for a quick view of prices, Information etc. Unfortunately the Google-Apps don't use this Proxy (configured with Zebra MX) for updateing themselves. That means we're still using Chrome, Play, Mail, ... Versions from the Zebra OS a few Months ago. A newer OS-Update doesn't contains newer App Versions of e.g. Chrome so we're now got stuck. Is there any chance to Update all this Google-Stuff by apk or do I have to change the WIFI so the Devices get unlimited Internet-Access? for example: The Chrome Version installed within the Nougat or Oreo OS of our Devices is 69.0.x. We just want to bring out an TWA Wrapper App which needs min. Chrome 74.x. I don't know at the moment how to Update Chrome to get this working. Many Thanks and kind regards
I can't believe it's finally here. Has anybody started using it with SOTI yet?
Hi Is there any way of getting the output from Mxconfig XML command into a file or into the logs of MobiControl?
Hi! When we use the script "resetpassword xxxx" on our TC56 devices running on Android 7+ we also get the setting for PIN on device boot enabled. When setting this manually we get the question if we want to use the PIN even for device boot. Is it possible for MobiControl to not set the PIN for device boot as well?
How can I not prompt the user to “Please give Write Settings permission” when sending the following script: writesecuresetting -sys hide_rotation_lock_toggle_for_accessibility 1 writesecuresetting -sys accelerometer_rotation 0 Using AEDO on the TC52 and TC20.
Is there a method for disabling Play Protect beyond these two scripts? I have tried both on an AEDO TC52 and neither seem to disable Play Protect. I am running Agent version 13.7.0 Build 1031. writesecuresetting -glo package_verifier_user_consent -1writeprivateprofstring DeviceFeature DisableVerifyApps 1apply featurecontrol
Hi, Any suggestions as to why Zebra devices wont enable network interfaces before a PIN has been entered? We are requiring a device PIN due to a certificate profile on the device. However when soft resetting the device, we are prompted for device pin (naturally). However the network interfaces are not enabled until the PIN has been entered, thus effectively cutting of a branch for the mobicontrol administrator. (The devices still have an administrative WPA2 network available). This is not the case for Samsung devices, they will activate interfaces to the network just fine before entering PIN. Any suggestions or workarounds?
Hello everybody, I'm encountering a problem with the remote control functionality on Zebra TC57 and Zebra TC77 devices. On our end, the remote control (both via HTML5 and the legacy downloadable plugin) shows a black screen inside the device skin. Yet if we click somewhere in that black screen, the remote control does actually work and we're able to control the device. Its screen just will not show. So if we haven't got the device itself nearby, we can't see what we're doing. Here's what we're using: MobiControl version: 14.3.1.1189 (cloud-based)Zebra TC57 and Zebra TC77Android 8.1.0, OEM version 01-13-20.00-OG-U12-STDAgent version: 13.7.0.1031 (GoogleMobiControl1370_1031.apk, DO mode)Remote control version 1.15.3.109 ("MDMPlugin_Notification" v1.0 from Zebra_Hawkeye_RC_AE_1.6.0.102.pcg) Any ideas? Thanks in advance. Cheers, Theun
Hi! We have configured the SOTI Surf on several devices but after an upgrade of the MobiControl Agent to one of the latest versions, we got problems with using SOTI Surf. The application won't get past the splash screen but it will also start flickering and head back to the lockdown instead. This seems to be some kind of problems with a permission?? Devices used in this case are Zebra ET50 and enrolled as Android Enterprise Managed Device, and we are installing the application with StageNow XML instead through Google Play or package deployment.
I just enrolled 1 Zebra TC52 (DO) with google enterprise profile. I have created a configuration profile where I need to block camera (via feature control). The camera stills not blocked despite profile has been applied to device. Any Idea ?
I have an enterprise B2B application that I distribute to devices via SOTI Package in a Profile. SOTI is properly installing the APK and is also now automatically granting the required permission (just storage) which is a nice feature recently introduced in this agent version. The issue that I'm now facing is that the app itself will no longer launch and I get a permissions related toast message error as soon as I try to launch it. The same version of the application works under the following circumstances: AEDO Managed Zebra MC33 running Android O (8.1.0) with LifeGuard 12 on SOTI server 14.1.3.1587 and the 13.6.0.1567 Android Enterprise Agent.- App runs correctly AEDO managed Zebra VC80x running Android O (8.1.0) with LifeGuard 12 on SOTI server 14.2.2.1170 and the 13.6.0.1622 Android Enterprise Agent - App crashes on launch with permissions error. I'm trying to isolate my variables as much as possible to identify the root cause of this problem but I'm starting to think that it has to do with the automatic permission granting of the new agent version. Is there any way to disable this feature so that I can manually enable the app permissions? The forced upgrade to a newer agent version seems like a pretty frustrating side effect of leveraging Android Enterprise with a Play Store distributed agent. Is there any way to lock in a specific agent version for AEDO enrollment if it does end up being the Agent causing the problem?
Hi, I'm trying to install Soti MobiControl on a new Zebra TC72 device. But I have not found an .apk that works, it always gives me the error "This device agent is incompatible with your device. Please contact your administrator". Does anyone have any idea if there exists a version I can use, and where to find it? Best regards, Daníel
My customer uses an Wifi environment, where each devices is identified by a static address. We now need to bring in around 50 new devices an need to set an individual static ip therefore. I pushed a fusion profile to each device, but how can I individually set the static IP? I do not hope that a need to create 50 separate profiles for this? Thanks for any hint on that
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.