Forum Discussion
Android Devices Not Evaluating
Hi All!
I seem to encounter this kind of error several times a year for no apparent reason.
It mainly happens on the Android side of things on newly created setups, and then corrects itself over time, which sometimes can be weeks.
I recently created two Android dedicated device environments.
Dynamic group linked to the enrolment profile name, etc etc
I scan the device and follow the normal process, device get all the way to the end but doesn't receive its assigned apps.
When I check in the Intune Admin Portal, the device is showing as not evaluated.
There is no default compliance policy showing and its custom policy.
When I click on Managed Apps, the list of apps the device is going to receive are showing as pending install.
The Group Membership tab shows the correct dynamic group.
So for me, the setup looks good.
I have left the device for 24 & 48 hours in case its a sync issue.
Enrolled the device via a different WiFi.
Wiped the device and left it 24 hours before enrolling it.
Checked spelling of groups etc.
Anyone else experienced this issue, and found a solution?
I have a Teams Meeting with our external support tomorrow,
Have a good one
https://admin.microsoft.com/AdminPortal/home?#/servicehealth/:/alerts/IT1051473
Looks like I am not the only one affected.
Hello all!
So, the problem resolved itself, MS said it was related to a global issue, and said that it was resolved in a service release. However, when I ask for the service release, or a least some form or documentation, they cannot produce any. I held out as long as I could for an answer but was eventually fobbed off with a recent incident with Android 15 devices that potentially affected my devices. I read what they sent me but failed to see a link, as my device was Android 13 and dedicated.
So all has been well for a few weeks until late yesterday when I created a new Android dedicated setup.
I enrolled the device and again ran into the same issue. I left the device over night, and it eventually evaluated and picked up the default compliance policy, but that is as far as it gets.
I have just wiped the device to try again after double checking the setup was good.
Any anyone else experiencing issues?
Regards
Update
Devices are now enrolling, not 100% smooth but they get there in the end.
MS advised a fix has been applied in a recent service release.
I have asked for a copy/URL for this, but they advise there isn't one 🤔
I'll keep you informed.
Hi, I've seen similar issues on Android, especially with newly created setups. In many cases, devices showing as "not evaluated" and apps stuck in pending install appear to be related to sync delays between Intune and the device. Often, the problem resolves itself after a few days.
I recommend checking the sync logs to see if there are any errors, and confirming that your enrollment profile and dynamic group are correctly configured. If the issue persists even after several days, it might be a good idea to reach out to Microsoft Support for further investigation.
I was on with MS support yesterday and the issue has been escalated.
I'm hoping for another call today with some positive news.
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.
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.
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: Performance recommendations when using filters | Microsoft Learn
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 :/
