Machine Rename - Azure AD
Win10 machines joined to azure AD - if they get renamed this isn't reflected in Azure AD or Intune.
Anonymous
shared this idea
As per the status update earlier, this will be available in the next version of Windows 10.
For managed devices, Intune will set the changed name
61 comments
-
Stas Sultanov
commented
Feature does not seem to work
Win10 pro 18363.900 AAD joined
renamed several devices after join (no way to set name during first windows run)
changes are not reflected in AAD -
Anonymous
commented
We have a hybrid AzureAD environment and have not yet adopted inTune. We now run a PowerShell script every week to correct the Azure displayname for any computers that may have been renamed. The script is based on the ‘AzureAD’ and ‘MSOnline’ PowerShell modules; mainly built around Get-AzureADDevice piped to Set-Azureaddevice -DisplayName.
-
Al
commented
Hang on. How can you mark this as COMPLETED??
We just tested with a device enrolled in Intune. We renamed the computer locally. The new name was never reflected in Intune. We have hundreds of devices in Intune that still show their OLD name not their CURRENT name! Which makes doing anything with them highly problematic, since we are never sure if we are dealing with the right account.
Here's an idea. Instead of continually rolling out new features, Microsoft, how about you focus on fixing, actually fixing, the current 'features'.
This one problem makes it very difficult to recommend InTune to anyone.
-
Matt
commented
Windows 10 1909 Azure AD Hybrid Joined devices do not update name in Azure after renaming on-Prem even after several days! only way to 'update' the name (provided you can locate the correct machine (since the only way to located a renamed machine is to look up it's 'DeviceID')) is to dsregcmd /leave... dsregcmd/join. Which means if (like us) you have already deployed a bunch of renamed machines out into production you now have no easy way of determining the identity of those machines in Azure AD.
-
Eric
commented
Devices using Windows Version 1909, changed the device name via Intune. It changed the devices name, but Intune still showing the old Device Name.
Which next version of Windows will this be fixed in? Was using 1903 and updated to 1909 and still no fix.
-
Maxim van Luttikhuizen
commented
26-03-2020:
Renaming the Azure AD Joined device does work. It takes about 30-60 minutes till the new name is shown in Azure AD.Windows Enterprise version 10.0.18363.418
The device is Azure AD Joined and uses Microsoft Intune as MDM. -
Anonymous
commented
It is still not working. If you change the name of a 1909 Windows 10 client in AD on-prem, the change will not appear in Azure AD. What's the workaround? Deleting the machine in Azure AD, Hybrid-Join the machine again? Really? LUL
-
Jean-François HIVERT
commented
I confirm this issue:
- Windows 10 1909 with name DESKTOP-xxxxx
- Adding this computer to Azure AD
- Renaming this computer to new nameOn Azure AD, this device has always old name.
I can not rename from Azure AD admin center. -
Thomas-Louis Laforest
commented
I can confirm the problem is still there.
Computer name was change on the pc, AD is updated, but not Azure AD -
Josh Villagomez
commented
Is anyone seeing the same behavior with Windows 10 Hybrid-Joined devices (non-Intune enrolled)? For example Win10 1903+ builds that are hybrid joined. You rename the PC within the device. Then, you export the change by running a delta sync cycle on Azure AD Connect. Does Azure AD portal show the updated name?
-
Oliver Graß
commented
The problem seems still to exist, the device name and also the Windows version, the registered owner, last activity is not updated or maybe not updated in time. How long does the update need?
Because of that ist actually not possible to handle devices in a propper way in AzureAD because you cannot see which device is still in use by which user and which device needs maybe deleted or deactivated or needs a Windows update!
-
Rob Nicholson
commented
I've just renamed a new 1903 test VM from it's default of DESKTOP-812PU5F to HELIOS005 and it's still showing as it's original name in Azure. When they say "next version of Windows 10", which version do they actually mean? Is there something else we have to do?
-
DFree
commented
I just tested this last night, device was running Win10-1903 and can confirm when I changed the device name on the system manually (with reboot), I watched it change in AzureAD.
-
James Dean
commented
Is the change implemented yet? I see several PC's with the same name still and different users logged in.
-
Anonymous
commented
For me works, I renamed computer name under Intune portal, and it's works, but in Local Active Directory still old name :| I missing something ? I have Intune Connector for AD installed and works, Windows Autopilot also works for me with user-driven. So , who know, what it can be ?
-
Anonymous
commented
Hi, can you please confirm which version of Windows it will be available in?
-
Jonathan
commented
Jan 2019, requesting this feature to be implemented as it's a real pain that devices won't automatically update PC Names in Azure AD compared to local AD.
-
Robert Roose
commented
I found this: https://www.petervanderwoude.nl/post/rename-a-device-via-windows-10-mdm/
Tested it, and it works!Create a custom Windows10 device profile
Use OMA-URI: ./Device/Vendor/MSFT/Accounts/Domain/ComputerName
String value: PCNAME-%SERIAL% -
Eddie Jackson
commented
The machine name can be easily controlled using WMI and reg keys. I was able to deploy a PPKG, under the security context of System Account, perform enrollment of a domain computer, and keep current computer name.
-
Rob Nicholson
commented
Great news - at the moment we have to logon first with Microsoft account, rename laptop, reboot, add to Azure AD, login with Azure account and remove the unwanted Microsoft account. Plus removing the Microsoft account always leaves the profile in C:\Users requiring manual delete.