Forum Discussion
Android Devices Not Evaluating
To check, are you using Android Enterprise?
What method are you using, COBO, COSU, COPE?
The first thing I'd change would be dynamic groups, they are old hat & unreliable. The MS preferred way is to use filters. Making these changes alone reduced our build time from 1hr to <10mins in like-4-like scenarios. from experience, the use of DDG's could certainly explain this.
- UpNorthIntuneMar 21, 2025Iron Contributor
Yes to Android Enterprise.
Corp Owned Dedicated Device.
I am using dynamic groups to link to the enrolment QR code.
My other Android devices enrol on different qr codes build in 15 minutes, depending on the apps.
Whilst on to MS yesterday, they never suggested a different way to enrol the devices or not to use dynamic groups.
Thanks for your reply.
- piersdcwwMar 21, 2025Copper Contributor
A lot of first line MS support aren't that experienced (based on my experience with them), not surprised to hear that. Filters are, on the whole, much better - clearly depends on the situation. In short, any dynamic group with devices should be looked at and converted to a filter, reference here: https://learn.microsoft.com/en-us/mem/intune-service/fundamentals/filters-performance-recommendations
Changing DDG to filter would resolve timing issues. Different profiles with the same DDG's could still experience different performance issues. However if it's still not resolved after 24hours then sounds separate issue.
I have seen this a few times, and it was a mixture of local network issues to the device, performance (as above), and also service issues - never got to the bottom of that, just magically resolved a few days after contacting MS support. Sorry I can't be more accurate on that :/
- UpNorthIntuneMar 25, 2025Iron Contributor
Hi,
I agree with your comment about MS 1st line :)
Going round in circles with them.
Setting up new profiles, and groups and then going off on a wild goose chase on an a different issue.
Have tried to escalate the ticket but getting nowhere fast.
This issue has been happening for nearly two weeks now.
I will look into the filters method one MS has resolved this issue.