Aug 06 2019 04:10 AM
Aug 06 2019 04:10 AM
When import device information for Autopilot, if the devices already registered to Azure AD, the profile status in Windows Autopilot devices have not changed from ”Not Assigned”.
After deleting the device from both Autopilot devices and Azure AD, and import again, it has changed to ”Assigned”.
It is the same behavior at import csv file, which created by PowerShell script manually or use Autopilot profile to convert targeted devices.
Note that we had not applied Autopilot enrollment to all devices, and we use a security group referring ”ZTDId”. And a security group specified Azure AD devices for convert.
And, it seems when import csv file to Autopilot, devices register to Azure AD automatically. If we remove it from Azure AD, the device information will not re-register automatically. Or will it work with the security group of all Azure AD device?
I want to know:
1. Import Autopilot information of devices that already registered to Azure AD does it work?
2. With the security group reference ZTDId, does it work?
3. The best practice to register Autopilot information, that device already registered to Azure AD and Intune
Thank you for reading. If you know anything about it, please teach me.
Jun 05 2020 02:01 PM
Having the same issues here (UK)
When importing Devices into the Autopilot, any devices using the [ZTDId] are not having profiles assigned.
I have also noted the 'sync', is roughly instant, this is abnormal as usually, it takes a few minutes before successful sync is reported
Jun 05 2020 07:31 PM
Jun 06 2020 04:05 AM
In my instance, the property 'Convert all targeted devices to Autopilot' is already configured to yes.
However, Devices registered for autopilot are not pulling a profile.
Jun 08 2020 09:16 PM
Could you add the PCs to regular Security group and assign them to the deployment profile? It might be the dynamic group somehow dropping the PCs.
Jun 09 2020 04:02 AM
So I have raised this as an MS Support Ticket, they have informed me that currently there is various region issues with profile deployment using Windows Auto-Enrollment. These are backend issues and are currently being resolved.
Although I have not seen any public comms from MS for this.