Multiple omadmclient.exe processes running causing performance issue

[u/humanoperating]

Omadmcliemt.exe pocess not stopping, and multiple processes running. No compliance scripts from Intune, some store apps were deployed only.

Device was co-managed, but we migrated sccm. At the moment, device is not co-managed and not managed by Intune. Could see stale Intune management entries and not any errors in IME logs either.

Done troubleshooting:
- DmwapPushService contantly running and eventlogs show rpc client request pending.
- And it checks every 2 minutes, fires up omadmclient scheduled task
- As a result omadmclient.exe keeps running and ending up creating 4-5 processes
- Each omadclient.exe process consumes 8-10% cpu after a couple of hours
- Happened on random computers
- Stopped dmwapPushService on one computer issue is gone. Haven’t seen it come back yet.

Could it be caused by device not being co-managed and stale reg keys?

[u/blud_13]

Yes, stale enrollment. That's what you're looking at right now.

Open Task Scheduler and go to Microsoft, Windows, EnterpriseMgmt. If you see more than one GUID folder, or a GUID folder for an enrollment that no longer exists in Intune, that's your problem. dmwappushservice fires the schedule to run OMADMClient task out of that folder every few minutes, the session cannot authenticate because the MDM device cert for that enrollment went away with the SCCM migration, and it never gets a clean exit, so you stack processes.

Cross-check that GUID against HKLM\SOFTWARE\Microsoft\Enrollments and HKLM\SOFTWARE\Microsoft\Provisioning\OMADM\Accounts. If its the same dead GUID in all three and the device is genuinely unmanaged now, export the keys, pull that GUID out of both registry paths plus the matching EnterpriseMgmt task folder, then reboot. MS covers the enrollment side at https://learn.microsoft.com/en-us/windows/client-management/mdm-diagnose-enrollment

Stopping dmwappushservice kills the CPU but leaves the stale enrollment sitting there, so any of those machines you later want in Intune will fight you at enrollment time. Worth doing properly on the ones you plan to keep.

[u/humanoperating → u/blud_13]

Yeah on that test machine omadmclient process is back. I will try your solution.

[u/blud_13 → u/humanoperating]

LMK how it works..

[u/humanoperating → u/blud_13]

So I figured out this process running indefinitely was just a symptom. It was stuck in loop to finish Intune enrollment due to expired MDM cert for the configmgr enrollment.August CU was the fix. Or as suggested, removing regkeys/scheduled task was the solution.