Jump to content


Sign in to follow this  
oxyle

Error 0x80072ee7 during OSD - SCCM 2012 R2

Recommended Posts

Dear IT'ers,

 

A friend of mine ran into an error that is getting really annoying right now.

 

Every time when we install hes lab environment, we keep running into 0x80072ee7 during an OSD deployment.

 

We've done the following:

  • Reinstall the whole environment from scratch.
  • Install a single stand-alone primary site.
  • We've verified the DNS records were made.
  • We've applied CU3 to SCCM before doing anything else in the console.
  • Applied boundary groups
  • Installed the PXE role, and verified that WDS was running.

Now when we start a clean Hyper-V Gen1 machine with a legacy NIC we run into the error above...

  • The VM gets an IP...(During networkboot)
  • The VM can ping everything in the local network.
  • It can ping the SCCM/DNS server on name. However when we try to ping the FQDN of one of these machines it would fail.

I've attached the smsts.log to this post. Hopefully you guys can help!

 

Kind Regards,

Kevin

smsts.log

Share this post


Link to post
Share on other sites

Solved!

 

Turns out the ISP was handing out IPv6 DNS servers inside hes local network. He blocked that in the modem and all of the machines started resolving locally on hes DNS server the management point now!

 

Would have been the last place where I would check...

 

Kind Regards,

Kevin

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...