There is an SCCM error, which many people seem to receive.
It’s the following error:
unknown host (gethostbyname failed) sending with winhttp failed 80072ee7.
The problem shows itself by:
- Client boots up and receives boot image
- The client loads Windows PE
- An unexpected restart occurs as soon as Windows PE loads
In this blog post, I explain what the 80072ee7 error is, how you can identify it, and how to solve the error.
Investigate the 80072ee7 error in SCCM
To start investigating the error, you should enable F8 support on your boot image, or temporarily switch to another boot image with F8 support.
As you hopefully know, enabling F8 support on a boot image should be carried out for lab testing as it reveals the network access account and domain join password in cleartext.
Once you have enabled F8 support on your boot image, start up the installation again and press F8 before the computer restarts and open the following file using CMTrace:
Now you might see the following error:
Unknown host (gethostbyname failed)
sending with winhttp failed; 80072ee7
Failed to get information for MP: http://sccm.newtech.local. 80072ee7
Try to ping your SCCM using the non-FQDN name. So, don’t add the domain suffix.
ping <sccm server>
If you receive a successful response, you are still on track with this solution.
Now try to ping the SCCM server using the FQDN:
ping <sccm server>.domain.com
If this doesn’t work, try to ping the server using FQDN from another machine.
If that works, please continue to read.
How to solve the winhttp failed 80072ee7 error
Follow the below instructions on the Windows Server hosting the DHCP role:
1. Go to the DHCP control panel -> DHCP Scope Options -> Right-click -> Configure Options
2. Select “006 DNS Servers” and then add the IP address of the DNS server. If it’s on the local server, enter the IP (i.e., 10.0.0.3) and not the loopback address (127.0.0.1).
That should be all!
In what scenario did you receive this error? Please leave a comment below!
- Solve issue with Secure Boot in Hyper-V on non-supported Operating Systems
- Don’t forget this step if you want clients to PXE boot using SCCM
- The issue with DHCP and WDS on the same server
- Issue with Hyper-V Secure Boot and Verification Error
- How to solve the issue with SCCM looking for policy during PXE
- How to fix error with long serial numbers in SCCM
Subscribe to newsletter:
If you want to receive the latest news for MEMCM, Windows 10, and Powershell, please subscribe to my monthly newsletter!