Ability to limit CPU usage from the Host Process for OMA-DM Client
We've noticed that our Autopilot (intune managed) pc's occasionally have CPU spikes during the day at seemingly random times (probably based on the Intune scheduled tasks for doing OMA tasks), those spikes in CPU usage are revealed to be due to the Host Process for OMA-DM Client.
This can spike to over 50% cpu and when in conjunction with other CPU heavy tasks can reduce a modern i5 computer to... a slow computer. This is immediately noticeable as it will trigger a FAN to start, so users DO notice it, regardless of the performance degradation.
Please give us the ability to limit this cpu usage somehow, much like how we can with Antivirus applications.
Thank you for considering this.
Noodle Soup commented
One strength of the BigFix product compared to SCCM is the by-design 2% CPU threshold during the background evaluation loop (and the independence from WMI doesn't hurt). This can be set higher at the beginning of a "task sequence" (baseline) and reset at the end. It doesn't apply during an action, just the policy/advertisement/inventory processing. Works well, you should try something similar.