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, I need to deploy a large fleet of Samsung tablets, and in my company these devices must be configured with static IP addresses. I’m used to working with Zebra and Honeywell devices, where setting a static IP is quite straightforward. I expected to be able to do the same on Samsung devices using Knox Service Plugin (KSP) via the OEMConfig profile, but after reviewing the available payload in MobiControl version 2025.1.0.1007, I can’t find any option to define a static IP, gateway, DNS, and so on. Does anyone know if it’s possible to configure a static IP on Samsung devices through SOTI (KSP or otherwise) without doing it manually on each device? Thanks in advance.
My Customer as an internal fleet of Zebra Products linked to this on-premise server and wants to drive Samsung Phones on A14 that should be outside in data connection.What should be exactly the best practice ? Using Samsung Knox enrollment or Knox LME Work Profile and Google profile As he holds many firewalling rules In each case, what connectivity should be preserved, from on premise server to outside, and from outside to inside ?Any registration and DNS needed ?
Hello i am trying to utilize speed control on a tablet, the lockdown mode is working correctly but i want the speed control to active and allow 3 apps to run while it is active. main one is google maps but the two others need to be active in the background or able to be switched to. when the speed control activates it only shows google maps, there is no option for me to move to the other apps. does anyone know if i need to add these 2 extra apps to the template in order for them to work during speed control. below is the configuration of the speed control and im using the default dynamic template Thanks Noah
A few months ago, we manually enrolled majority of our Samsung devices into the Samsara Driver beta program for testing out new features & giving feedback to Samsara. Now that we are the end of the beta period, we are advising the on-site teams to go through all of their phones manually to unenroll the phones from beta program. On each of the phones, they have to go into the Google Play Store on each phone to remove it from the program, same what they had to do for enrollment. In my testing of removing a phone from the beta program, uninstalling and reinstalling did not automatically remove it from the beta program. Does MobiControl, and I guess Android as a whole, allow IT administrators to either enroll or unenroll devices from application beta programs? All of our Android phones are enrolled into MobiControl as Work Managed if that makes a difference.
Hi the community, hope you're all doing well. Hope someone can help me as I'm starting getting crazy with this point. We have an APN to be setup on all our mobile for our staff to use their dedicated app on different type of device. Crosscall Core X5 and Samsung Xcover7. We created, years ago, a profile with all APN informations inside and deploy it to the group of device. It is working perfectly on Crosscall devices but on Samsung devices, the phone dialing is not working anymore since 10 days. If we setup the APN manually on the device it works, but if it is pushed by SOTI, it doesn't. The only difference between the one pushed and the manually created is the type of APN (default, mms, ....). Via SOTI it was pushing a * which is not recognized anymore by Samsung but still by Crosscall... My problem is, I havemore than 2000 devices working with this APN profile, I don't want to touch the actual profile. I made a clone of this profile and just change the type of APN and now SOTI is not pushing the correct password with a new profile... I dont know why. I tried with a new profile, a clone of profile, .... Everytime the password is false now... I also tried to push the APN via the OEM config of Samsung in SOTI but it doesn't work, the device receive nothing... Any idea? I got more than 500 Samsung devices and really don't want to install the APN manually on all of them... Thank you
Hi all, I'm looking for a javascript that I can run trough the task scheduler to a device that pushes an application to the forefront of the device every 5 minutes when the device is unlocked. (device is Android 14 / Xcover 6 pro Samsung) I have a task scheduler running now with a legacy script that brings the app to the forefront every 5 min (script is: start package.name). The problem with this is, even when the user locks the device, the script will bring the app before the unlockscreen. So i'm looking for a script that says: If PDA locked no push application else if pda unlocked start application every 5 min (bringing the application to the foreground every 5 min) else no push application end Thank you for you help!
I'm unable to take over Samsung devices in SOTI MobiControl without acceptance from the user.Once the user has accepted my request i'm also unable to do any actions on the device.I'm only able to look. I need to be able to take over any samsung device with full control and without any interference of the user. I tried using several plugins but none are working.
I raised this same issue last year, and am wondering if anyone has any permanent solution yet? https://discussions.soti.net/thread/remove-edge-panels-from-samsung-tablet MobiControl Version: 2024.1.2.1046 Device: Samsung Tab A9 (SM-X115) OS Version: Android 14 Agent Version: 2025.0.5.1064 Android Enterprise I still dont beleive there is any native way of disabling the 'Edge Panels' on Samsung devices, either through MobiControl or Samsung Knox Service Plugin. The below script works, but if the feature control profile is changed/re-installed it reverts. writesecureprofstring DeviceFeature DisableEdgeScreen 1 apply featurecontrol I have tried to combat this by adding it as a 'Task Scheduler' in my Feature Control profile, but it doesnt seem to apply. The logs show the script sent through succesfully, but the Edge Panel remains. Again, the script works if i send it to a device manually, just not when it is scheduled in the same profile as a feature control. I have also tried to delay the script by changing it to the following, but again it doesnt work. sleep 60 writesecureprofstring DeviceFeature DisableEdgeScreen 1 apply featurecontrol Are there any better solutions?
Hi all, I'm using Samsung Knox Service Plug-in (KSP) to push policies to our fleet of 2 device types below: Samsung Galaxy Tab A7 Lite (SM-T227U).Samsung Galaxy Tab A9+ (SM-X218U). I followed the steps outlined in these 3 articles to grant Special Access Permissions to SOTI MobiControl and the Files by Google app, but have not seen all policies succesfully apply to the Tab A7 Lite. https://docs.samsungknox.com/admin/knox-platform-for-enterprise/knox-service-plugin/kbas/kba-1261-grant-special-permissions-for-an-app/ https://docs.samsungknox.com/admin/knox-platform-for-enterprise/knox-service-plugin/kbas/kba-1151-policies-not-applying-after-installation-on-device/ https://discussions.soti.net/articles/000002579 All policies are being applied to the Tab A9+, but only some policies are applied to the Tab A7 Lite. I pushed KSP via Managed Google Play, and have tried pushing the configuration policies in both the Managed App Config page and the Profiles section using OEMConfig for Samsung. I have entered valid Knox Platform for Enterprise (KPE) license keys, and yet I'm not sure why all policies don't take effect on the Tab A7 Lite. In debug mode, the Knox Service Plug-in app states all policies have applied successfully, or that the latest policies have already been applied, and yet this isn't true as the special access permissions aren't turned on for MobiControl, one of the policies I configured. I have sent logs, including Configuration Results, Received Policies, and dump state device logs to Samsung support, but no one has been helpful so far. Battery restriction shows as unrestricted when I followed the steps in Samsung's knowledge base. I also don't receive any errors of any kind in the KSP app while debug is on. It only says that all policies have successfully been applied, even though they have not upon checking after, so I'm not sure what to try next. The policies I configured to be pushed are: Device-wide policies (Selectively applicable to Fully Manage Device (DO) or Work Profile-on company owned devices (WP-C) mode as noted) Enable device policy controls ON Application management policies Enable application management controls ON Battery optimization allowlist: com.samsung.android.knox.kpu Package Name for Auto-Launch: com.samsung.android.knox.kpu Enable permission controls ON Permission Controls Permission Policy: Notification Access Package or Component Name: net.soti.mobicontrol.androidwork/net.soti.mobicontrol.notification.SotiStatusBarNotificationListenerService Permission Policy: All files access, Appear on top, Change system settings, Alarms & Reminders, Usage data access, ALLPackage or Component Name:net.soti.mobicontrol.androidwork/net.soti.mobicontrol.ui.MainActivity Permission Policy: All files accessPackage or Component Name: com.google.android.apps.nbu.files The policies not being applied are: All Files Access Notification Access For the apps: SOTI MobiControl Files by Google This only affects Samsung Galaxy Tab A7 Lite devices (SM-T277U). They are running Android 14, although some are running Android 13. The version of Knox Service Plug-in is 1.4.72 (24.06) The Galaxy Tab A9+ (SM-X218U) hasn’t had any issues and all policies are applied successfully. The issue is only with Galaxy Tab A7 Lite devices. Any assistance would be greatly appreciated.
Hello everyone, I would like to know if it is possible to automatically approve the authorizations that MobiControl requests using OEMConfig. In my case it is about Zebra and Samsung devices. Have any of you had any experience with this?
Does anyone know how to block a user on a Samsung phone from accessing contacts on the SIM card using Samsung OEMConfig or any other way?
MobiControl Version: 15.6.1.1048 Device: Samsung Tab A9 (SM-X115) OS Version: Android 14 Agent Version: 2024.1.1.1125 I have noticed that on our Android 14 Samsung tablets, we dont seem to be able to remove the 'Edge Panel' via MobiControl. Previosuly we had done this with an app run control profile that blacklists the Edge Panel bundle ID (com.samsung.android.app.cocktailbarservice). This seems to work for all Android versions apart from 14. On our Android 14 devices, it shows as uninstalled, but it still appears on the device and in the settings app as per the screenshots below. Is there another way that i can bulk remove this from devices without having to manually go into settings on each one and disable it?
Hi, I add a new device to SOTI and when I make remote control(Legacy) the device has the wrong orientation. Any idea how to fix this? Samsung Galaxy Tab Active4 Pro Android 14 Supported APIs - SamsungMdmV57, Samsung RC v1, Samsung KNOX v3.3, Work Managed Device
Hi, We have a problem, import_contacts_vcf %sdcard%\contacts.vcf 1 no longer replaces my contacts but only adds them to the existing contacts. Did something change in the latest MobiControl Agent version? We are running on Samsung A53 5G with Android 14 on latest version. MobiControl Agent 2024.0.5.1062
Hi. I want to setup web browser kiosk on Samsung A7 lite T-220 Tablet - Android 13 When I set surf lockdown item into single app mode it asks for draw over other apps permission, but it is already turned on. I tried native/suppression method lockdown, there is same issue on both. Draw over other apps is allowed, but mobicontrol all the time show notification lack of permission. I want to setup kiosk mode, and restrict user to exit browser. Do you have any idea? Device: Samsung A7 Lite T220 OS: Android 13 Agent: 2024.0.3 Build 1194 Enrolled as Work Managed
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.
