Solution to OSD issue 80072ee7

posted in: Blog | 26

I’ve had some problems recently with deploying clients in my lab environment. The problem I was having was this:

1. Client boots up and receives boot image = fine
2. Client loads Windows PE = fine
3. Client restarts as soon as Windows PE loads = not fine

I started up the installation again and pressed F8 before the computer restarted and went to X:\Windows\Temp\SMSTSLOG\smsts.log and had a look.

In the log I found this error:

Unknown host (gethostbyname failed)
sending with winhttp failed; 80072ee7
Failed to get information for MP: http://sccm.newtech.local . 80072ee7

I tried to ping my SCCM server called “sccm”. Worked perfectly. But then I tried to enter in the whole FQDN “ping sccm.newtech.local” and all of a sudden the name was not able to be resolved. Why was this happening? Tried to ping sccm.newtech.local from another server and it worked perfectly.

The reason for this is that SCCM OSD is reliant on DHCP and receives the DNS server that is specified in the DHCP scope.

This is how I solved it:

1. Go to the DHCP control panel -> DHCP Scope Options -> Right-click -> Configure Options

2. Select “006 DNS Servers” and then add the IP adress of the DNS server. If it’s on the local server, enter the IP (ie. and not the loopback address (

This worked for me! Feel free to drop me an e-mail if you’re experiencing issues with this.

26 Responses

  1. This article is outstanding, helped me solve the issue! Many thanks

  2. Good to hear, thanks! 🙂

  3. I have the same problem. But my DHCP is the router. How would someone use the steps you mentioned. Thanks

  4. 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.

  5. that was the perfect solution! thanks for your infos! now the client is installing… great!

  6. Tnx m8, worked like a charm!

  7. DreamensioN

    Great post Daniel – thanks for figuring this out. I just had this exact same issue and this was the cause.

  8. You are a life saver!!!

  9. Thanks!!!!!!!!!

  10. Datrion Griffin

    This worked for me also.


  11. Mohammed

    Bingo. Thanks Mate.

  12. Kevin

    Thanks mate! this worked for me 2!

  13. Terence

    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

  14. William Lee

    You Did It!!!!!!!!!!

  15. Didn’t help me 🙁 Mine was already set to the IP’s of my 2 dhcp servers 🙁

  16. Thanks, it was very helpful…….

  17. Matt Sample

    AWESOME!! Thanks!!

  18. Spencer

    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.

  19. Absolutely brilliant, thanks so much for this!

  20. Joseph Priolo

    THANK YOU! Worked for me! 🙂

  21. 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?

  22. Geovan

    Thanks, Sucess!!!

  23. Umer Hakeem

    Thanks Worked also for me !!

  24. You are my hero! Thank’s

  25. Mattias

    Hi Daniel
    Just used your guide to help a customer. It is still valid after all these years 🙂 amazing.

  26. I’m glad that it helped 🙂 I have heard from customers where this also helped them out. Things have a tendency to not change 🙂

Leave a Reply