Table of Contents
Introduction
Sometimes you run into issues that you see now and then. This is one of them.
You will see the following error when the SCCM client failed to run the task sequence due to error 0x80072ee7 in X:\Windows\Temp\SMSTSLOG\smsts.log:
unknown host (gethostbyname failed) sending with winhttp failed 80072ee7.
The problem shows itself by:
- The client boots up and receives a boot image from the distribution point
- The client loads Windows PE
- An unexpected restart occurs as soon as Windows PE loads
You may see the issue described here as part of a client push or when the client is looking for DP locations.
This blog post explains the fatal error 80072ee7, how you can identify it, and how to solve it.
Failed to run task sequence error 80072ee7 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:
X:\Windows\Temp\SMSTSLOG\smsts.log
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).
Conclusion
This error appears because operating system deployment in SCCM relies on DHCP and receives the DNS server the DHCP scope specifies.
In what scenario did you receive this error? Please leave a comment below!
References
Related posts
- How to configure collection updates in SCCM using a Powershell script
- What are maintenance windows in SCCM, and how should they be configured?
- How to deploy HP BIOS settings using SCCM and HP BIOS Configuration Utility
- Solve issue with Secure Boot in Hyper-V on non-supported Operating Systems
- How to solve the issue with SCCM looking for policy during PXE
- How to fix error with long serial numbers in SCCM
This article is outstanding, helped me solve the issue! Many thanks
Good to hear, thanks! π
I have the same problem. But my DHCP is the router. How would someone use the steps you mentioned. Thanks
Open DHCP “Scope Options” and put your router in option name “003 Router”
Make sure that the DNS adress that the DHCP server hands out is the IP of the router. You should be able to set this in the DHCP options on your router.
that was the perfect solution! thanks for your infos! now the client is installing… great!
Tnx m8, worked like a charm!
Great post Daniel – thanks for figuring this out. I just had this exact same issue and this was the cause.
You are a life saver!!!
Thanks!!!!!!!!!
This worked for me also.
Thanks!!!!
Bingo. Thanks Mate.
Thanks mate! this worked for me 2!
Is there anyway to set this in the boot image, im using a very basic router for DHCP and it doesn’t publish the DNS server address. Thx
You Did It!!!!!!!!!!
Didn’t help me π Mine was already set to the IP’s of my 2 dhcp servers π
Thanks, it was very helpful…….
AWESOME!! Thanks!!
Had the same problem but our SCCM server is in a sub domain. I had to create a static WINS entry pointing to the server for the capture to work.
Absolutely brilliant, thanks so much for this!
THANK YOU! Worked for me! π
I have found this error deploying using SCCM 2012 R2, I followed your steps and I still get this error, it has the exact same errors as your screen shot, I can ping my server sccm, but when I use my FQDN, it fails. what other options is there to resolve this?
Thanks, Sucess!!!
Thanks Worked also for me !!
You are my hero! Thank’s
Hi Daniel
Just used your guide to help a customer. It is still valid after all these years π amazing.
I’m glad that it helped π I have heard from customers where this also helped them out. Things have a tendency to not change π
Thank you.
My error is (Failed to get client Identity- 80072ee7) and another error is (failed to get information from FQDN for SCCM SERVER).
You save a lot of time, I stayed with errors around 4 hours until I found a solution from your website.
Thanks and God Bless you
Nashaat Mena
Legend! After upgrading to 1802 my lab broke. Thank you very much! Been digging for a while π
I try everything and still doesn’t work?
Holy grail!it worked. banging my head for past 2 days. thank you very much!!
Glad that it helped!
I just had the issue after I configured HTTPS/PKI in a lab. When trying to set up a machine, it didn’t get the connection to the MP. I had missed setting the Trusted Root Certificate Authority in \Administration\Overview\Site Configuration\Sites, Properties of the site server, Communication Security.
Yep, ran into this today, luckily spent only 1-2 hours researching smsts.log, thank you for this.
No problem, great to hear the article helped you!
/Daniel
Thank you Sir! We had the same issue and by you showing us where the logs were stored was key! Many thanks and cheers
No problem, great to hear the article helped you!
/Daniel