unknown host (gethostbyname failed) : 80072ee7

Article
2016-05-25

Question

_{Wednesday, May 25, 2016 1:34 PM}

Hello,

Below error received in the smstsl.log

unknown host (gethostbyname failed)
hr, HRESULT=80072ee7
sending with winhttp failed; 80072ee7
Will retry in 6 second(s)
Retrying... TSManager
CLibSMSMessageWinHttpTransport::Send:

System is not joining id domain and receiving the below error. Other workstations are joining in domain during the OSD.

Attempting to join and create account with OU
Result= 0x0000054b
Attempting to join and create account, without OU
Result= 0x0000054b
Attempting to join within the OU
Result= 0x0000054b
Attempting to join without OU
Result= 0x0000054b
Failed to join domain. The account may not have permission
The specified domain either does not exist or could not be contacted. (Error: 8007054B; Source: Windows)
0, HRESULT=8007054b (e:\nts_sccm_release\sms\client\osdeployment\osdjoin\main.cpp,420)
DoNetJoin( joinType), HRESULT=8007054b (e:\nts_sccm_release\sms\client\osdeployment\osdjoin\main.cpp,509)
Finished with error code 0x8007054b OSDJoin 5/25/2016 6:28:06 AM 2356 (0x0934)
Process completed with exit code 214794375
!!
Failed to run the action: Join Domain or Workgroup.
The specified domain either does not exist or could not be contacted. (Error: 8007054B; Source: Windows)

Verified the NetSetup.LOG and below is the message.
NetpCheckDomainNameIsValid for abc.com returned 0x54b, last error is 0x0
NetpCheckDomainNameIsValid [ Exists ] for 'abc.com' returned 0x54b
NetpJoinDomainOnDs: Domain name is invalid, NetpValidateName returned: 0x54b
NetpJoinDomainOnDs: Function exits with status of: 0x54b
NetpDoDomainJoin: status: 0x54b

Let me know is it a machine specific problem or something else

All replies (6)

_{Thursday, June 16, 2016 8:49 AM ✅Answered}

I found the problem. Model name in the BIOS is incorrect. When it comes to the Driver installation of the step, drivers are skipped due to problematic model is not found as per the condition

Thank you.

_{Wednesday, May 25, 2016 3:55 PM}

You'll have to do some troubleshooting as this really has nothing to do with ConfigMgr.

0x80072ee7 means the system cannot lookup the name in DNS. This can be for many different reasons including a DNS issue, misconfigured DNS on the client, connectivity issues on the client, missing network driver on the client, etc.

Jason | http://blog.configmgrftw.com | @jasonsandys

_{Monday, June 6, 2016 2:16 AM}

Dear Sir,

You could attempt to join domain manually by using the account specified in your TS to verify if it works. Also check that if the NIC driver has been installed correctly.

Best regards,

Jimmy

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Wednesday, June 15, 2016 5:15 PM}

Hello Jimmy,

Able to boot the system using PXE Boot. It means there is a NIC driver in the boot image. Is any other driver required to join in domain.

It is purely a driver issue because same issue resolved for different mode and I am not sure about the particular driver which resolved the problem

Regards,

Boopathi

_{Wednesday, June 15, 2016 5:32 PM}

Hi,

You need to apply the correct NIC driver that matches the operating system you are deploying after the apply image step so that it is present when Windows completes the install at reboot. otherwise it will fail. If you are using the ADK from Windows 10 and are deploying Windows 10 you can use the same driver in the full os.

Regards,
Jörgen

-- My System Center blog ccmexec.com -- Twitter @ccmexec

_{Thursday, June 16, 2016 2:34 AM}

Hello Jimmy,

Able to boot the system using PXE Boot. It means there is a NIC driver in the boot image. Is any other driver required to join in domain.

It is purely a driver issue because same issue resolved for different mode and I am not sure about the particular driver which resolved the problem

Regards,

Boopathi

Hi,

The NIC driver you added to boot image is only used in WinPE. When the Apply Operating System step completes, the computer will reboot into the OOBE not WinPE, so if the NIC driver isn't available in the driver package it will fail at the Join-domain/install ConfigMgr client phase.