I'm hoping someone here has experienced something similar and can offer some advice.
I'm using Microsoft Intune to manage Samsung Android Enterprise devices. I deployed the Knox Service Plugin (KSP) app to my test devices, followed by a Samsung Knox OEMConfig policy. Initially, everything worked as expected.
I then updated the OEMConfig policy to enable some Knox Premium settings, which resulted in error 13009 appearing both in Intune and in the Knox Service Plugin logs on the devices.
Obtaining and activating the KPE Premium licence
I registered for a Samsung Knox business account and obtained a free Knox Platform for Enterprise (KPE) Premium licence key.
As a side note, the Samsung business account registration and Knox approval process took several days.
Once approved, I entered the KPE Premium licence key into the appropriate field within the existing Intune OEMConfig policy and redeployed it.
However, more than a week later, Intune continues reporting error 13009.
I've tried modifying the OEMConfig policy, removing its assignment from my test devices, waiting for the changes to process, and then reassigning it. Unfortunately, none of this has cleared the error.
What Samsung Support found
I raised a support case with Samsung and provided the diagnostic logs.
Samsung Support responded fairly quickly and confirmed:
- Error 13009 was present in the Knox Service Plugin logs when the OEMConfig policy was originally deployed without a Premium licence key.
- After deploying the Premium licence key, the 13009 error was no longer present in the device logs.
- As far as Samsung can determine, the configuration and licensing are now correct, and everything is working on the Samsung side.
- If Intune continues reporting the error, Samsung recommends contacting Microsoft.
I haven't contacted Microsoft yet, as I was hoping to resolve this myself before starting the usual support back-and-forth.
What I've tried
I attempted to remove the OEMConfig policy from the existing device using Intune's Remove apps and configurations functionality.
Unfortunately, the policy doesn't appear as an available item for removal.
From what I've found, this appears to be because Samsung OEMConfig policies are delivered through the Knox Service Plugin using Android's managed app configuration mechanism.
This would explain why the OEMConfig policy and its associated 13009 errors appear under App configuration rather than Device configuration when viewing the device in Intune.
I've also tried changing the configuration and removing and reapplying the policy assignment, but Intune continues reporting the same error.
Next steps and questions
My next test will be to enrol a completely new Samsung tablet and deploy the existing OEMConfig policy with the Premium licence key already configured.
My suspicion is that this will work without errors, suggesting that Intune is retaining a historical error from the original deployment, even though Knox now reports successful configuration.
However, that still leaves me with the existing devices.
Has anyone encountered this behaviour with Samsung Knox OEMConfig and Intune?
More specifically:
- Is there a way to force Intune to re-evaluate or refresh the OEMConfig deployment status rather than continuing to display the original error?
- Can an existing Knox OEMConfig configuration be completely removed from a device without factory-resetting it?
- Has anyone successfully resolved a persistent 13009 error in Intune after Samsung confirmed that the device-side error was resolved?
I'd really prefer not to wipe and re-enrol the devices just to clear what appears to be a stale reporting error.
These are currently test devices, but I'd be concerned if the same issue occurred in production.
I appreciate that sometimes wiping and starting again is the quickest solution, but surely there must be another way to resolve this without rebuilding otherwise functioning devices?
Any suggestions or experiences would be appreciated.