question

PhilipKhoury-8156 avatar image
0 Votes"
PhilipKhoury-8156 asked JeremyDavies-1146 answered

Dynamic group showing serial number instead of device name!

Recently I enrolled a few computers into Intune using GPO (automatic enrollment), all devices names showed in All devices section of Intune, I am using an enrollment profile that has "Convert all targeted devices to Autopilot" enabled.
all devices serial numbers are showing now in the Windows autopilot devices.
From there I change the group tag of these devices to be assigned automatically in to dynamic groups so they will be able to get all the apps and configs assigned to that group.

The problem is that when I open the dynamic group and check the members list, I see the devices serial numbers instead of their names! and non of these devices are getting the apps and configs assigned to that group.
Is this a bug or something? it used to work fine before!!


mem-intune-generalmem-autopilot
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

LuDaiMSFT-0289 avatar image
0 Votes"
LuDaiMSFT-0289 answered PhilipKhoury-8156 commented

@PhilipKhoury-8156 Thanks for posting in our Q&A. From your description, I know that you convert Hybrid Azure AD joined devices to autopilot, but the devices shows the serial number instead of device name. If there is anything misunderstanding, feel free to let us know.

To clarify this issue, we appreciate your help to collect some information:
1.Please show the screen shots of settings about autopilot deployment profile.
2.Please show the screen shots of settings about domain join configuration profile.

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.


· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hello,
Thank you for your reply,
The serial number is showing only when I browse the dynamic group members list like in the photo below, the computers inside the red rectangle are showing serial numbers instead of device name, where the computer inside the green is an example of a normal computer showing its name.
117938-image.png
117930-image.png
117939-image.png


0 Votes 0 ·
image.png (44.6 KiB)
image.png (34.9 KiB)
image.png (42.0 KiB)
PhilipKhoury-8156 avatar image
0 Votes"
PhilipKhoury-8156 answered LuDaiMSFT-0289 commented

Please note that this happens only with hybrid joined computers (enrolled to Intune using GPO), converted to Autopilot, and is not happening when I upload a csv file with the hardware ID of a computer then assign a group tag to it.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@PhilipKhoury-8156 Thanks for your quick update.

From the settings you provided, it seems everything is normal. For this strange situation, it is needed to open an online ticket to double confirm if it is a known issue and find if there is a method to fix it. It is free. Here is the online support link:
https://docs.microsoft.com/en-us/mem/intune/fundamentals/get-support

Thanks for understanding and hope this issue will be solved as soon as possible.

0 Votes 0 ·
AndrewHawes-7045 avatar image
0 Votes"
AndrewHawes-7045 answered AndrewHawes-7045 commented

We are getting the same issue. Also, when clicking on the device the device in EndPoint - Windows Devices - Windows Enrollment - Windows Autopilot Deployment Program - Devices, the "Associated Azure AD device" is showing the device serial number instead of the name.

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@AndrewHawes-7045 Thanks for your feedback.

As I replied to PhilipKhoury, here's support is 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://docs.microsoft.com/en-us/mem/intune/fundamentals/get-support

Thanks for understanding.


0 Votes 0 ·

OK I have done that, Thx anyway @LuDaiMSFT-0289

0 Votes 0 ·
PhilipKhoury-8156 avatar image
0 Votes"
PhilipKhoury-8156 answered LuDaiMSFT-0289 commented

What I found is that the deployment profile is creating another device (with a different device ID and a similar serial number) when converting computers that are auto enrolled to Intune using GPO.
I am sure it is nothing I did, because everything used to work fine and suddenly this started to happen without us changing anything.
Hope that Microsoft consider this issue and try to resolve it the soonest possible.
Thanks

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@PhilipKhoury-8156 Thanks for your feedback.

At the same time, I also feedback this issue. However, I couldn't guarantee that I will get the response at once.

Let's wait for the solution.

0 Votes 0 ·
PhilipKhoury-8156 avatar image
0 Votes"
PhilipKhoury-8156 answered ThomasGarcia-1267 commented

Just to make things more clear:
I am attaching 2 screenshots, the first shows an enrolled device showing its name and serial number,
119953-image.png
the second shows the device in Autopilot devices list (after the deployment profile was applied to it) and it shows that it has another device that has a name matching the serial number associated to it.
and this device is disabled in Azure active directory.
119884-image.png

Thanks



image.png (31.1 KiB)
image.png (398.2 KiB)
· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I'm glad I found this thread. We're getting ready to start using AP and all our existing devices registered in intune need to be converted. New laptops will go through our white glove service using an off-site vendor. We use the Hybrid solution as well for AP and current devices.

When we/vendor upload new devices by harvesting the hash, the above screen is exactly what I see in our AP tenant. We setup dynamic groups to assign the profile, apps, policies. The Azure AD device stays disabled until it goes through AP provisioning. It enables and updates to our pre-fix and the associated intune device updates as well so they both match. As far as I'm aware the associated intune device is the computer name. This works great... until I started exploring existing devices.

We registered our existing devices through GPO the same as you. If I understand correctly it basically uploaded the same information as if you were doing a fresh hardware hash? Before this issue, did the associated intune device (above Azure Ad device) show the actual computer name when you converted them?

I'm afraid of this because I don't want all our AP policies and apps being assigned to existing devices unless we reset them. I just want the deployment profiles assigned so we can use it after the device goes through a whole wipe. Your screenshots is kinda what I was hoping would happen, but if that's not the case then I may need to explore this thread further. Let me know your experience with existing devices and the whole converting.

0 Votes 0 ·

Hello Thomas,
Thank you for your reply,
Before when I first started to enroll Hybrid joined computers to Intune using GPO, and after these devices were converted to AP, the AP devices used to be assigned to the same device name it was converted from.
Recently this stopped to happen, and this was my problem :-).
Any way I found a way to go around my issue and it works fine.
Thanks

0 Votes 0 ·

Hi Philip - How did you end up fixing it?

0 Votes 0 ·
PhilipKhoury-8156 avatar image
0 Votes"
PhilipKhoury-8156 answered

Hi,
By creating device categories and assigning a category to the "GPO enrolled devices", then adjusting my dynamic group rules to include devices depending on their category.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

JeremyDavies-1146 avatar image
0 Votes"
JeremyDavies-1146 answered

Hi Philip,
You describe a workaround to the published issue, but this sounds like you are avoiding the Convert targeted devices process completely (or, you are replicating what it should do itself)?
Are you then also setting Convert targeted devices back to 'No' in your AP deployment profile (to prevent the useless duplicate AAD accounts being created)?

I am getting the same behavior, and am interested to hear how your case with MS progressed.
Did they admit to there being a bug here?

I appreciate that we could do the same as you: set a category and assigning that to the GPO-enrolled devices, but then those devices would surely not show in Intune as Autopilot devices, with the different icon, etc?

Thanks.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.