Forum Discussion
Muliple Entra AD objects for the same device
- Nov 07, 2023
Today, i got a bit of history which might partially explain what is going on.
It seems they enrolled devices with Intunes before they configured AD Connect.
However this might explain some of the Azure AD joined devices, but does not explain why some (although a minority) have been registered in 2023.
Today I noted the attribute DeviceVersion, al the Azure AD joined devices have DeviceVersion=2. Been looking for info regarding this attribute, but failed to find any besides this:
-DeviceVersion
For internal use only.
Type: Int32
Position: Named
Default value: None
Required: False
Accept pipeline input: False
Accept wildcard characters: False
Today, i got a bit of history which might partially explain what is going on.
It seems they enrolled devices with Intunes before they configured AD Connect.
However this might explain some of the Azure AD joined devices, but does not explain why some (although a minority) have been registered in 2023.
Today I noted the attribute DeviceVersion, al the Azure AD joined devices have DeviceVersion=2. Been looking for info regarding this attribute, but failed to find any besides this:
-DeviceVersion
For internal use only.
Type: Int32
Position: Named
Default value: None
Required: False
Accept pipeline input: False
Accept wildcard characters: False
Will monitor closely to see if still double entries are created.