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.
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?
As of MobiControl 2024.0, I saw that SOTI added OEMConfig management through Profiles. Can anyone clearly explain the pros & cons to this over an application policy using managed app configurations? One reason might be due to some specific network or Google Play restrictions (outlined here), but other than that, what practical benefits do I have as someone that doesn't have those restrictions? I also noticed that SOTI is pushing the legacy Zebra OEMConfig app when deploying the profile, so I've got more questions that documentation doesn't appear to discuss. They do "recommend" profiles over policies, but don't explain why. (This seems to be a common theme in their documentation, a lack of detailed reasoning and impact). How does SOTI determine which app generation (new vs legacy, Zebra) and which app version to deploy? Does SOTI ever update the OEMConfig app or not? How often and under what conditions? Do we have any controls over it? Do the same rules of managing OEMConfig still apply (i.e. tattooing settings to a device) or is there some other functionality to be had? Thanks!
Hello! I am looking for a method of downgrading from Android 10 to Android 9.I have downloaded the HON660-P-88.00.22-(0214).zip (1.6GB) file from honeywell.Issue: When creating a file sync and attempting to upload the .zip it errors out.Created a package and when uploading the package into mobicontrol another error out. I think it might be caused due to size of file?The goal is to standardize our Honeywell endpoints to only run on Android 9. any insight is most welcomed!
Can anyone provide any insight into where SOTI is with OEMConfig Feedback Channel support, specifically Zebra? I'd like to be able to effectively troubleshoot OEMConfig settings or maybe someone has a better way.
There's not a lot of OEMConfig documentation out there that I've been able to find. One basic question that I have, specifically for Datalogic, is if Android Enterprise enrollment is required or if the OEMConfig advanced configs can still be used with Android classic?
Hi! Is there anyone who have gotten OEMConfig (Zebra) to work in the Application Catalog Rule with managed google play store.From what I understand you should be able to add a config to the application when it is installed onto the devices? Like for example Google Chrome which also supports "Managed Configuration"
I can't believe it's finally here. Has anybody started using it with SOTI yet?
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
