Forum Discussion
Autopilot enrollment via MDT
Hi all, Within our organization, we’re implementing Microsoft Endpoint Manager to manage devices like laptops. The situation is as followed: laptops are currently unmanaged and we’re trying to...
Hi Harm, the device group query is indeed like the one in your example. The device based on this query becomes a member of this group, but Intune recognizes its membership too late..
Dynamic groups do take time to get Intune config applied, specially for new members. I’m not surprised with this behavior.
Moe
- +1.. Just like Moe tells... Dynamic groups can take some time before they are processed.
https://call4cloud.nl/2020/10/autopilot-the-group-membership-war/- Thanks for your reply Rudy! Seems like I've got to deal with this situation.
- Did you manage to fix your deployment?
- Perhaps you should use the moment when you have to laptop of the user at the office location to register the device in Autopilot by using the get-windowsautopilotinfo.ps1 -online command in the current Windows installation. If it's registered, you can then proceed in wiping the OEM/Previous installation for a new current version of Windows. When the user turns on his/her laptop again, the device will be in the ZTDid group and ready for deployment using Autopilot.
- Thanks for the suggestion! I'll probably go with the provisioning package after a clean installation. This is, for now with the pre-provisioning method included, the most user-friendly way.
