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 am using a cloud mobicontrol server to manage Samsung Android tablets. This has been working fine enrolling tablets until today. I have just tried to enroll 3x Samsung Galaxy Tab Active 3 tablets of the type we have used before. The enrollment process seems to go ok, app deployment rules kick in and apps deploy, but the device sticks on "Device Activation Pending - Activating License with Samsung please wait..."Because it is stuck on that the device doesn't accept profiles (they are assigned but in pending install state). There are no errors in the Mobicontrol logs, and nothing obvious in any of the log messages. Any ideas what to try/check?
I am testing the firewall configuration in the Android Classic Profile, and I am having a problem with the cellular data restriction not applying correctly. I am testing by restricting all network traffic on both WIFI and Cellular for the google Chrome application. I have outlined the process I used below along with screenshots for reference 1. screenshot below displays the rule configuration in MobiControl2. screenshot below shows that the profile was successfully installed to the device 3. screenshot below shows in the Deployment server logs that the Knox Firewall rule is being pushed to the device 4. writeprivatestring_FirewallCommand.png shows the specific MobiControl script commands that are being pushed to the device 5. screenshot below shows the commandin logcat on the android phone the IPTables command being run on the device. 6. logcat_enableFirewallFailed.png - shows the line in logcat on Android where it says "Enable Firewall failed" I have verified that the rules I am using successfully restrict traffic on a WIFI network, but for some reason, they do not work over a cell connection (I am using Verizon Wireless) I have tested on a Samsung J3 and a Samsung S21 using the Samsung ELM agent along with varying OS versions and Samsung Knox versions and I get the same result. Can someone help with figuring out why the firewall rule will not apply over a cellular connection?
hi team, im new at Android devices for using SOTI, so i have problem in start, so how to create a enrollment rule for Samsung A7 devices? Till now I deploy succesfully all kind WIN rules, so please if anyone can help me. Thank you!
Hi, I'm having some issues with Samsung Galaxy Tab A7 running Android 11 and MobiControl. I installed the MobiControl app and enrolled the device. Then the app ask me to enable work profile and uninstall MobiControl app. I would rather use the MobiControl app and avoid work profiles. What am I doing wrong here? Are there any up to date documentation on setting up MobiControl on Samsung tablets? If I ignore MobiControl when it ask to enable work profile, I can see the device as online in the MobiControl web console, and I can remote view, but not control. I can not deploy any packages or profiles.
Hi All, we have a large number and variety of samsung devices with both Android Plus and Android enterprise agents. The majority have SOTI kiosks on them but we see that many are not ever receiving firmware updates. On my personal phone i get a prompt to download and install firmware updates. Would the SOTI kiosk block this behaviour ? we do not use EFOTA services Thanks in advance!
Hi there, I`m facing a issue regarding Samsung Galaxy Xcover 5. I`ve installed an application that monitor the fleet but the users find a way to exit from it and now they have access to google search bar(marked withe the red line) and some apps like google play, google, setting and it`s not ok. I didn`t find a way to block this security breach. As you may find in the picture below, the term "Cautare" means "Google search bar" and "Inchidere totala" means "Close All". The user should`nt have the possibility to leave the app and see these options(search bar and apps). Agent version: 14.5.5, but I`ve tried even with older agent versions but I`m facing the same issue. OS version it`s Android 11, One UI 3.1. Please let me know what to do in order to block the user to leave the main application. Thank you very much for your support.
I have deployed Samsung Galaxy Note phones for several years now, starting with Note 4 and now we have a handful of Note 9s in the field (we do equipment delivery, so I don't need the latest and greatest). I've noticed that when I click the Remote Control function in MobiControl's web interface, I can only view a Note 9s screen. I cannot actually interact with the screen as I did on Note 4-8. I can click the Home, Lock, etc. buttons at the bottom of the remote control interface, but anything "on-screen" does not respond to my mouse movements. These phones are geographically distributed, so I can't bring them in-house to make any config updates; only push out new updates from the Mobi console. How can I remote control my Note 9s? Is this just something that I have to give up on Note 9 and newer phones? Agent Version 14.5.5.1023 Android 10 Note 9 SM-N960U
Good Morning, Our company is in the process of upgrading our employee's devices. The current tablets we use are the Samsung SMT387 & M-T378. We enroll them with Android Plus and push out a profile with Kiosk screen and several packaged APK's for the approved apps. We recently ordered the Samsung A7 lite devices SM-T227U. These come with Android 11 out of the box. I was able to enroll the device with Android Plus. When I went to push our test profile (Exact clone of Production Profile) the entire profile failed. All my packages failed to install with the message being "Failed to Install (Incompatible Platform)". Is there something different I will need to do with the enrollment to get these new Android 11 devices to work with our current profile? MobiControl version: 14.4.6.1047 Agent Version: 14.1.4.1010
Device: Samsung Galaxy Tab Active 2 OS: Android 9 Agent Version: Android Plus ELM 14.5.0.1011 (latest) I'm trying to change the following settings in the Device Care/ Battery Settings. I have tried to identify the setting using the logs and the watchsetting but nothing comes up. Any ways I could set these remotely?
Hello, We are trying to enroll Samsung Galaxy Xcover -devices to SOTI, but have run into problems. I'll try to explain all of our situations as well as possible, but apologies if I forget something. Anyway, the devices run on Android 11, while out SOTI client is running version 15.2. SHA-2 is enabled. First, I have tried enrolling with Android classic Mobicontrol. I found one from SOTI site, that should work. Non-ELM was seemingly not supported anymore, so I tried with ELM enabled device. There is a small problem with it, because our production network for SOTI clients do not have access to public network. In order for me complete the enrolling, I have to switch WLAN networks to a more public one during it. I was able to do this once, but subsequent enrolls fail upon completion and unenroll themselves. After that I have to do enterprise data reset in order to try enrolling again. I decided to try using the more universal Google Mobicontrol afterwards. The enrollment succeeds, but the devices do not support remote control and always install a work profile. I got some guidance from our seller, that I should enroll the device during the initial bootup, by using the camera to read a QR-code from Mobicontrol stage program. That worked on a Zebra device we have, but on Samsung device I ran into different problems. Because our production environment do not have access to Google play, I must do the initial installation on a different network, so the device gan download the Mobicontrol app. After that, the device starts to enroll, but for some reason I am unable to change settings during the installation. On Zebra device I am able to open Android during enrolling (Zebra runs on Android 8), but on Samsung I can't back out to Android during enrollment, meaning I am unable to change to production network. Is this because of a different Android version? If anyone can give me some hints about how should I proceed with enrollment, I would be very thankful.
Hi Community! I have a support case raised with SOTI on this, but thought I would reach out to the community to see if anyone else has experienced this issue so far. We have a wifi payload assigned to our devices via a profile that applies a number of wifi profiles to the devices for the various SSIDs that we have broadcasting around our sites. We also have a DHCP MAC filter applied at our sites. More recent versions of Android have MAC Randomisation functionality and in recent versions (Android 11 etc), it is enabled by default. MAC Randomisation is not suitable in our environment, due to the DHCP MAC Filter. We therefore turn this off for our Corporate SSIDs (not via MobiControl) to allow the devices to seamlessly connect to wifi via the DHCP MAC Filter. The issue we are now facing, is that Android 11 devices on the latest security patches (Details below) have Random MAC turned back on every time the device is rebooted. Random MAC is only turned back on for wifi profiles that we enforce via MobiControl payload. Any SSIDs (Known networks) on the device that are manually entered (not via MobiControl), do not have Random MAC turned on after reboot. This appears to be a bug perhaps, but not sure how to try and remediate against this. Currently, we are having to tell users of these affected devices, not to reboot them. Make: Samsung Model: Various MobiControl version: 15.0.2.1049 Agent version: Samsung ELM 14.5.5.1023/14.4.3.1074 Android OS: Android 11 Knox version: 3.7.1 Knox API level: 34 Android Security Patch June 2021 Devices on previous OS versions and older versions of Knox are not affected.
We have a selection of devices (Samsung SM-T295) which cannot be enrolled. I have tried using our server (on prem) provided Samsung ELM agent and we get the error "This device agent is incompatible with your device. Please contact your administrator". We've also tried the SOTI provided ELM agent from soti.net/oem and we get the same message. We also tried the non-ELM agent but as expected that didn't work either. Has anyone any idea what is going on and how can I enroll these devices? Our server version is v14.4.1.1195, the agent version is v14.5.4.1016. Our server has SHA2 certs. The tablets are running Android 11.
Hello, Currently we try to enroll Samsung tablets in SOTI after a very good experience with Honeywell CT60 devices knowing almost nothing about the "Samsung world".Now, after some days we are still struggling to find a "fast and clean" solution to stage/provision these devices.The first surprise was the "SOTI MobiControl Stage Programmer" where on the WiFi options we had only OPEN/WEP/WPA association modes without the posibility to chose 802.1x EAP (required in our environment)...so a no go scenario?After this we've tried to use the "afw#mobicontrol" method which has worked but based on the agent type (Agent Version 14.5.3.1017) with limited functionalities (Supported APIs Remote View, Work Managed Device)I would really appreciate from somebody with a know-how experience a "little help". Thanks!
We would like to command the lock and unlock device directly into the MC Console as also to install and enable the Knox Guard with no end user interaction. So far, we send a link by script that is opened in Surf and end user has to click next and accept on it. Is there a way to install Knox Guard and activate it directly from MC Console ? In positive case, where should I find a guidance to it ? Is there a way to define the lock command from MC Console to be propagate to konx guard console, releasing the tasks to do it on both console ?
Hello, I have a Samsung phone that is pin locked from an ex employee. when attempting to perform a manual factory reset, the option is not available on the list in recovery mode on the device. Is this something that gets altered by the Mobicontrol console for Samsung devices. when you select the prevent factory reset option in device profile? the device cannot connect to the server for me to perform any script commands. Samsung Galaxy X Cover Pro Android Enterprise Zero touch enrollment Work managed device with Managed google play account Console version 15.2.3.1033, cloud based. I have been told by support that this is a Samsung issue. I'm asking for a second opinion because other android devices I have in production have that option on the list. Any help is appreciated. Seth Spears
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.
