Forum Discussion

Brass Contributor

Oct 19, 2017

Solved

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 ...

Tristan Scott
Oct 19, 2017
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.

Tristan Scott

Microsoft

Oct 19, 2017

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.

Michael Niehaus

Former Employee

Oct 19, 2017

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.

Jason Burt
Brass Contributor
Oct 19, 2017
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.