Back to top

How the Knox Service Plugin managed configuration is pushed to a device

Last updated October 11th, 2024

Categories:

Environment

  • Knox Manage
  • Knox Service Plugin

Overview

This article explains the implementation logic behind KM and KSP, and describes the steps involved with deploying a managed configuration to a device.

How the Knox Service Plugin schema/managed configuration is pushed to a device

  1. Knox Manage sends the Knox Service Plugin schema data to Google.

  2. Google sends the Knox Service Plugin managed configuration to the device, and Knox Service Plugin sends feedback to the Knox Manage server.

    It may take approximately one to two days for changes to be reflected on your device.

  3. When the device’s Knox Service Plugin agent receives the new managed configuration, the agent applies the newly updated policies. If there are no functional changes to the previous policy configuration, the agent doesn’t update the managed configuration.

The managed configuration should be applied with little to no delay, but is subject to server traffic, internet connectivity, and potential product issues. If your changes aren’t applied within 1-2 days, submit a support ticket.

Additional Information

For more details about Knox Service Plugin, see Knox Service Plugin admin guide.

Is this page helpful?