This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(259.20000000000005, 33%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Hello, technical folks. What would cause co-managed devices to appear in Endpoint Management with the name of the Azure AD ID of the device and a registration time stamp? Like this
8998h96f-caa4-45Ff-8622f6f14b5887c9_Windows_05/07/2021_01:07 PM
The device name appears as above which is same as management name. I created a PowerShell script to count the devices and our environment has a count of 2,097 devices in this state (from a total of 12,987),
How do we troubleshoot this or make those devices appear with their correct names. We would appreciate any help with this.
@Madscientist Thanks for posting in our Q&A.
To clarify this issue, we appreciate your help to collect some information:
If there is anything update, feel free to let us know.
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Thank you for the information. The version of config manager on premise is 2103 and it has been cloud attached.
Yes, in Azure AD, the device name for those devices show the same as Intune, the Azure AD ID, instead of the actual name of the device.
I will drive to the location today where we have some of those devices and run a manual sync like you are suggesting and will report the results. If you think of anything else, please let me know.
@Madscientist Thanks for your update. Hope everything goes well.
If this issue still exists after a manual sync, we may need more background information to find the root cause. With Q&A limitation, it is better to create an online support ticket to handle this issue more effectively. It is free. Here is the online support link and hope it helpful.
https://learn.microsoft.com/en-us/mem/intune/fundamentals/get-support
Hello and thank you for the follow up. We have done the manual sync for 300 devices and we have seen duplicate objects. We suspect the manual sync may be creating duplicate objects. We are still investigating and will update as soon as we have more details.
@Madscientist Thanks for your kindness. Any update will be helpful to anyone who may meet the same issue in the future.
Hello, yes, I will provide an update as soon as I have one. People working remote makes it difficult to track down clients. It looks like running the sync manually for the workstation creates a duplicate entry. We are still testing and as soon as we have more details I will post back with additional questions or steps to resolution.
I suppose one pending question for now is why would the manual Sync from the device create a duplicate entry, if the device tried to Azure AD hybrid join and it is showing the object ID? The assumption would be the same device will merge with the existing ID, not create a duplicate entry.
Thank you.
@Madscientist Based on my experience, duplicate entries situation usually occurs in Hybrid Azure AD joined devices. It created an Azure AD registered record and an hybrid Azure AD joined record for the same device during enrollment. However, we automatically clean up the Azure AD registered state when the windows 10 verison is upate to 1803 and above.
https://learn.microsoft.com/en-us/azure/active-directory/devices/faq#why-do-i-see-a-duplicate-azure-ad-registered-record-for-my-windows-10-hybrid-azure-ad-joined-device-in-the-azure-ad-devices-list
In fact, I haven't seen that it creates the duplicate entry when sync the device. If possible, please contact the oneline support to find if there is a method to just keep an entry in background.
Based on my understanding, I think we can delete the older record. Just to be on the safe side, it is needed to double confirm.
Thank you for the information. We have tracked down 7 devices to test with and will post back the results.