Known issue with “Rename device” setting for Windows 10 devices in the Intune console

[Intune_Support_Team]

Updated 01/25/21 - You can now rename a co-managed device that is Azure AD joined. The “Rename device” setting is currently disabled for Hybrid Azure AD joined devices. Intune Engineering is continuing to work with our Windows and Azure Active Directory teams to investigate this feature and restore it’s functionality within Intune. Stay tuned to this blog for any future updates regarding this feature.

We’ve discovered an issue with a new feature that was recently released in the console. If you manage Windows 10 devices, you may have seen a new “Rename device” setting in the console to rename an enrolled Windows 10 device. We’ve found that the renaming flow using this setting might not complete on Windows devices that are joined to on premises Active Directory, including Hybrid Azure AD joined devices. This setting has now been temporarily disabled for Hybrid Azure AD joined devices to prevent device login errors.

Here’s the current experience in the Intune console. When you go to Devices > All Devices and choose a Windows device, you will see an option to rename the device. On renaming the device, the new name is reflected in the Intune console and in Azure AD. However, we’ve seen some cases where the new device name is not reflected in the on premises Active Directory.

This can result in login errors where a user may be able to log on to their device initially but may experience single sign-on (SSO) errors when they try to login again after a password change.

Engineering is still working to understand the cause and remediation. We've temporarily disabled this setting in the console for Hybrid Azure AD joined devices and Azure AD joined co-managed devices (you can now rename a co-managed device that is Azure AD joined) until we have a fix for this issue. Stay tuned to this post for more information as we investigate.

Blog post updates:

• 5/17/19 - This post previously shared that the impact was limited to Hybrid Azure AD joined devices. We've since updated the post to include Azure AD co-managed devices.

• 8/7/19 - We’ve received reports from customers around this issue. Engineering is still continuing to restore this feature within the console.
• 1/17/20 - We've followed up with the team, and they are continuing to work with the respective teams on this feature.
• 12/30/20 - Updated post on current investigation status.
• 01/25/21 - Updated post that can now rename a co-managed device that is Azure AD joined.

[AlexandrosAP]

Hello Intune,

we are having a very serious issue with Hybrid AAD Joined Windows 10 machines and our MDM users.

They are able to see their Windows 10 Corporate-Owned Hybrid AAD Joined machines in the Company Portal and from there, issue a Refresh (Wipe) command! This is very dangerous as it allows end users to reset their assigned company machines through their mobile.

I have already been informed by Intune Support that this is a known issue and should be resolved.

The logic here should be that if a Windows 10 Domain Joined / Hybrid AAD joined machine is Corporate owned (GPO or SCCM used for automatic enrollment), the "Enrollment user" shouldn't be able to act against those systems. Only designated entities should.

Please raise this case's impact as it could really cause issues where users unknowingly do such actions (rename should also be blocked for them) as these devices are not under their ownership, rather they are company resources.

Thanks

[Neil Petersen]

Hi,

Any update on this issue? we are still seeing updates to hybrid join devices still not being reflected within On-Premise AD.

Thanks,

[taslanpour]

Any idea when this will be resolved? We would like to have the ability to rename computers from the Intune portal. Waiting anxiously on this!

[Jim McKay]

Any chance that what was done to block this functionality could be preventing hybrid joined  machines from being renamed period??? .... even locally from the machine itself? ... i have an autopilot joined machine that neither I (with domain admin priviledge and local admin) nor the end user (local admin) can apparently rename his machine... we both get "access denied" when we attempt to do so... the machine is here in the office. 

[taslanpour]

@Jim MCKAY 

I'm having this issue only with my PowerShell scripts - When I deploy the script for AzureAD joined devices the script works perfectly and the computer name changes. But when the machine is a Hybrid domain joined device, the PS script fails. Of course, getting the reason for the failure is near impossible with the Intune portal so... I'm just stuck with it for now.

[MHagreis]

can we get an status update form someone form microsoft as this still a problem with or organization

[Jim McKay]

It appeared to have been addressed at least for us.... my most recent hybrid joined autopilot box renamed fine... 

[Philip Kluss]

It's still an issue for us.  I just renamed a hybrid joined device using the Intune console and now I get the following error when attempting to sign in to the device with an AD account -- "The security database on the server does not have a computer account for this workstation trust relationship."

[Stephan Mey]

We are facing the same issue after renaming a test client via Intune -- "The security database on the server does not have a computer account for this workstation trust relationship."

[DeanBrightonNTT]

Can confirm that I am also having the rename issue. Windows 10 1909 and Hybrid AD Join. Is there a way to turn this feature off per tenant to prevent people breaking users' computers?

[Brachio1370]

We are having the same issue. This is making Autopilot nearly unusable in a Hybrid scenario. We are forced to join on-prem first, and then rely on gpo and multiple reboots to register MDM etc. All this just to let us chose a name without a forced prefix and a random number.

We would be less irked if there was a workaround of some sort (without having to install SCCM), no matter how technical. Renaming doesn't happen that often, but it is pretty vital when we need it.

[tech22]

Similar issues with our tenant

[Philip Luke]

Im having a similar issue, but for me when the Computer Object is renamed in AD DS, and the Azure Connector Sync makes the change in Azure AD (for Hybrid Domain Joined Win10 devices), the Intune obect device name doesnt change. 

Update - The object is removed from Intune but the local Win10 device then complains when trying to 're-enroll' with :-

[DeanBrightonNTT]

This will probably be the case until AAD Connect Syncs the computer object again.

[Philip Luke]

Thanks @DeanBrightonNTT , the connector has completed a few syncs. The Azure AD object name is correct, but it's not correct in Intune still.

[Sujith Suriya]

Autopilot Deployment Mode: HydridAzureJoin

Issue: Hybrid Azure AD Joined devices looses the workstation trust relationship after renaming the device from the Intune Portal. 

after renaming it gets reflected in the Intune portal but not in on-prem activedirectory. In my opinion, this has to be addressed as soon as possible because there are no alternative ways to figure this out. (May be I should give out a try re-naming it using GPO).

I had to rename the device because of the device configuration domain join profile limitation where it does not allow naming the devices with %Serial% or %random%. 

Troubleshooting performed so far:

1) did Initial Sync on AD Connect Server - no luck

[Sujith Suriya]

I tried changing it from the device like the usual way and it worked.  I was able to see changes on on-prem AD and after a sync it has also updated on azure ad and Intune as well.  but this is a kind of a manually work and it would be great if the Intune connector can do this update, as it has all right delegation rights over the targeted OU.

[MilSak]

Autopilot Deployment Mode: HydridAzureJoin

Same Issue here:Hybrid Azure AD Joined devices looses the workstation trust relationship after renaming the device from the Intune Portal or from AD.

Is there any updates on this fix.

[HARIB520]

We can give a try

https://oofhours.com/2020/05/19/renaming-autopilot-deployed-hybrid-azure-ad-join-devices/amp/

[AMDf7]

Is it resolved in Windows 10, version 2004?

[AadilTeeluckdharry]

Hello , do we have an update with regards to this issue? I am running Windows 10 version 2004 enrolled in Intune. I still need to disjoin domain and rejoin post renaming to make it work. This is not feasible for my pool of devices.

Would be great to have an ETA for the issue to be fixed!

[dcorona1360]

Our Organization is heading to Hybrid Azure AD Join for our Windows 10 Computers and would love to have this renaming devices resolved. Is there any update for this issue?

[Dr. Jeffry A. Spain]

@dcorona1360 I've heard nothing. This issue and others make using Intune in a hybrid AD environment really problematic. Do you have any news for us, @Intune_Support_Team ?

[Brachio1370]

Not sure if this will help anyone but this is the recap of my testing of Hybrid device renaming:

- Logging as local admin and manually changing the name of the machine: It works

- Remotely using Rename-Computer powershell command, works. 

Both actions above see the change of name reflected in Endpoint Manager. If joined by Autopilot, only the Hybrid object changes name, the Autopilot (duplicate?) AD joined object stays the same, although I haven't found any issues.

- Rename Device in Endpoint Manager. Does not work. Worse, it breaks DC trust for all user's devices. I haven't found a way to recover this apart from resetting and reenrolling.

- User changing name in Company Portal: Nothing happens. All the AD and AAD names stay the same. It seems to just update the "Display name" for the user.

Can anyone else replicate the above?

[simenvag]

@Intune_Support_Team,

Any update on this issue? This is an important function within Hybrid mode.

[divadiow]

also need an update please @Intune_Support_Team 

[HARIB520]

https://oofhours.com/2020/05/19/renaming-autopilot-deployed-hybrid-azure-ad-join-devices/amp/  was worked for me on 1909. also changed to my requirement like ABC-%SERIAL%.. only problem is if the same device some reason if required reset ,we have to delete the record. but rest all working.. changed both AAD & HAAD device records!!!

[Intune_Support_Team]

Hi @Dr. Jeffry A. Spain, @simenvag, @divadiow, thank you all for your comments. Intune Engineering is continuing to work with our Windows and Azure Active Directory teams to investigate this feature and restore it’s functionality within Intune. Though we don't have an ETA to share, stay tuned to this blog for any future updates regarding this feature.

[Andy_Blogged]

Hello Intune Team,

are there any news about renaming "Hybrid Azure AD Joined" devices, which are published with AutoPilot?

In our (and in other customers) case(es) we can't rename a computer account is located in Active Directory and in Azure AD Endpoint Manager. 

Target: Rename the computer account in Endponit Manager and get the result with replication in Active Directory. 

Is there any timeline to solve this problem from microsoft intune team?

Regards 

Andreas 

[lahsr]

Same Issue as @Andy_Blogged 

When an autopilot hybrid joined device is created, it makes 2 objects in Azure AD. One of them is "Azure AD joined" and the other one is "Hybrid Azure AD joined"

When we rename the device, it is synced with the object in:

• Endpoint manager
• Hybrid Azure AD joined object
• The object in onprem AD

But it does not sync with the object that is Azure AD joined.
Hope this can be resolved

Regards
Lasse

[vikasnaru]

Any update on this to get this working so that Hybrid machines can be renamed 

[dbroughton]

The way I do is login as domain admin onto the laptop.   Logon to your VPN/network if necessary. Goto advanced system systems.

In computer name enter the new name you need. Wait a few seconds for it to make the change and reboot.

This renames AD/AAD and intune device names (I have done this successfully on over 100+ devices)

[DeanBrighton]

Come on man.... Did you not even read this thread?

[andy_blogged125]

Hello Dean,

i'm shure you didn't read this blog exacliy enought.

To change computer names in Azure/Intune/ActiveDirectory is not the problem, but change computer names from machines are depolyed by AutoPilot in Intune Console is not supported. You can't change this computer name neigther in Intune still in ActiveDirectory. This names are fixed and you are not able to syncronize the names with your local AD.

Regards

Andreas

[DeanBrighton]

The whole thread is about "Known issue with “Rename device” setting for Windows 10 devices in the Intune console". We can rename devices by logging onto each of them, as per the post above, but that is NOT practical in a corporate environment, with any significant device count. We have now learned to work around this limitation, thanks Michael, so it is not that much of a deal. I have been following this since Nov 2019, see my comment above, and know what this is about.

[RuhnkeSam]

Was this request just forgotten?  Are there any updates at all?

[dkafrissenrvk]

Anyone else still having this issue.

We have just begun experimenting with implement Autopilot and are having very disapointing and incosistent results.

The failure to rename is an especially galling one.
After autopilot brings the machines back up, we tried renaming from intune but it keeps failing, says it restarts (it doesn't) I then rename in AD from the machine and while it shows in my ADUC as correct Azure is still not seeing it, and insists it's the old name.

So I'd love to know if MS has done anything to address this.

Thanks

[Andy_Blogged]

@dkafrissenrvk

I can see, nothing has been changed :|

Microsoft didn't understand the problem of consitently machine - names onPrem and in Intune or AutoPilot.

What a pity!

Regards 

Andreas

[David Taylor]

Any updates on this? Is this even being worked on, or is there a way to prompt the technician to set a hostname or even use the serial during the Hybrid Azure AD join Autopilot process instead of using random computer hostnames? The reason we want/need this is that it is much easier for users to rattle off ABC22000621, than it is to rattle off (not to mention memorize) ABCFkZttbHmEwBZ, especially when we need to either remote into machines to troubleshoot things or deploy things to specific devices. I, and probably most IT professionals consider this to be a high priority need with Autopilot.

Additionally, we use a company for imaging devices before they are shipped to our offices / employees. Unless that company provides us with the current hostname, serial number, and assigned asset tag (which becomes the hostname), we can't rename them.

[CSU_Scott]

Good afternoon, 

I just tested renaming a Hybrid Azure AD joined device which led me to this known issue.  Any update since the last update 18 month+ ago?

-Scott

[Simon1980]

Looks like the issue is still not resolved, because I get an error each time I try to rename Hybrid Joined Computer.

Action: Rename device to UTCHNB532A

Status: Failed

Date/Time: 22.9.2022, 13:31:59

[sheldondickinson]

2023 and the issue remains

[nicoserup]

Renaming device from azure is still not working June 2023. 

We have just configured autopilot in our Hybrid azure AD enviromnemt 
This is a pretty big deal for us. 

Come on Microsoft, we believe in you! 

[jameslgwct]

The rename device function doesn't work very well for us either. We have an autopiloted Azure AD joined device which didn't have a group tag assigned to it when it was first switched on - the deployment profile which defines the device name is assigned to a dynamic group of all devices with the group tag.

I subsequently renamed the device from Intune - Properties - Rename and gave it the correct naming structure. Intune shows a device action of Rename device and that it was successfully completed. On the device, it shows the correct name. But the Intune portal still shows the autocreated DESKTOP-XYZ1234 name that it gave the device and Azure does too.

[dkafrissenrvk]

I've just had to revert to disconnecting from Intune, then logging in as local admin, then renaming, then rejoining the domain and then connect to intune again.

[nicoserup]

@dkafrissenrvk - We do this too. But you dont have to login as local admin, you can log in with a normal user, even without administrative rights, and go to settings and press "rename device" and it will prompt for admin credentials. Hence saving you time. 

[dfeifer]

Just recently had to do this with my own work machine. I was working through some problem machines and realized my own device was no longer showing in intune even though dsregcmd shows as being managed.

+----------------------------------------------------------------------+
| Diagnostic Data                                                                              |
+----------------------------------------------------------------------+

AadRecoveryEnabled : NO
Executing Account Name : ------------------, ---------------------
KeySignTest : PASSED

DisplayNameUpdated : Managed by MDM
OsVersionUpdated : Managed by MDM
HostNameUpdated : YES

Last HostName Update : SUCCESS
Client Time : 2023-09-20 20:20:40.000 UTC
Request ID : d878f7db-09a1-43cf-84d8-6055dde8d478
Server Time : 09-20-2023 20:20:41Z
HTTP Status : 200
Server Message : The attribute 'hostnames' value(s) were successfully updated

[Benjamin Donato]

We also are unable to rename a HAADJ device in Intune. Our computer technicians are also unable to rename these devices manually using their domain accounts that with admin rights on the computers. The only account that works is my own domain admin account to change the name. The vendor that provides us support told me that I needed to stop changing computer names after deployment or wiping because is it doesn't work well and just let Autopilot rename devices. Our organization still relies on the computer name to provide specific information (who, where and what).

[shawntran]

Has this ever been fixed?  Five years and we still can't rename AP Hybrid devices?

[Andy_Blogged]

Well, this issue has been never fixed from Microsoft side. 

Result was, that we never used Autopilot with automatic register the machines in Intune, cause the divice-name can't changed. Last week an external consultant confirmed us this behavior. 

Regards

Andreas