Update Assignment IME Slowness - Resolved?

[Matt.Wreede]

I tried search, and found nothing. If I missed it, 100% my bad

4 months ago:

https://www.reddit.com/r/Intune/comments/1lg7rno/pmpc_updates_assignment/

From here:

"Hey, I've just spotted this (along with other Patch My PC colleagues) and would like to say that we are exploring workarounds to provide a reduced client overhead for large app assignment numbers like the numbers you mentioned.

There are members of the team right now trying a few creative solutions, and although we can't give you a timeframe, we do take this feedback at a high priority."

Has anything happened with this? I am mildly playing Devil's Advocate here, as we're primarily a ConfigMgr shop, but as we go down the path of 'moving to the cloud, powered by the cloud' and stuff, this thread caught my attention. as it is now, we use SUGs (in ConfigMgr; props to David James, I love you so much I have a photo of you on my wall), and it works great, since SUGs were designed logically and with love; we see no silliness.

but, if we take that same SUG and lol-it into Intune, with 700 patches... well... I get scared.

So, is this an active issue? Was it fixed? Make your script faster? etc etc? Building an Agent, calling it CCMEXEC2.exe? A man can dream.

A man can dream.

[Andrew Jimenez (Patch My PC)]

Not resolved quite yet. There are multiple possible solutions, deployment to specific groups instead of All Users/All Devices (no specific plans here at the moment), and using native detection rules instead of script detection. We are working on the backend to support native detection rules, once those backend changes are made, we can then focus on adding native detection rules for our apps, the tough part is going to make them as accurate as our script detection rules, as the native rules in Intune are not nearly as flexible as a PowerShell script. I'm really bad at timelines overall, so I would just say to look for that improvements sometime in 2026.