Skip to main content
AdmMI95
AdmMI95
New Member
September 1, 2026

Experience with Knox Service Plugin in an Android Enterprise Environment

  • September 1, 2026
  • 4 replies
  • 114 views

Hello Android Enterprise Community 😎

We are currently evaluating the Samsung Knox Service Plugin (KSP) in an Android Enterprise environment managed through Ivanti EPMM, formerly MobileIron. As part of this evaluation, we would like to hear from organizations that are already using KSP in production.  We would be grateful for any real-world examples, lessons learned, best practices, or recommendations you could share. If possible, it would also be helpful to know which EMM solution, Samsung device models, and Android versions you are using. Thank you in advance for your feedback and experience!

4 replies

Moombas
Moombas
Level 4.4: KitKat
September 2, 2026

Hi ​@AdmMI95,

what kind of best practice or recommendations are you looking for?

I mean KSP is an app to provide device settings, the default Android API doesn’t (or at least partial doesn’t) provide.
The settings you do there are very dependant on your use case(s).

 

I might have a special view on the settings there but i form my side would do it this way as a general thing:

  • provide all settings you can do via the EMM, not KSP
    • Reason: If you have multiple manufacturers (you never know if this changes), these settings are already ready to go.
    • Additional recommendation from me: Depending on EMM possibilities: Split up the settings as much as you can instead of a huge bundle.
      • Reason: On single changes not the entire bundle needs to be re-pushed to the devices and when the setting runs into an issue, only one setting is stuck instead of all at once
  • Everything special where only KSP provides settings, like DEX or so, must be done inside of it.
    • Sadly settings here can’t be seperated (as i mentioned above) at least as far as i know.
    • Depending on EMM possibilities: When you have your settings done, i recommend to “export” them if possible and save them with a version history, so if it fails you can lookup changes/import old configurations.

But maybe rease your use case of your devices maybe we can then provide more specific recommendations if you want.

    robthenry
    robthenry
    Level 1.5: Cupcake
    September 9, 2026

    The Knox Service Plugin can be useful for managing Samsung devices in an Android Enterprise environment, especially when administrators need more control over device policies. It would be helpful to hear about real-world setup experiences, supported configurations, and any compatibility or troubleshooting issues encountered during deployment.

    Moombas
    Moombas
    Level 4.4: KitKat
    September 10, 2026

    Most of this depends on your setup.
    supported configurations you can lookup when start creating an app policy and activate managed app config. At least in our MDM you directly see what kind of options KSP provides (it’s a long list).

    KSP is only compatible to Samsung devices ofc and as i guess someone investigating it will use latest models, we haven’t seen any compatibility issues yet.

    Same on troubleshooting, KSP ran yet very well equal to other oem config apps (maybe slightly better but as you must use vendor specific oem app, it most likely doesn’t matter to compare in this regard).

    enrique
    enrique
    Level 1.6: Donut
    September 10, 2026

    If you are using Samsung devices, KSP is a must. regardless of the MDM, KSP provides settings that are not available on any MDM, Using KSP with devices running Android 13+, mostly on the A series. 

      Terms & ConditionsAccessibility statement