Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED SCCM 1906 UNABLE TO PXE BOOT - "FAILS TO RUN TASK SEQUENCE"

  • Thread starter Thread starter soundmagus
  • Start date Start date
  • Replies Replies 15
  • Views Views 6K
Status
Not open for further replies.

soundmagus

Active Member
Messages
35
Reaction score
4
Points
8
HI Guys,

So I have dilligently created everything required for PXE BOOT installing "Bare Metal" machines via SCCM 1906. Below are the error messages i get when attempting this.

1570720769302.png

It seems to be unable to run the task sequence for some reason. I have been at this now for 2 days straight, tried both Gen 1 and Gen 2 with the same error each time.

Can someone please help me resolve this?

many thanks,

Mark
 
Error 8004005 is a generic error code, going to need a deeper dive into a log for whatever caused the 8004005.

As you say "Gen1/Gen2" that sounds like you're doing Hyper-V VM's, one of the first errors most peole run into on those is setting the startup memory too low for the Windows Install's liking. Just a guess in the dark at this point though.
 
press f8 to open up command prompt and i think you go to C: and get the SMSTS\smsts.log
 
hyper V - error.jpg

This is the final error that comes up.

The VM has 4GB of RAM.

How do i read the smsts.log using the F8 command? I have managed to get to the destination but am unsure how to read the file on the VM.

thanks for your help.

Mark
 
SyncTimeWithMP() failed. 80072ee7.
WinHTTP error (8007), last 16 bits says "12007" in decimal:

ERROR_WINHTTP_NAME_NOT_RESOLVED
12007
The server name cannot be resolved.

Check your network configuration, verify basic network and DNS services.
 
is this a lab? do you have dns server? network connectivity is there but as Sam points out, it couldnt resolve for sccm server.
 
SyncTimeWithMP() failed. 80072ee7.
WinHTTP error (8007), last 16 bits says "12007" in decimal:

ERROR_WINHTTP_NAME_NOT_RESOLVED
12007
The server name cannot be resolved.

Check your network configuration, verify basic network and DNS services.

Thanks again Sam, i have managed to resolve that but still getting weird error messages. I ghave now been at this today for 5 hours with no success, hope you can help me out.

I have attached another smsts.log file.

Mark
 
is this a lab? do you have dns server? network connectivity is there but as Sam points out, it couldnt resolve for sccm server.
Hi Edy,

I have posted the latest smsts.log below.

This is a home lab.

I have one DC running ADS, DNS, IIS, WSUS.
1 SCCM Server and several clients in Hyper V.

Mark
 
failed to request for client
SyncTimeWithMP() failed. 80072ee7.
Failed to get time information from MP: http://CONFIGMGR.soundmagus.local.
Failed to select MP TSPxe

Is the network access account configured ?. Setting the time correctly in the BIOS / firmware should resolve the issue.
 
Hi Guys,

Thanks for all your help, it was due to me not setting up a DHCP scope on the DC. Timing was nothing to do with it even though it all pointed that way, great fun and learned loads throughout this whole process.

Edy and Sam thanks for your help and patience, you guys are a wee gem :)

Mark
 
Timing was nothing to do with it
Reading errors in SCCM is foggy at times: "SyncTimeWithMP() failed" is the effect, 80072ee7 is the cause. Sometimes you get layered causes: Task Sequence Failed caused by 8004005 caused by 80072ee7.

interesting how you got to load the boot image without having the dhcp scope
Only way I can guess that happened is that he started with a static IP address and when it rebooted it lost connectivity due to a lack of DHCP. But I think this starts out with a system with no OS so how would that be the case... *shrug* :|
 
Status
Not open for further replies.
Back
Top