Forum Discussion
Autopilot profile is not assigned if a device already registered Azure AD
I went to the deployment profile (with the dynamic group), click to edit the basics information, add some text there in description box and save. The deployment will reload and update devices in autopilot table. Now all are assigned. For me it worked.
- Thank you Marcos I still have no idea why this works but it does.
- THIS WORKS! I will this issue was solved once and for all. Editing the description of the deployment profile and saving so it updates. This will be a pain to have to always remember BUT it will save a ton of time in the long run. Thank you.
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.
- Hi.. Could you share some more information about seemed to be "corrupt" ... not assigned or just devices that weren't retreiving the autopilot profile?
- Well this still happens from time to time. We utilize multiple autopilot profiles with multiple different group tags, and occasionally changing the grouptag on some devices never triggers them to switch to the correct autopilot profile. The solution we do is still just editing the profile that won’t apply, and then it begins updating all objects
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 ?
