Forum Discussion
Is the co-management going to handle this differently when a device is re-imaged?
When a device joins AzureAD and is re-imaged, we notice the device appears multiple times in AAD/Intune as it receives a unique ID. Obviously this does not happen on the domain joined side. Is the co-management going to handle this differently when a device is re-imaged? I know that the Fall Creator's update has a way to reset a device to its original state which would probably help with the multiple instances getting created in AAD/Intune…just wondering if there will be any known issues when the device appears multiple times after a re-image process.
Hi, that's great feedback. Co-management in itself will not create issues, as turning on co-management will simply create that first Intune device record. However, your point on multiple device records as PCs get reset over time is fair. I'm making a note to see if we can better reconcile these records when we know it's the same physical PC.
4 Replies
- Tristan Scott
Microsoft
Hi, that's great feedback. Co-management in itself will not create issues, as turning on co-management will simply create that first Intune device record. However, your point on multiple device records as PCs get reset over time is fair. I'm making a note to see if we can better reconcile these records when we know it's the same physical PC.
- The Windows 10 1709 feature that you referenced, Windows 10 Automatic Redeployment, preserves existing MDM and AAD enrollment information, so no new objects are created. See https://docs.microsoft.com/en-us/education/windows/windows-automatic-redeployment. Overall, this is better than reimaging, as long as you want to start clean.
We are definitely going to try that new route, but we sometimes have to re-image due to hard drive or other problems. Thank you.
Maybe consider also the option to remember the installed Apps. I mean Apps that were "Available" and were chosen by the User.. resetting the device would be smoother then (on the Admin). :)
