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

We come around this strange issue when deploying Windows 10 on HP Elitebook 840 G8 through ConfigMgr operating system deployment (SCCM OSD). The OS deployment process completed successfully however machine could not be joined to AD Domain.

We noticed the following behaviors.

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

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: 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 above error suggest network related issues. However build completes and continue to send status message to ConfigMgr. Hence the network issue was seems to be intermittent.

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

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

Solution:

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

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

The following options didn’t worked for us. let us know in comment if any of below steps worked for you.

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

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

Related Posts

• SCCM Application Deployment Failed with Error 0x87d01106 | ConfigMgr
• SCCM Client Installation Failed With Error Code 0x87d00215
• PXE-E99: Unexpected network error – SCCM OSD
• Configuration Manager OSD task sequence fails with error code 0x80004005
• MECM OSD Task Sequence Failed with Error 0x80072EE7
• SCCM Client Push Installation Failed with Error 0x800706ba
• Failed to Add Update Source for WUAgent of type (2) and id ({ID). Error = 0x80004005
• SCCM OSD – Domain Join Failed with Error code 0x54b on HP Elitebook 840 G8
• ccmsetup failed with error code 0x87d00227
• Fix Application Deployment error 0x87d00213 in ConfigMgr
• CMG Connection Point Status Disconnected | SCCM | ConfigMgr
• CMG Setup – Subscription ID drop down not populating
• CMG Setup – Error when granting Contributor permission to the Azure AD app
• Failed to connect with DP – Error Code 0x8004100e | ConfigMgr | SCCM
• SCCM Client Installation Failed with error 0x87d0027e
• ConfigMgr OSD – PXE Troubleshooting
• SCCM WSUS sync error – Sync Failed – WSUS server not configured
• SCCM Software Distribution Troubleshooting