This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have 3 on-premise computers that are all configured as hybrid devices in Azure AD (let's call them PC1, PC2, and PC3). I've confirmed all 3 show up correctly in Azure, with different Azure device IDs.
When attempting to enroll these 3 machines into Intune, however, if I enroll 1 of them, it works fine, but enrolling either of the other 2 makes the first one vanish from Intune and the new one show up instead. I have no idea why this would be happening, and there are literally hundreds of other computers enrolled without issue, it's just these 3 machines that have this issue.
Has anyone encountered this before and know how to resolve the issue?
How are you enrolling them in Intune? (SCCM Co-management. Azure AD Connect, Autopilot etc) I know that Intune has issues with Hybrid devices that are VMs but normal machines that is strange!
@Covalt, Jonathan G, Thanks for posting in Q&A.
From your description, I know the previous enrolled device will disappear from Intune after we enroll another. Based on my researching, if the devices share the same serial number. the issue can occur. Please check if the two devices are with the same serial number.
To check the serial number, you can run the following command in command prompt:
wmic bios get serialnumber
Please check the above information and if there's any update, feel free to let us know.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
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.
@Covalt, Jonathan G How's everything going? I am writing to see if we have the opportunity to check the above information. If any update, feel free to let us know.
Perhaps fortunately, this is not apparently the issue; these machines all show a different serial number when running that command.
@Covalt, Jonathan G, Thanks for the reply. For such strange thing, it is better to open case to look into the issue. Here is a link with the steps to open case for your reference:
So, they're joined to Azure by AAD Connect, and then they're supposed to be pushed into Intune by SCCM co-management for now (we're planning to eliminate SCCM eventually, and when that happens we'll use GPOs to force the machines to auto-enroll).
When I was testing and discovered this, I was initiating the Intune join process via PowerShell, since SCCM was only enrolling one of the three, but now I know why that was the case, I just can't determine why it's happening.
So how I am doing this is using SCCM Co-management we put them in a group which has intune workloads in pilot and we have a device collection. If you create a pilot collection put the devices in there and if the device is in an OU that is synced with AD Connect it will place it in there. Does sound really strange. Personally instead of Enroling them through powershell you could try this method below? I personally have had no issues with this method. As long as they are both in ADConnect sync and this group it should work. Hope this helps.