There's a new home for Articles. Find Articles on Our Product Support Page.
Hello, can some provide me sample reports/ where can I find examples? Thank you!
We keep having issues whereby multiple users are being randomly unassigned from Samsung SM-T365 (Android) devices for no reason whatsoever. Whenever this happens their Exchange profile is removed and we see the below entry in the log file for the device: Device Configuration removed ([EAS Settings] Configuration is being uninstalled) We are then able to re-assign the user and the Exchange profile is automatically re-added, however this is getting quite annoying! We are currently running Soti MobiControl v13.2.0.3247 Has anyone else seen the same issue? Thanks, Stuart
Hi all, I run an instance which has been slowly growing, we've recently hit 549 devices. However, the amount online has stayed consistently just under 40%. 60% of devices will be offline at any time. IT also seems to rotate through different devices but never going above that 40% online mark. All devices are Android +. Some will connect one day and not the next. I'm at a loss as to why this is happening, but we urgently need as many of these devices connected at once as possible. Would there be a connection limit on the server? Any help as to why this is and how to fix it would be hugely appreciated.
I have seem to have run into an issue where passcodes are unable to be reset thru the console. We can send the command and see in the log that the command was sent and that the device received said command. We then have the employee put in what we have reset it to and it tells us it is invalid. So then I send a script resetpassword 123456 and the device says it has received the script and applied the new passcode. Have the employee try again and still wrong. So then I send the script unlock and go into settings and press on pin and it wants me to make a new one. So for S&G's I try to reuse a passcode I used in the script 123456. And it tells me I can not use a previous passcode. Which it should tell me that since in my Auth Policy I say do not allow previous 2 passcodes. So this tells me that policy is working. Any thoughts on why said commands thru the console or even script would not allow an employee to get into the device? Version 14.1.6.1113 Agent Ver : 13.5.1.1234 Enrolled as Android for Work afw#mobicontrol Device: Samsung Tab S3 OS: 8.0.0
we push an application via app catalog. Some users complained that their app is uninstalled, also there is a profile that contains a webclip to let the user see the apps that can be installed. I don't understand why my mandatory installed app removed from the device. And web clip removed from the device. Any help will be great
We just started using SOTI MC a month ago to allow for remote training and support to be possible on field personnel's company devices. My company has requested that our on prem Soti Mobi Control be accessible through OKTA for the support users. I have opened a ticket a couple weeks ago when our SSO admin was having issues configuring it in the web consol. I haven’t had much luck support wise with that subject(but some luck in other areas). So after getting another “has this been resolved yet” email, we decided to just try using what little info is in the guide. That was a mistake. The moment the “Enable SSO” box was checked and “OK” was pressed we were all kicked. I immediately responded to the ongoing email chain with Soti on the case regarding our SSO setup, got a response a day later, but only asking if the issue was resolved or not. (Update)I just received another response from support. They stated that I had several issues and a case needed to be made for each one. The original issue regarding the SSO(SAML) was replaced with one of the latter issues. I’ll have to open another case with support to have someone else start helping with the SSO issue. TLDR: SSO was activated but not configured properly, and now no one can log into the system to turn SSO off. Not sure what else we can do to recover the system. Anyone know what options we may have to get this back to a usable state? Chances are I won’t have access to do anything on the server or database side(I will have to speak to the departments instead), but if I knew what to say and ask for, that would help alot. On a side note, does support from Soti get better if you pay for Enterprise support? I am still trying to justify the extra expense to the bosses.
Even though I disable removal of mobicontrol agent and prevent unenrollment from group configuration, I can still uninstall the mobicontrol agent via drag and drop (uninstall). My goal is to prevent end-user to remove the mobicontrol agent without using kiosk mode or restricting whole settings, I want only restrict him in removing the agent in any ways.Type: Android+ Brand: Samsung Model: SM-G530H OS Version: 5.0.2 Agent Version: 13.5.1.1044
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
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.
