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.
Hi all. We are running varios Android version on Zebra MC9290 and TC70. We keep getting a pop up on the bottom of the lockdown screen saying, "Server Policies restrict use of Wi-Fi profiles not meeting required security level." Also, this pop up shows about 3-4 times. If a user is in an app, it kicks them back to the lockdown screen evertime the pop up shows up. Any ideas on what could be causing this or how to fix this?
Hey Guy's, anyone an Idea how I can set the Device Proxy (Auto PAC URL) on an Android Work Device? Unfortunately the common script command "setwifiproxy" ist not working on the TC20 anymore.... Stage Now is not an Option, cause I'm using 802.11x with Certificates delivered by Soti Certificate Template and Soti itself has no Proxy-Config within the Wifi-Profile. Hope anyone can help me or facing the same issue... Thanks
Hi I've just updated our environment to the version 14.1.3.1587. This version has the Andoid Plus Agent 13.5.0 1327 included. A newer Android Agent is available on soti.net/oem. Is there a way to update the Agent to the newest Version in the Database? Best regards Markus
I need to start thinking about changing my MobiControl URL as I need it to reflect the domain name of our parent company since we were purchased. Is there a process for going about that considering I have 625 devices registered and communicating to the current system? The server itself will not be changing. I just need for the public facing URL to change from mobi.oldDomain.com to mobi.newDomain.com. Could it be as easy as adding a CNAME record for mobi.olddomain.com to resolve to mobi.newdomain.com and then change the deployment, web, etc... URLs in the system? All new devices would register to mobi.newdomain.com and the older devices would not know the difference? Obviously I need to figure out the least intrusive way to do this without bringing down all of our systems live in the field. Thanks!
Hi, can anyone explain me the "writeprivateprofstring" for Android Plus devices? I'm using MobiControl "14.1.3". I don't undestand the help: https://www.soti.net/mc/help/v14.1/en/scriptcmds/gsrindex.html?gsrid=reference/writeprivateprofstring.html How can I read the value from my device? Where can I find the pbd.ini on my Android device? What I have tried: "writeprivateprofstring isAllowed "Zebra Technologies" "MC18N0" "Yes" It looks like the command works but I don't know how to read the value
I want to implement Custom Data for profile deployment filtering on my Zebra TC51 devices running Andorid 6.0.1 Is there a easy way to change the value of a section inside a .ini file?
I have a 13.3 setup on a physical server, and I have recently setup a 14.1 on a VM that will be our new production server. I'm trying to figure out the best way to start to migrate these windows (all win ce) devices to the new SOTI server. Any one have any ideas or experience doing this? I've been searching around for some info but I actually do not see much online.
[HKEY_LOCAL_MACHINE \ SOFTWARE \ Teklogix \ OpenTekTerm \ Params \ app \ 116 \ tess \ termno]"Data" = dword: 00000019
Hi all, We have 500+ Android devices, and are looking at rolling out a lockdown profile. However, we want to restrict the users from accessing settings. Ideally they will need to be able to change an enforced password. I managed to create a change password icon on the lockdown screen, but it doens't require the user to enter their current password. Therefore anyone could change the device password whilst it is unlocked. Is there any way to require user to enter their current password before changing it? Otherwise they will need to call my team - get them to remotely disable the password, or change it to whatever the user requests. Many thanks in advance, Seb
I am installing MobiControl v13.2 on our server and when the installer is trying to create/update the database, throws the error above and crashes. Install log Ends with this 5-4-2018 11:08:22: STEP=>SharedFiles_Installing.5-4-2018 11:11:05: STEP=>DatabaseExecute_Installing.5-4-2018 11:11:05: STEP=>DacPac_Installing.5-4-2018 11:11:05: MCSetupDll_DacPac: FIELD_DacPacInstallerPid = 2476.5-4-2018 11:11:16: DacPac stats = -2, FIELD_DacPacLastAction = . I followed the installations guide, there is no proxy in between, firewall is disabled. Maybe someone here could have an idea what is this trying to say? Many thanks in advance! App server WS 2012 R2 DB MS SQL 2012
Greetings, We have an agency that is using the XPlore iX101D1 (XSlate D10) tablet for their fleet and for some reason even though in their profile in the Lockdown configuration we have all 3 Status Bar items checked (Disable Status Bar Expansion, Disable Settings Changes, Hide Status Bar), the status bar is still visible. Also, in the lock screen, the status bar can even be pulled down by the user. Before entering in a support ticket, I wanted to see if anyone else had this issue and if there was a resolution to it. The Android OS version is 5.1 and the Agent version is Xplore 13.3.3.1010 (Android+). Thanks, Craig Prusansky
I have a problem with one of my Zebra TC51 Android+ devices. (non GMS) It just got send back to me after being in repair. The repair centre installed Android version 7.1.2. Unfortunately we cant guarantee it yet, that our application on these devices is compatible with Andoird Nougat so I had to downgrade the OS to Version 6.0.1. Before proceeding with the OS downgrade I played around with StageNow to get the MobiControl device agent back on the device. After installation of the agent the device got added to MobiControl as a completely new one and the "original" device is still offline. The device had a cracked touch panel and it got replaced. This is the only hardware change listed in the repair details. In the webconsole the "new" added device even has the same serial number and MAC-address as the original one. I then un-enrolled the device and did the OS downgrade.... MobiControl Stage is already installed with Android version 6.0.1 so I used barcode staging to get the device back into MobiControl. I only have one Add Device Rule for Android devices and used the shown enrollment ID in the barcode settings. After re-enrolling the device with Android 6.0.1 installed, it got added as a completely new one once again. Im using MobiControl Version 14.1.0.1152 Does anyone know what could cause this behaviour? Am I doing something wrong when enrolling the device?
Hi, I have a .rdp file that I am adding as a menu item to my SOTI Lockdown screen as it's required for my particular scenario. The RDP logo will appear in the lockdown so the path is correct but launching it does not seem to work. (ie. tap/enter but nothing happens) If there was a way to get that working that'd be great but there may only be a solution for my workaround below: A few threads back I had a topic on launching a script from the lockdown screen on an android device and we achieved that with script://<path>/<script file> for the menu item after placing a .cmd script on the device. I would like to essentially accomplish this same thing but on Windows CE this time if possible as I have a SOTI script that can be used to launch the .rdp extension. There may be something simple I'm overlooking so I'm going to go dig through some docs. Thanks, Ben
Is it possible to set an alert to send an email when the devices exceed a certain speed? (Android+)
After finally freeing up enough space on the VX6 device to get the agent installed the device still does not show up. I can go into the configure menu then servers. I select my server and hit test. The connection box comes up with the server name then next line is Connected and final line is Cannot send data to server. So it looks like it is connecting but not transferring data. I have several Thor VM1 running CE6 that are connected to the same server and same port with no issues. I am only having issues with all of the VX6.
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)
