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.
Jun 21 2021 05:25 PM
Jun 21 2021 07:06 PM
Jul 31 2021 04:31 PM
@scubaAl I also still encounter the same issue. A workaround that mostly works is deleting the device from the tenant first, registering it for Autopilot (using csv or graph api), then doing a local windows reset on the device.
Sep 02 2021 01:05 PM
Jan 04 2022 08:28 AM
@Marcos_PaulaHoly crap, you just saved a whole day of manually uploading 200 devices that seemed to be "corrupt". Even MS-support recommended deleting the devices and re-adding them.
Just editing the description on the profile re-applied it correctly.
Thank you so so much.
Jul 06 2022 02:33 AM
@Marcos_Paula Thanks for your suggestion - just testing this now, have the same issue. If it works, fantastic - but so strange.
Basically we have devices in SCCM and co-managed that I would like to be able to autopilot reset. So on one of the test deployment profiles I enabled 'convert to autopilot' and targeted a dynamic azure group with the test devices. They appear in autopilot devices, but profile never gets assigned.
Hopefully this change to description will fix that. But it's a big hassle. Do you need to change EVERY single time you add new clients ?
Jul 06 2022 02:48 AM
Jul 06 2022 08:07 AM