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, Is is possible to provide Android Enterprise devices (DO) with a wifi profile that includes proxy settings with username and password authentication? A customer of mine wants to push this wifi profile to samsung devices. The proxy settings include an SSID, PSK, Proxy server name, port number, Service Account Name and password. I can see in the profile config everything but the service account username and password fields. Some of the devices are leveraging Samsung Knox Configure Dynamic. I've tested this once but the result was that the username and password fields on the devices wifi profile appeared blank once I made the changes. However, even if I get this to work, I'm only able to push this to those devices on KNOX configure... not all devices. So a SOTI mobicontrol solution would be the preferred method. Any help or suggestions would be appreciated. Chris
Hey all, We are currently on MobiControl Version: 15.0.0.6019 We have both Samsung S8 and S5 in enrolled into our account. Is there a way to disable the physical power button from getting used on the devices? We want to prevent users from turning off the devices on their own as it becomes a security risk. They can simply turn off the device if they want to steal it. Any help is greatly appreciated! Thanks.
Need a way to reduce camera resolution when taking pics using an android enterprise tablet. Would prefer to use the default android camera, since unable to find an open source camera app to edit the UI.
Hi. I have a trouble with enrolling devices to my SOTI server. Here is a screenshot with messages which I can't get rid of and enroll any device, using google mdm account in SOTI. Device: Samsung J5Android version: 9Knox version: 3.4Playstore version: 22.4.25-21Soti Server version: 15.1.0.3413 Soti mobile version: 14.1.4 Build 1010 At the beginning, there were any problems with enrolling device. I've could enroll more than 50 device in the same day.Later, only 10 a day. Next day there were no problems to continue enrolling.After few weeks, only one device a day.Now, I can't enroll any device. Sometimes, I need to wait few days, sometimes more than a week to enroll.This problem started from June and still persist. There is no any problems with SOTI license or Samsung ELM, because device is always succesfully enrolled without google account. What i've tried:- create a new rule with another mdm google account and enrolling device: success.- enroll device without google account: success.- reboot server, reboot device: still not working.- check if hash for mdm google account is the same. Are the same, but device still stuck in same message. - enroll devie in another server and without google account: success.Is there any google account limitations for how much devices you can enroll via MDM? Thanks.
Hi I wonder if you can help me we have been using custom data on Samsung Xcovers to display information about out app in soti for about 12 months with no issue however around 4pm yesterday the custom data stopped displaying within the fields on the portal. When i look at the logs there is the following error message. Error message received from device (Failed to parse XML file(SAXException) /storage/emulated/0/Documents/XXXXXXX.xml (filename masked)
Our whole device estate is Samsung and we are slowly transitioning every device enrolled via enterprise enrolment with a managed playstore. We’ve recently found that the default Samsung screen recorder app is uninstalled from the enterprise enrolled devices and can’t seem to restore it. We have found the package name and tried to script it via MobiControl but no luck. Any suggestions on how we restore the built in Samsung app? It’s normally just accessible by swiping down from the top of the screen.
Hi all, We have some Samsung tablets in our environment. But they keep switching WIFI profiles. We have one staging profile using a WPA2 passphrase and a cert based wifi. After switching to the production wifi (cert based) the device keeps switching back now and then. With our Zebra devices we are able to use the MX framework. But there is nothing like that on a Samsung tablet. Does anyone have something to resolve this?
Hello, Is there a script to set a default launcher for AE Samsung devices? I see there is MX configs for Zebra, but not seeing anything for Samsung.
Dears, I am trying to enroll Samsung Mobile A01 Android 10.1, the steps i did is: - Brand new mobile, Start, set the link on google email, AFW#mobicontrol (Android Enterprise) and it install the agent with no issue, and when you go to my SOTI License , you can see that it took a license, and you can run the application and add the enrollment id, until this point everything is fine, but after enrollment id success, the Soti Mobicontrol agent open and it give a msg, Your License is not Activated, this could take until hours sometime foe it to find the license and work and some time it dont. Mobile Samsung Galaxy A01 Version 10.1 Android any support on why its takes long time to work ? and the cure for it.
Hello,I’m trying to remotely wake up Android Tablets. The situation is that I have a number of Samsung Galaxy Tab A (2016) tablets that are configured with a lockdown for customers to use. We have been getting complaints that staff are getting tired of having to wake the tablets up every morning. The tablets are in enclosures that and they can’t reach the buttons to wake it up. The tablets are on Android 8.1 SOTI we are using is 14.4We have disabled the daze mode and set the screen time out to 5 or 6 hours. Our initial tablets that never turned off had to be replaced due to burn in so leaving them lit up overnight isn’t going to work out that wellI’ve tried sending scripts like unlock and they don’t seem to do anything no error nothing. However, if I send reset /s as a script command it reboots, if I send lock it locks so it is executing some scripts.The tablets being what they are don’t have the double tab to wake option.When I remote to them and used the home button they wake up fine so the connection is fine.Ultimately I was hoping to use the task schedule to send the script but if I can’t get it to work as a one off it seems unlikely it will work with the schedule.Anyone run into something like this or have any suggestions?
Hello. We have MC 14.4 OnPremise and some Samsung Tab A6 (Android 8.1.0, AE, COBO, afw#mobicontrol) enrollment. For a few days we have realized that all devices have "Agent Outdated (Upgrade Required)" icon.The agents version are between 13.7.5.103 and 14.1.8.111 If we start the agent upgrade from the web page, the warning "Invalid device software version (Device is not allowed to upgrade)" appears. All devices allow remote control, but we can't manage any profile/package (Install/Removal Pending). I can't even remove LockDown. I have a deployment out of control completely. Any idea, please.
Hello, Does anyone have any experience in configuring and enabling hotspot while in lockdown? Ideally, we would like the end-user to have this functionality as it's needed for work use to connect our RFID scanners in the field. I know there is no such feature in SOTI Settings and I am not sure if there is a way to script it via a shortcut on the lockdown. Models: S7, S8, S8+, S9, S9+, Note8, Note9, Note10, A50 (some models are AT&T firmware and some unlocked) OS: 7.11, 8.0, 8.1, 9.0, and 10. DA+ 95% majority, only about 10-11 devices enrolled with AE.
Hello, We are currently using a mixture of Telecom Expense Management (TEM) and a simple HTML lockdown we've developed internally. The issue we are currently facing is since we have such various devices in our possession, developing a lockdown and system to issue it is challenging. We currently only have one lockdown profile and this has some issues with some models. We've discovered today that some of our devices have different application names for the dialer. One uses "com.samsung.android.dialer" and the others seem to use "com.samsung.android.contacts/com.android.dialer.DialtactsActivity" from my testing. Is it possible to include two package names in the lockdown but only show the one installed on the device? I'm not entirely against having another profile, but I feel like it might be more work in the future if we ever need to modify these profiles later on. Another issue that we've encountered is that the user cannot modify settings on the device. I believe in the past they were able to modify the device settings unless we checked the "disable settings changes" under the status bar in the lockdown menu. I could technically install the SOTI settings application, and will likely do so, but it does not have the ability to adjust the hotspot on the device and some of our users need access to modify the hotspot settings. MobiControl Version: 14.4.8.1043 Agent version: 14.1.8.1111 Models: S7, S8, S8+, S9, S9+, Note8, Note9, Note10, A50 (some models are AT&T firmware and some unlocked) OS: 7.11, 8.0, 8.1, 9.0, and 10. DA+ 95% majority, only about 10-11 devices enrolled with AE.
Hello, Recently we've been seeing S10e devices enrolled in MobiControl are rebooting into recovery and not allowing the phone to boot without doing a factory reset. Are there any known issues with the S10e and MobiControl? Or any solutions to this problem?
Hi everyone! I've encountered with a quiet strange behavior of Samsung devices. When I'm trying to migrate my enrolled in SOTI 13 Samsung device(Xcover4s) using script with few Writeprivateprofstring commands, after enrolling in SOTI 15, it wipes completely to factory defaults. My steps were: - In SOTI 15 SHA-1 is enabled for enrollment rule. - MobiControl agent is up to date. - SOTI 13 device profile is clean and with any rules or restrictions. Same in SOTI 15 - With Writeprivateprofstring I'm adding a certificate key, new deployment server, and device rule tag. - Restart agent and forcing to connect with Connect -f. How can I evade or disable wiping my device after enrolling? Thanks for your help
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.
