Hybrid Join Renaming Manually

Question

Hello

As everyone knows, renaming a hybrid joined device is not supported.

I am trying to do this manually but need an expert insight into what issues may arise by the method I am using:

1. Hybrid join runs - has a crazy name....this is where the steps start:
2. Rename the device thru windows while on VPN
3. reboot
4. Rename AzureAD Object: Set-AzureADDevice -ObjectId <objectID> -DisplayName <intended on prem AD name>
5. Rename Hybrid Azure AD object: Set-AzureADDevice -ObjectId <objectID> -DisplayName <intended on prem AD name>
6. Gpupdate /force to update PKI cert
7. Install SCCM Agent

Please by all means tell me what I'm doing wrong or right - leaving it a alphanumeric name is not acceptable in my environment and hoping to complete this as easy as possible for both end user and technician.

DSregcmd /status appears to show the computers is in an OK state however on the Azure side - the azure object has some unknowns (OS/OS version) and on the intune side, it no longer shows corporate or personal (listed as unknown, greyed out).

Thanks in advance,
Sean

Answer 1

Hi,

Thanks for posting in Microsoft Q&A forum.

1,You could try to delete the cert and regenerate a new certificate. Similar thread for your reference:
Renewing machine cert after hybrid joined device rename

2,Some other threads for your reference:
Renaming hybrid joined machines
Renaming Autopilot-deployed Hybrid Azure AD Join devices

Thanks for your time.

Best regards,
Simon

---

If the response is helpful, please click "Accept Answer" and upvote it. If you have extra questions about this answer, please click "Comment".
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.

Answer 2

As everyone knows, renaming a hybrid joined device is not supported.

No one knows this as it is not a true statement. You cannot rename an HAADJ device from MEM admin console, but that doesn't mean that you can't, or it isn't supported to rename the device locally.

There's nothing special about renaming an HAADJ device as long as you rename it locally as noted and while it has connectivity to the on-prem domain that it is joined to -- you should be able to rename it while it is not connected as well but the changes won't be fully effective and propagated until it connects again. AAD Connect will also have to kick off its sync cycle (by default this is every 30 minutes from memory) for the rename to fully propagate as well.

There's no reason to manually rename any objects in AAD for this and that may actually cause issues.