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.
The support page mentions the availability of "Knowledge Base Articles Access" with a description of "SOTI knowledge base articles to find answers to your SOTI MobiControl implementation. Get helpful advice in an easy to understand format written by our support engineers."Great! Where do I find it?? I'm looking for information on disaster recovery configurations. The deployment server config contains things like: "Secondary Agent Address and Port". Seems like a recovery/failover mechanism of some kind. Finding any detailed information about it though seems to be impossible. The online (un)help contains the useful: "Displays the secondary address for device connectivity in IP or FQDN format as well as its associated port."How about a description of WHEN or HOW it would/should be used! Are there any "best practices" documents that explain how to prevent devices from becoming orphans if our data center blows up and we need to bring up the infrastructure in a different location?
I recently setup a telecom expense management rule to monitor data usage across our Samsung Tab E Android devices. I pushed out the rule to a group of the devices I want to monitor but found a user must activate the setting manually on the tablet. I pushed this out to a couple hundred devices in vehicles where we do not want the user to have to do this manually. Is there anyway I can programmatically make these changes?
Our customer has the problemnot all apps appear as desired after a lockdown.The customer works here with Acer Tablets with the Android version 6. MobiControl v.13.4.0.4339 Acer Tablets A3-A20A3-A40B3-A20 The agents for Acer are up-to-date on the devices.Does anyone have an idea?
Currently we have a public IP address where a port is forwarding to a Windows 10 machine (MDM server).But we have the Problem, that the Deployment Server says "Started but not connected to MS" And the icon under the server settings is yellow.Look -> So i can Add Devices without Problems but thats it. I can only add these Devices.Its MobiControl v.14.1.0.1152
We have Blackberry KeyOne devices that was setup with AFW#MOBICONTROL, managed device setup. Issue: Bluetooth contact sharing is greyed so users does not have contacts list on their car. It is greyed out even before it's enrolled. Same after enrollment. We do not have this issue with Google Pixel with same setup. Our Samsung devices are on Android Plus, no issues there. anyone have any idea? we submitted a support ticket and the rep is taking a long time to respond.. screenshot that says it has been blocked by administrator(even before it's enrolled) https://imgur.com/a/SPtzr
Hi everyone We have 2 Deployment Server behind a loadbalancer. Which is the best way to use the load balancer address? Just use it in the mcsetup.ini? [Connection] DeploySvr1=loadbalancer.company.com:5494 Or should i configure the loadbalancer address somewhere in the console? Thank you for your help Best regards Markus
A newly installed ver 13.4.0.4449 on premise server with the error message when generate the report with the result of "Unable to generate report, please try again later." All reports generation with this problem. How to fix this issue?
I need the wifi to be enabled on my devices but if i do the units go into a boot loop . Please assist ASAP
We had a script that we pushed to laptops to reboot them working fine in MC13. The script stopped working when we upgraded to MC14. We are now at the latest MC14 version and we can't get it to work. Does anyone have any ideas? This is very important to us because it returns the laptop to the state where a smartcard and PIN is needed to access the latop's contents. Thanks!
Hello, after upgrading MobiControl from version 13.3.0.2906 to 13.4 (latest MR) Devices running on the M3 SM10 LTE (Android 5.1.1) and M3SM10 non LTE (Android 4.3) can not be upgraded to a compatible version of the server .On M3SM10LTE devices, agent 13.3.0 build 1069 is installedOn devices M3SM10 non LTE installed agent 13.3.0 build 1069Automatic Update> Right Device Button> Allow Upgrade> Upgrade now feeds information about an incompatible device.Attach a sample log:Agent upgrade attempted (Unable to find matching Android Plus Agent)Please for assistance, the problem so far 300+ devices
Hi All, We are using SOTI V13 with majority android plus devices. We are struggling to get vendors to provide us with APKs to push to our devices and provide updated APKs when required. I see we can put them in an "app catalogue" but this seems to just provide a link to a play store but the majority of our devices are shared devices in lockdown. I've also see within mobile iron you can pull an APK in from the play store. does anyone have any suggestions / advice?
What protocol does SOTI use when connecting to a Windows Desktop computer? Is it Remote Desktop? Can other programs use the client on the desktop computer to control the computer? What security does the client have to prevent connections from other remote control programs? Can the client be hacked to allow another program to connect to and control a windows computer?
The idea is to create an Apk on the device that would ask the Device Agent to execute a syncfile (like commloader -syncfile on Windows CE) I guess there is an intent that can be sent to the device Agent ? What is the right syntax to do this ?
Hello, I get the following message on my device: "The certificate for this Server is invalid". How can I avoid this message / what is the solution?
Hi guys, I'm trying to remove a "test" Device Rule and leave another 3 I have created. There is no way I can remove the test one as it says "The Add Device Rule cannot be deleted as it is currently set as the Default Add Device Rule. Please change the Default Add Device Rule before deleting the rule" However there is no way I can change the default rule. Does anybody know if this is possible? 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.
