Back to top

How managed configuration deployment works for Knox Manage

Last updated July 26th, 2023



  • Knox Manage (KM)
  • Knox Service Plugin (KSP)


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 KSP schema/managed configuration is pushed to a device

  1. KM sends the KSP schema data to Google (Audit log, Request for Management configuration of Google managed app).

    • When the admin sends a policy from KM to Google, KM creates and updates a unique UUID in the profileName field of the KSP policy to check its transmission history.
  2. Google sends the KSP schema to the device, and KSP sends feedback to the KM server (Audit log, Save KSP App feedback).

    • Delays may occur when KSP schema data is delivered from Google to the devices. Changes can take around 1-2 days before being reflected in your devices.
  3. When the device’s KSP agent receives the new KSP schema, the agent applies the newly updated policies based on the currently applied KSP policies.

Based on Google’s logic, the managed configuration should be applied with little to no delay, but further delays may occur based on server traffic. If your changes aren’t applied after 1-2 days, the cause may be server, internet connectivity, or bug issues.

Additional Information

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

Is this page helpful?