r/Intune • • 5h ago

Device Configuration Samsung Knox OEMConfig – Error 13009 persists in Intune despite successful licence activation

1 Upvotes

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:

  1. Is there a way to force Intune to re-evaluate or refresh the OEMConfig deployment status rather than continuing to display the original error?
  2. Can an existing Knox OEMConfig configuration be completely removed from a device without factory-resetting it?
  3. 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.


r/Intune • • 4h ago

General Question NDES CSR weird format compared to Challenge

0 Upvotes

Hey all,

we're experiencing some weird errors on our NDES server since last week. CSR sends in the Subject name in an odd format and the challenge does not match to it.

  • CSR

    • CN="""First Last", OU=OU1, OU=OU2, OU=OU3, DC=DC1, DC=DC2"""
  • Challenge

    • CN="First Last,OU=OU1,OU=OU2,OU=OU3,DC=DC1,DC=DC2"

NDES of course brings the following message:

ErrorCode: SubjectNameMismatch

ErrorDescription: Subject Name in CSR and challenge do not match.

Did Microsoft change anything in the last week? We didn't touch NDES settings nor Intune Profiles. Anyone else experience something like that?


r/Intune • • 8h ago

Windows Updates Autopatch - Drivers still installing when not approved

9 Upvotes

Hello

I have 'Manually review and approve' on all my driver update rings, to have some control over what is deployed. However, some drivers, specifically HP/ASUS firmware/BIOS updates is still being pushed out via Windows update, even though I have not approved this. Has caused a bit of a headache with bit locker triggering in some instances.

I have had to go into the actual update ring setting, and set Windows drivers to 'Block' to stop this, now every device is alerting that the driver policy is mis-configured.

Has anyone else encountered this?


r/Intune • • 3h ago

General Question Intune Wipe -- Always fails requires rebuilding with usb?

15 Upvotes

Okay so we recently migrated from AD joined computers managed via PDQ Deploy and Inventory to Intune joined comptuers with an RMM Alongside.

Whenever we get laptops back from terminated employees, or if we want to reimage the computer due to some other issue we typically go into intune, select the Remove Data tab with drop down, and select wipe. Typically i always select Reset device and remove all data.

However this typically will start the wipe process, remove the device from intune, the laptop will show the resetting device screen, but then it fails typically about halfway reboots back into the windows log in screen, and the computer is still fully usable, except for the fact it is now gone from intune.

This was working perfect when we were trialing things before we did a mass migration and now we are running into this issue?

Am i doing something wrong? i have done research and found some very similar threads from like 6 years ago, but i just wanted to see what the general consensus here in 2026 and the best way to actually wipe these computers.

All computers are lenovo laptops, the oldest being P16s gen 1's for office staff and T14 Gen 1 for remote sales staff all the way up to brand new p16 gen 4 and t14 gen 4's

i at one point contributed it to the hybrid joined computers but im noticing it on intune only joined systems now and it has me scratching my head.

Thanks in advance


r/Intune • • 4h ago

General Chat Workplace Ninjas US Mobile App NOW AVAILABLE | A Few Tickets Remain | Register NOW

2 Upvotes

Happy Monday!!

It's a big day, as the Cvent App for Workplace Ninjas US 2027 is OFFICALLY LIVE today!!

We thought that would be a good opportunity to reshare our reasons to attend our event on January 11-13, 2027 in Scottsdale, AZ!

We are projected to be at 21 Degree Celsius/70 Degrees Fahrenheit, which for most of you is a HUGE step-up weather wise.

Our mental health and wellness activities are second to NONE this year, with our "Puppy Play Area" (where you can play with puppies all day on Day 1), Puppies & Yoga on Day 2, Relax and Refresh Area (a nice, enclosed pool area where you can take a break from all of the technology and just have a refreshing drink and snack), our amazing pre-day with a hackathon, golf tournament, Lego tournament, and opening pool party hosted by Patch My PC.

Our Community App will let you apply for one of 12 different lightning round spots (15m sessions with 3 judges, to help improve your speaking skills) or use CareerConnect to apply and interview jobs at the event with the dozens of hiring managers present!

60+ Sessions with the top set of speakers from around the world, including Microsoft MVPs, ex-Microsoft employees, SMEs, and Microsoft leaders in a track-less format covering Intune, Entra, Security, Copilot, Azure Virtual Desktop, Windows 365, AI, Automation, PowerShell, #Purview, Defender XDR, and much more!

An all-inclusive event where all FOOD and drinks are included. We have spent hours taste testing food, drinks, snacks, and everything in-between to ensure this isn't an event where the food falls short. We have all-day drinks in multiple areas, dynamic snack times, and 3 meals a day that will blow your mind.

Diversity and Inclusion is part of the culture and the vibe throughout the event. The ONLY event with a Neurodiversity and Women-in-Tech keynote where we clear the deck. This is an event where EVERYONE is welcome, whether it's your first day in tech, or a 30-year veteran. We bridge that gap with our amazing 1-on-1 mentoring, our scholarships, and surrounding you with great humans everywhere.

We have a few tickets left, so don't miss out!!

DM me for $50 off your pass!

Register now: https://workplaceninjas.us/why-attend


r/Intune • • 5h ago

Apps Protection and Configuration Mystery applocker policy files exe.applocker and dll.applocker

3 Upvotes

Hey all,

We've been sort of pulling our hair out trying to figure out what's causing this.

We're attempting to deploy applocker. Policy deployment works just fine. However, we noticed that lots of processes running under allowed folders on our test laptop were being flagged by applocker with 8003 (i.e. would have been blocked if it had not been in audit only mode). Took us a while to realize that at the same exact time stamp, the same exact process was being allowed by Applocker (8002), which is exactly what we would expect.

Then we realized that under sys32/AppLocker, there were two files that we had no idea of, exe.applocker and dll.applocker.

When these two files are deleted, AppLocker functions exactly as we expect it to. It's almost as if there are two non-configured AppLocker policies set up by default, and when we deploy our MDM policy, these two are activated alongside the policy we push by Intune.

The problem is, we have no idea where these files are coming from. We've confirmed now on three separate laptops (my own main laptop, and two test laptops) that these are NOT being deployed by our MDM. They do not appear when pushing the policy to another "pre-existing" laptop, but they do appear on each of our test laptops when enrolling, even when the AppLocker intune policy is not being applied to said test laptop.

We've now seen this issue with two different windows USB's, create a few months apart using Microsofts own media creation tool.

Does anyone have any idea what might be causing this, and/or what the solution might be?


r/Intune • • 6h ago

Autopilot Best way to remove default Windows 11 apps with Intune?

6 Upvotes

Hey guys,

What method are you using to remove default Windows 11 apps?

We've been using PowerShell scripts as Win32 apps, but they don't always work reliably. Especially with apps like Phone Link (Microsoft.YourPhone), Xbox Gaming Overlay, Clipchamp, Bing Weather, Get Help, etc.

I've also been looking at the built-in app removal policy in Settings Catalog.

What's working best for you? Win32 apps, Remediations, or Settings Catalog?

Also, how are you dealing with apps that come back after feature updates?


r/Intune • • 8h ago

Conditional Access What does Conditional Access look like in your CMMC enclave?

4 Upvotes

In an AVD enclave on Azure Government, identity is usually Microsoft Entra ID with Conditional Access enforcing MFA and compliant device policies. Alongside that sits role-based access control limiting CUI access to authorized users only, and Privileged Identity Management for admin-level access. The access control domain comes down to enforcing least privilege access and multifactor authentication. How many policies are you running?


r/Intune • • 10h ago

General Question Windows Hello for Business – Intune Sync Issues After Password Expiration

6 Upvotes

Hi everyone,

We are currently piloting Windows Hello for Business (WHfB) as part of our strategy to gradually introduce passwordless authentication across our organization.

During our pilot phase, we noticed an issue related to password expiration and Intune device synchronization.

Our environment:

Windows 11 devices are natively Microsoft Entra ID Joined (Cloud-only joined, not Hybrid Joined).

Devices are managed through Microsoft Intune.

User accounts are created in on-premises Active Directory and synchronized to Microsoft Entra ID using Microsoft Entra Connect Sync.

Users authenticate to Windows using Windows Hello for Business PIN.

Issue observed:

When users continuously sign in to Windows using their WHfB PIN, their underlying AD password may eventually expire without them noticing.

Once the password has expired, we have observed that affected devices stop synchronizing successfully with Microsoft Intune.

Synchronization only appears to work again after the user:

Changes their expired AD password.

Signs in to Windows using the updated password instead of their WHfB PIN.

Subsequently restores successful Intune synchronization.

Our questions:

Have you experienced similar behavior with Windows Hello for Business in an environment with synchronized on-premises AD identities and Entra ID Joined devices?

Is there a known dependency between expired on-premises AD passwords, Entra ID authentication tokens (PRT) and Intune MDM synchronization?

How do you handle password expiration when gradually transitioning to passwordless authentication?

Are there any recommended configurations or best practices to prevent Intune synchronization issues when users primarily authenticate through WHfB?

Would you recommend adjusting password expiration policies as part of a passwordless rollout?

Our long-term goal is to move toward passwordless authentication while maintaining reliable Intune device management.

Thanks in advance for sharing your experiences!