SCCM OSD – Domain Join Failed with Error code 0x54b on HP Elitebook 840 G8

When deploying Windows 10 using SCCM OSD on HP EliteBook 840 G8 devices, you may encounter a puzzling error: domain join failed with error code 0x54b. Although the operating system deployment completes successfully, the machine refuses to join Active Directory, leaving administrators scratching their heads. In this guide, we’ll walk through the symptoms, root cause, and practical steps to resolve this issue so your deployments run smoothly.

We noticed the following behaviors.

Setup Windows and ConfigMgr, step reboot the machine, the configuration takes 15-20 minutes, and then continue with the rest of the Task sequence steps.
The Task Sequence continues to send status messages to SCCM, and the build completes successfully.
Machines do not join the Active Directory Domain.
The OS deployment on other hardware models works fine from the same network without any issues.

The following issues are reported in log files:

C:\Windows\panther\UnattendGC\Setuperr.log

[DJOIN.EXE] Unattended Join: NetJoinDomain failed error code is [1355]

[DJOIN.EXE] Unattended Join: Unable to join; gdwError = 0x54b

C:\Windows\panther\UnattendGC\Setupact.log

Unattended Join: Calling DsGetDcName for corp.xyz.com

[DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 10 seconds…

[DJOIN.EXE] Unattended Join: NetJoinDomain failed error code is [1355]

[DJOIN.EXE] Unattended Join: Unable to join; gdwError = 0x54b

Cause:

The error indicates a potential network-related issue. However, since the build completes successfully and continues to send status messages to ConfigMgr, the problem appears to be intermittent rather than a complete network failure.

Further investigation and information available on other blogs helped us to conclude the following points.

HP Elitebook 840 G8 do not have an in-built NIC card and a USB Type C to Ethernet adapter was used to connect the machine to the LAN.
There was a delay in network initialization when the machine rebooted during Setup Windows and ConfigMgr. The setup continued to try Domain join for 15-20 minutes and then timed out.
The network initialization worked fine at the next reboot, and the Task Sequence execution was completed successfully. The client sends all status messages to SCCM.

Solution:

Based on the information available on different blogs & forums, we tried the following options. However, none of them worked for us.

We were able to build the laptop successfully (with Domain join) using the docking station.

The following options did not resolve the issue for us. If any of these steps worked in your environment, please share your experience in the comments.

Disabled fast boot in BIOS
Updated the BIOS to the latest version
Included the latest drivers in the SCCM drivers package
Added a step after “Setup Windows and Configuration Manager” to delay the execution of the next step.
Added an additional step to retry the domain join if the machine is not yet joined to the Domain. The step executes if the following WMI condition is met

SELECT * FROM Win32_ComputerSystem WHERE NOT Domain LIKE "%FQDN%"

Subscribe to Techuisitive Newsletter

Be the first to know about our new blog posts. Get our newsletters directly in your inbox and stay up to date about Modern Desktop Management technologies & news.

Cause:

Solution:

Related Posts

Subscribe to Techuisitive Newsletter

Recent Posts