Back to top

Knox Service Plugin frequently asked questions

Last updated September 8th, 2023

Knox Service Plugin is a free application on Google Play that helps you deploy policies faster. If you want to apply any Premium Knox policies, you may need a free Knox Platform for Enterprise Premium license.

Knox Service Plugin works on any Samsung mobile and tablet device models with Android 9 and higher, and Knox 3.2.1 and higher.

Knox Service Plugin has no device restrictions and it relies solely on the Android version installed on the device to determine compatibility.

No, Knox Service Plugin is not preloaded on Samsung devices. We recommend that you remotely distribute Knox Service Plugin to devices using a Managed Google Play store on your UEM console.

Yes, currently Knox Service Plugin is only installed using the managed Google Play Store. Your chosen UEM partner must support the managed Google Play Store in DO or PO mode to push the Knox Service Plugin app and associated managed configurations to eligible managed devices.

See minimum requirements for details on which UEMs are supported.

New Knox policies are released to customers as a Knox Service Plugin app update in the Google Play Store. IT Admins can easily use the updated app to push new polices to managed devices. UEMs do not need to perform any additional development for each Knox release.

Each Knox policy that Knox Service Plugin supports is published as a Managed Configuration. A Managed Configuration file is an XML file within that particular app. Whenever a new version of Knox Service Plugin including new Knox policies is released to the Google Play Store, IT Admins use the same UEM console to immediately import the new version and see the new policies.

Knox Service Plugin results are sent to your UEM console using the Google Feedback Channel SDK. Note that this functionality is only available after the UEM integrates the appropriate Google API. For limited testing you can enable Debug mode and check the Knox Service Plugin application UI on your test devices to see the following:

  • Input profile received
  • Result of each policy (success / fail)
  • Error information for policies that fail

As a general guideline, we recommend that you use the built-in features that your UEM console provides, and use Knox Service Plugin only for applying additional policies that are available only through Knox Service Plugin and KPE.

For example, lets say you want to disable Bluetooth on a device. If your UEM console already supports disabling Bluetooth, then don’t use Knox Service Plugin to disable Bluetooth.

If the UEM Console supports all the Knox device restrictions you want to apply on the device, then set up the policy with the UEM console and don’t use the “device restrictions” section of the Knox Service Plugin managed configuration. That is, keep “Enable device restriction controls” disabled.

However, if you need to use even a single device restriction in Knox Service Plugin, then you should turn on “Enable device restriction controls” and then set up all the device restriction controls within that structure.

Currently, Knox Service Plugin relies on a Managed Google Play Store for app installation. Knox Service Plugin can’t be used in an on-premise deployment unless you allow both your UEM and devices to connect to the Managed Google Play store.

Is this page helpful?