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.
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?
Good Evening, Anyone using Cisco Anyconnect as their VPN clients on their mobile devices with an Enterprise Profile vs Android Plus profile? I am seeing that once you you leave the elm agent you can no longer add profiles thru SOTI which then leaves it up to the employee to configure.
My company has started moving from the ELM clients to the android enterprise and BYOD setup devices. So far this has been a simple thing to do and it is working flawlessly, with one exception. We utilize several non-public enterprise applications that must be pushed out to our users. If they are on BYOD it does not get pushed or even detected on the end user's phone. Since we utilize BYOD using the packages for the apps is not an option. I located this page http://www.soti.net/mc/help/v10/en/Content/Web/Rules/Plus/Plus_Web_ApplicationCatalog.htm about half way down there is a section stating you can upload an enterprise application to the application catalog and push it out that way but only if you have a SSL certificate on the server to validate authenticity. We already have an SSL cert installed on the server per the requirements. When i try to push the enterprise applications using this method nothing happens. the app does not show up on the application catalog of any phone that i assign it to, android Enterprise or even an older ELM device. there is no error message or alert that tells me the issue as to why the devices are not seeing the full application catalog. Is there a setting that I am missing to enable this feature? Has anyone successfully pushed a non-google play store application via the application catalog?
I have received documentation in the past that was a patchwork of links to different locations and I'm hoping there is something better out there. I have two servers I'm maintaining with third-party SSL certs and I feel like I'm walking on very thin ice every time I touch this area.
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
Hello, I was wondering where I might be able to obtain an installer for a Zebra TC52 running Android 8.1 for your MobiControl Stage product? I have used your product for some time provisioning our legacy Windows Mobile devices and was curious if it existed in the same form for Android. I usually install this via USB for Windows Mobile via .cab
Hello all, i have some zebra tc75x device on android 6.0 and android 7.0. On this device we have the soti client on version : 13.6.0 build 1476 The server version is on version : 13.3.0.3454 i would like to disable the option under security -> unknow source But i've looks and nothing found ... Anyone have an idea about how i can disable this option ? Perhpas in the new version of mobicontrol or any other idea ? thanks for all
Are there any SQL DML scripts that should be run as a means of housekeeping prior to upgrading MobiControl? Should we shrink the database prior to upgrade?
I attended the SOTI partner event and I could swear that they said a brand new install of MobiControl version 13 would not have some of the components (ex. TLS 1.0) to support Windows Mobile/CE devices. It was suggested that the best way to support Windows Mobile/CE was to start with a version prior to 13 and then upgrade to 13. Are there any documents out there that can clarify this situation? Thanks much.
cant remote onto any samsung j6 android version 8, anyways to get round this
Hello Is it possible via MobiControl create a Schedule Task which start the distribution of the IOS update to the IOS devices Powershell ? Script ? Task ?
You have post this script : $MCUsername = "MobiControl username goes here" $MCPassword = "MobiControl Password goes here" $MCFQDN = "MobiControl FQDN Goes here" $ClientID = "MobiControl API Client ID Goes here" $ClientSecret = "MobiControl Client Secret Goes here" # You may want to figure out a way to encrypt the Password and the Secret, that's best practice $IDSecret = $ClientID + ":" + $ClientSecret $EncodedIDSecret = [System.Convert]::ToBase64String([System.Text.Encoding]::ASCII.GetBytes($IDSecret)) $Body = @{} $Body["grant_type"]="password" $Body["username"]=$MCUsername $Body["password"]=$MCPassword $Header = @{} $Header["Authorization"] = "Basic " + $EncodedIDSecret try { $response = Invoke-restmethod -Uri https://$MCFQDN/mobicontrol/api/token -Method POST -Headers $Header -Body $Body } catch { $($_.Exception.Message) } $Token = $response.access_token Write-Host "My MobiControl API Token is: $Token" #Now you can use the Token in other API calls by refering to the Token Variable.I want to send this script via the console script below via the powershell api call: sendintent -a "intent:file:///sdcard/clochecausses.mp3#Intent;type=audio;component=com.android.music;end" Can you add an exemple please ? In this script where to find client ID and client secret in the web console ( it is the name of the device ?, client secret is pin code ? ) Thanks a lot.
We have a need for attaching an alias for each device in MobiControl. The alias contains information about the owner and more. It will be approximately 10 characters long. I havent found any other way than to add a note to each device. The next problem is that we would like to find a specific device from its alias - ideally in a column in the list. Alternatively by using the search functionality. Is there any way to accomplish this? BTW changing the personalized name is not feasible, as we do not own some of the devices and as we cannot change the name from the office.
Hi, I'm using Android Enterprise to run a fleet of CT50s and CT60s. However, I recently enrolled a couple of devices, which won't install the applications from the Playstore. They're appearing in the App Catalog fine, but when I go to install, google play says "Your administrator has not given you access to this item". This is now happening on all new devices I enrol, but existing ones are still updating apps that are already installed. Does anyone have any idea what the problem might be? I'm using SOTI 14.2.1 Many thanks
We are staging Zebra handhelds, model TC56 and TC25. With Android version 7.1.2. And for some strange reason, roughly about 5% of the handhelds loses the functionality of the home button on the display. (circle icon in the bottom of the handheld). "Back" button works though. We are not using kiosk mode/lockdown or any kind of software that limits the handheld. Has someone got any clues to what can cause this issue? edit 1: tried to send a stagenow config, that would enable the home button. <wap-provisioningdoc> <characteristic version="7.1" type="UiMgr"> <parm name="HomeKeyUsage" value="1" /> </characteristic></wap-provisioningdoc> Didn't work. /Martin Ekman
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.
