Forum Discussion
Dynamic groups based on device.enrollmentProfileName for WIndows 10 devices
Didn't really find an answer to this and getting a proper answer from support seemed hard because the functionality spans multiple teams. So here it goes. As I read in the dynamic group document...
EnrollmentProfileName is more for Android Dedicated devices.
You could look into devicePhysicalIDs, check out this website: https://docs.microsoft.com/en-us/mem/intune/enrollment/enrollment-autopilot#create-an-autopilot-device-group
You could look into devicePhysicalIDs, check out this website: https://docs.microsoft.com/en-us/mem/intune/enrollment/enrollment-autopilot#create-an-autopilot-device-group
I could, and I am for now.
But that doesn't quench my curiosity about this. 🙂
I've also seen scenario's where suddenly the Autopilot related attributes in devicePhysicalIDs seem to have disappeared. But that is a problem for another time. Haven't been able to replicate that one.
But that doesn't quench my curiosity about this. 🙂
I've also seen scenario's where suddenly the Autopilot related attributes in devicePhysicalIDs seem to have disappeared. But that is a problem for another time. Haven't been able to replicate that one.
- Have you looked into GroupTags?
What they might mean for you?
I haven't seen easy issues with them disappearing.
https://techcommunity.microsoft.com/t5/intune-customer-success/support-tip-using-group-tags-to-import-devices-into-intune-with/ba-p/815336Yes, but the grouptags are pretty much the devicephysicalIDs.
U use them in dynamic groups just the same:
(device.devicePhysicalIds -any _ -eq "[OrderID]:Sales")
I know all that, but I want to know the answer to my question. Out of curiosity. You can solve my problem in many different ways. But my curiosity is only solved with knowledge. 😄
ShellBlazer I'm curious about this too. Were you ever able to find a solution for this?
