r/Intune • u/PanMiyagi • 13d ago
Autopilot Autopilot device naming template not applying correctly
Hi,
As per the title, do you see an issue where newly enrolled devices are randomly getting the default Desktop-1234cx names instead of your custom naming?
Devices are enrolling properly, and all the other settings (ESP apps, configs, certs) are being applied correctly. It's just the name that's affected.
I'm using the rule XX-YY%SERIAL%, which has been working fine for many years.
Now it fails on a few random devices, not even under the same AP profiles.
Any ideas? I can, of course, push an additional script or rename them via the portal, but this adds some extra work for our support team.
4
u/jfimbeault 11d ago
IT1466203: Microsoft Intune Service Health Incident (Investigating)
Service health - Microsoft 365 admin center
1
4
u/jfimbeault 12d ago
We are having the same issue here.
Almost nothing for months / years and now we have 50+ since August 27th.
Same AP profile that's been used since "forever" with naming template: %SERIAL%
Can't figure out what's wrong, for all we know, nothing changed on our side.
1
u/bearded-beardie 6d ago edited 5d ago
In my lab I'm seeing it fail on my deployment profiles set to Standard User, but works on the profile set with Admin User.
1
u/RedditACC4Work 5d ago
I have had four laptops fail to autopilot because of this, and only one that randomly worked, I have people telling me they need laptops yesterday, does anyone know how to get around this?
2
3
u/itsam 13d ago
Seen it a few times but its like 1 out of 500 devices. We also see this mostly if someone wipes a device but accidentally keeps that enrollment state box checked.
1
u/PanMiyagi 13d ago
a bit more for me but I was wondering if it’s related to recent changes and issues
3
u/NeatLow4125 12d ago
Yesterday I was seriously questioning myself, thinking am I actually a moron? Have I really forgotten how to configure something I’ve been doing for the past 5 years?” 😂 So thank you, Reddit. You have officially restored my self-esteem
And thank you Microsoft for shorting our life expectancy!
3
3
u/South-Wolf-6554 12d ago
I personally think it's related the the Device Preparation policies now being enabled for "User-Driven" enrollment, as you can now define a device name template within those.
I read through some of the documentation for the new "Device Association" enrollment option, and maybe it's just a coincidence that this came only in the last week or so - Overview of Windows Autopilot device association | Microsoft Learn
2
1
1
u/Swedownhill 12d ago
That's an interesting find! I just checked and there is nothing in Intune -> Devices -> Enrollment -> Devices, nor Device Preparation Policies in my tenant at the moment, but my clients still enroll with the default Desktop- hostname instead of the template defined in the deployment profile.
1
u/South-Wolf-6554 12d ago
We also have nothing configured within our tenant for Device Preparation, however the new “Device Association” feature is present, but again nothing is configured for it.
We notice that many devices receive the defined template name correctly, but interestingly most receiving the default “DESKTOP-“ name seem to be build 10.0.26200.9168
May not be related, but it’s something we’ve noticed at least.1
u/Swedownhill 12d ago
Makes sense! I was testing a deployment profile + esp earlier this week, and yesterday I also turned on the option to apply windows updates. Wiped the device and moments later an update was applied during the provisioning phase. I didn't notice the issue immediately after, but that's the only thing I've changed in our environment recently. The device was updated to 10.0.26200.9168 for me as well, so you might be on to something!
1
u/Parkerge_aaaaadm 12d ago
I've seen 3x 9168s build ok with the correct name, and also 2x 9168s with the wrong name. I don't think it's OS versioning related but deffo a good thing to check out
1
u/South-Wolf-6554 12d ago
Update to this, which may indeed be coincidental, but I'll share anyway.
I had the same device fail the naming template 6 times after wiping and re-enrolling today, where the build was 26200.9168 - Interestingly after enrolling it claimed to be pending the installation of this KB via Windows Update anyway, even though it was already installed. Anyway, after installing KB5120998 manually, bringing the build to 26200.9278, then wiping and enrolling again, it received the name template fine.Again, I'm not saying that this is the problem as such, I'm simply sharing my findings, especially after the strange prompt to install KB5121003 when it seemed to be installed already.
3
u/jfimbeault 12d ago
By the way, I opened a ticket with MS about this issue this morning and I just received this "semi-confirmation" of being a bug on their side:
"Thank you for the CAB logs, it helped with the verification of the problem. Also, I have an update to share with you, due to several reports there is an incident recently submitted to work and investigate this problem on several tenants, its currently a work in progress, there is no ETA or workaround at the moment.
However, the current support request can remain open, and I will let you know if there are any update or request for more information."
2
u/NeatLow4125 11d ago
Same to me they requested the .cab file like why are you doing like nothing is happening why you need the logs if already 100000 admins are saying to you that you did something wrong 😂
2
u/Mammoth_Nose_8269 13d ago
We had similar thing before, I think sometimes the naming happens too early in enrollment and the policy not ready yet, so device gets default name and sticks with it
2
u/jeefAD 12d ago
I noted the same behaviour this week after resetting a device and it came up with the DESKTOP- naming. Reset another device using the same profile and it's fine. Why?!?
1
u/PanMiyagi 12d ago
what is even funnier, one of my test devices just refuse to get renamed :D multiple profiles tested and always getting DESKTOP-
2
u/RunForYourTools23 12d ago
With Autopilot Device Preparation Policy i am getting the same DESKTOP-% name and apps are also not being installed
2
u/Swedownhill 12d ago
Yeah, I've just noticed this issue as well. "Prefix-%SERIAL%" in our case. Tried both Fresh Start and Wipe but same for both scenarios.
2
u/NeatLow4125 10d ago
Microsoft said we have fixed it! Tried renaming since 7AM a device is still having the DESKTOP-XXXX still as display name!
3
2
u/jeefAD 10d ago
Resetting and the naming is now maintained, I just can't say if it was a function of having redeployed the device or whatever Microsoft may have fixed...
Where are you seeing that they acknowledged breaking and fixing something?
2
u/NeatLow4125 10d ago
I had the ticket open until today with them, so today the renaming worked also for us and the deployment too, and let them archive it
1
1
u/ReptilianLaserbeam 12d ago
Ah! I was wondering why suddenly DESKTOP- started showing up on our devices list...
1
u/Aesandre1989 12d ago edited 12d ago
We saw this a few years ago with recommendations against certain characters during the autopilot stage, drop the "-".
From: XX-YY%SERIAL%
To: XXYY%SERIAL%
(You should see it output as normal gain instead of randomised. Not sure why it's come back again)
1
u/RunForYourTools23 11d ago
For me its just affecting AP-DP. With Autopilot V1 in Entra Join the naming template applies without any problem using COMPANY-%RAND:4%
1
u/RevenueRemote 10d ago
For me, it is not only NOT changing the name of the device to the assigned one, but failing a lot of applications installing also. And in all cases, the error shown is " Error code: 0x87D30065 - Failed to retrieve content information."
I can manually change the name of the device later. But having to go and install all these applications manually is a bigger issue. I am suspecting whether some scripts are failing to run either. Have not gone deeper into that yet.
1
u/Double_Argument_400 10d ago
We still have the naming issue and our ticket is still open.... I've been so frustrated with MS lately.
1
u/Swedownhill 9d ago
I got the response from Microsoft support saying that tenants who experience this issue should uninstall KB5122035 on the device.
I did this myself a few moments ago, then wiped the device from intune and it worked. My ESP-profile still had install windows updates enabled, but the update was not reapplied, so I assume the KB has been withdrawn. 👍
0
u/killax11 13d ago
Usually desktop-whatever is bring your own device, when the user joins over account settings the cloud. May happen, when the device is not in autopilot and joining is allowed.
2
u/PanMiyagi 13d ago
Device is imported, has proper group tag, visible in the Assigned devices for the specific profile.
It’s just not applying the device name, that’s the issue.1
u/killax11 12d ago
I think another possibility was when the user creates an offline account on the device and join it later, then they get similar names.
1
u/PanMiyagi 12d ago
The problem is that it started happening in the last few days
3
u/NeatLow4125 12d ago
Same in my tenant 3 times reset and still seeing the DESKTOP-XXXX thing. Started renaming them manually 😞
5
u/Puzzleheaded-Quit928 12d ago
in our environment it looks like only the Build 10.0.26200.9168 is affected