OfflineIdentification in windows11 24h2 xml deployement

Question

I'm using OfflineIdentification
https://learn.microsoft.com/en-us/windows-hardware/customize/desktop/unattend/microsoft-windows-unattendedjoin-offlineidentification#xml-example

, but it doesn't seem to work with windows11 24H2, the machine believes it is in the domain but it has a random hostname.

This clearly seems to be a bug

with or without hostname entered in the conf it changes nothing.

It worked very well with previous versions of Windows 7 to Windows 11.

Answer 1

Hi,

Thank you for posting in Microsoft Q&A forum.

1,Please help check the c:\windows\debug\netsetup.log (detailed logging of join attempt) and c:\windows\setuperr.log (errors only) to see if there is any further information about the domain join failure.

2,Are you using Configuration Manager to deploy Windows 11 to your clients? If yes, we can use task sequence domain join account to join a newly imaged computer to a domain during Windows Setup.

Thanks for your time. Have a nice day!

Best regards,

Simon

---

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.

Answer 2

After going through trial and error, the culprit is the attribute microsoft-windows-setup-/UserData/FullName [1].

To reproduce the error, create a unattended.xml file using :

• add fullname userdata information [1]
• use offline join component [2]

The installation finishes, but after reboot the machine has a name derivated from the FullName attribute instead of the name included in the djoin blob (eg. FullName attribute has superadmin value, and machine name ends with the SUPERA~1 name). And thus the domain join is not working.

The exact same unattended file was working properly using Win10 23h2 iso (machine with correct name from djoin blob and properly join to the domain).

The documentation [1] and [2] does not mention anything about deprecation or caveat.

The MDT xml validation tools "Windows System Image Manager (SIM)" says the file is properly formatted.

Best regards,

Simon

• [1] https://learn.microsoft.com/en-us/windows-hardware/customize/desktop/unattend/microsoft-windows-setup-userdata-fullname
• [2] https://learn.microsoft.com/en-us/windows-hardware/customize/desktop/unattend/microsoft-windows-unattendedjoin-offlineidentification-provisioning-accountdata