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.
We have some work managed devices (Android 7+). We'd like to use our enterprise catalog managed by GooglePlay. We don't want to allow users to download an application without our validation (IT department), but we want still allowing the Google personal accounts creation. Is there any way to disable account switching only in the Google Play application? Thank you. Regards
Is there a way to change the device name with the REST API? I am using the API already to move devices to different folders and change the user of a device. But I couldn't find out if it is possible to change the name nor other attributes except of custom attributes. Thanks for you help! Cheers,Andy
When we remote control into some Galaxy S7 and S8 devices, the remote control is inverted/upside down on the screen passcode login. Phone OS is Android 8.0. Using SOTI MobiControl 14.1. Is there a way to solve this through MobiControl?
Hi all, Has anyone deployed Citrix SSO for Android Devices? I'm currently deploying it via an Application Catalog deployment rule but it requires user interaction to setup the connection. Does anybody know how to set the connection server without the user interaction? Thanks in advance, Héctor
Hello, I have a group of MC33 devices running Nougat. Devices enrolled in Android+. I need to be able to script the changing of device name (easy enough) then change the value in an .ini file to match. The .ini is accessible via Mobicontrol and permissions are not an issue. With CE devices I could have used writeprofstring or a replacetxt command to accomplish this. When I try either of these I receive a "command not supported" error in the log. There are 800+ devices each with a unique value. How do I accomplish this? Unfortunately in the case, Soti support wasn't very helpful. Would using Android Enterprise as device owner help? If so how? Thanks, Shawn
Can a Zebra TC75x be enrolled as a Fully Managed Device under Android Enterprise on MobiControl 14.1? When I try to use the AE agent I can only get this device to enroll in the Work Profile mode. Anybody have suggestions or instructions on what I am doing wrong?I am currently using the AFW#MobiControl on device setup. Thanks.
We are talking with SOTI about moving our on-prem MobiControl instance to the Cloud, however we use File Sync rules right now which sync to on-premise resources by UNC path. I understand there is something called "Cloud Link" which I thought would be a solution to this but it seems that this actually only deals with Active Directory. Is it possible to file sync MobiControl Cloud instance with on-premise files? Or a way to get files onto the cloud server for file sync?
Our developments team is recently converting some mobile apps to Android (Xamarin Forms). We have an existing SOTI server version 13.2.0.3123 for Windows CE devices. Android device is Panasonic Toughpad FZ-N1 OS: 6.0.1 We have been successful Registering Android+ devices in SOTI and have managed to create a Profile that adds a local WiFi connection and deploys several packages to the device once the Profile is assigned and everything is as expected the apps function accordingly. However when Lockdown feature is enabled in the Profile the device arbitrarily crashes and reboots itself. I did run AppCat on the device and notice there was a fatal exception that happened close to the time a reboot occurred but the log does not display the exception details, only a pointer to a subsequent log file that I cannot seem to access on the device. I am not certain if the device has to be routed to gain access to those debug files. I am under the suspicion that Android 6 is not really supported with server version 13 or the agent is not fully compatible with Android 6.0.1. I have read a similar post on this forum where it stated that the Lockdown is too aggressive and blocks access to system services that get called once the app is running by the OS and a fatal error is raised so the system reboots. Any insight would be appreciated before we make a call for SOTI support otherwise Regards
Hi , I'm unable to enable sync settings for this VM3 Honeywell Device which is running on OS Windows Enterprise 64bit , the reason i wanted to enable this function because advised by one of the technical team from SOTI where i'm not able to send packages ( I/O error ) This unit enrolled in Windows classic , but the packages successfully deploy whenever we restart the SQL / MS / DS services in MobiControl server. Thanks/Regards , Sharron
Hello. Does anybody have any experiences in loadbalancing Management Servers? Did anyone run into problems especially when using ERG servers pointing to LB-VIP? Are there any references in how to configure session stickyness on LB? And what about the Search Index service which is running on the first Management Server? Regards, Simon
Hi We are currently running in SOTI lock-down mode on Android plus devices I would like to know what kind of PDF viewer programs you guys are using for your lock-down mode. As we would like to have a very simple PDF viewer program that does not have any file-browser, print, or prints etc. options in it. plain and simple PDF viewer. Any recommendations ?
We have a device in the field that our Kiosk profile is not being activated on as it's stuck on the "Device admin policy pending" screen. When I tap the portion of the screen, I can tell it recognizes the tap as the background turns an orange color for a second but then it never does anything. Any thoughts on getting this resolved?
Looking to create device groups (a few hundred) from a list in a text file. I'm most familiar with powershell, but I've not worked with API's or security tokens before. Does anyone have a template or sample scripts that they would be willing to share?
Dear all, is there any way to move devices based on device name from one group to another group ?? as our policies are differing based on group . so there inter group movement is very frequent
Recently we had changed our root DMZ certificate for our Zebra/Symbol MC3190 and MC3200 devices however we are having a lot of trouble with wireless connectivity on multiple devices after it went live. After the change, we are noticing that some of our Fusion profiles are not connecting anymore even after verifying our wireless settings are correct and that the correct certificate is bound to the correct profile we want to use, not all of our production devices have experienced issues. We deleted the old root certificate as well. We can use bar-code provisioning for our MC3200 devices to install a “support” profile as well as delivering the new bar-code embedded certificate which works pretty well but doesn’t stick. What we are seeing is that the certificate delivered from the bar-codes for the 3200 handhelds is disappearing each day when the device is rebooted or has a battery swapped out. Here is the tricky part, each store has its own folder for district>region>store and each store folder has individual wireless settings. Due to this structure I was not able to use the cold boot persisting bar-codes due to the fact that it leaves copies of the said profile on the handheld (if stores use the codes more than once) and we only want the device to use the store profile we created and not the "support" profile assigned by the bar-codes. It seems that the store profile is our point of failure but I am unable to determine if this is a device issue, or a profile issue. Is it possible that the individual store profile is carrying a conflicting certificate and is somehow and overriding the new root cert that we pushed out via a blanket profile over all of production? If this is the case would it require manual removal of the root certificate from each store profile? When we rolled out the new certificate we used a profile with the new root cert attached and assigned it to our production environment in phases. We then used the reporting feature to check to ensure all of our production devices received the new profile and reported "installed". We remoted in and verified the new certificate installed on a number of device's root cert store, but we are still seeing issues after the original cert expired. Is there any way the Fusion profile could get corrupted due to the certificate update? We are looking for a way that we can potentially re-provision our devices offline as they are now disconnected and we do not use networked charging cradles that can reach the deployment server in the stores. We are fervently trying to avoid needing to physically replace these units if possible. We appreciate any help or insight you can provide. Thanks
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.
