PXE Boot Stopped Working

[mkeehn]

I am running SCCM current branch 1606 and have imaged over 500 computers this summer and am down to about 20 that need to be finished. Things have worked great all summer.

 

All of the sudden around noon I could not get any client to PXE boot. I've been searching and trying things for hours and seem to be getting nowhere. Here a portion of my SMSPXE.log

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
5C:26:0A:5C:26:D6, 4C4C4544-0052-4C10-8054-B2C04F355131: device is not in the database.
Request using architecture 0.
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName=""><Machine><ClientID>57dc6c9f-614a-4994-8ce7-b85de04750a1</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="CG320022" OfferIDTime="8/8/2016 5:13:00 PM" PkgID="CG300037" PackageVersion="" PackagePath="http://servername/SMS_DP_SMSPKG$/CG300002" BootImageID="CG300002" Mandatory="0"/></ClientIDReply>
5C:26:0A:5C:26:D6, 4C4C4544-0052-4C10-8054-B2C04F355131: found optional advertisement CG320022
Getting boot action for unknown machine: item key: 2046820352

It then just repeats the lines from 3-6 over and over. So it's contacting the PXE server, it's being seen as an unknown computer (2046820352 is the itemkey of my x86 unknown computer), It's being offered my x86 image (CG300037), but it never goes anywhere from here. It freezes while hanging on the pxe boot screen. Doing the same for a x64 client produces similar result, except it will show me a PXE-E07: Network Device Error when it fails. It finds the appropriate boot image and task sequence in it's log, but does the same thing.

 

Any tips on what I should try?

 

I've disabled/re-enabled PXE

I've redistributed boot images.

I've unchecked "enable command support" and rechecked as suggested here.

I've created new task sequences and deployed them

 

Any other logs that would help me? Thanks for any advice.

[mkeehn]

This morning I've tried uninstalling the Management Point, running ccmsetup.exe /uninstall and reinstalling the Management Point.

 

Upon reboot, I am seeing this in the SMSPXE.log

RequestMPKeyInformation: Send() failed.	
Failed to get information for MP: http://servername.domain.lan. 80004005.
reply has no message header marker
PXE::MP_LookupDevice failed; 0x80004005
PXE Provider failed to initialize MP connection. 
Unspecified error (Error: 80004005; Source: Windows)
Prioritizing local MP http://servername.domain.lan.
RequestMPKeyInformation: Send() failed.
Failed to get information for MP: http://servername.domain.lan. 80004005.
reply has no message header marker
Failed to send status message (80004005)
Failed to send the status message
PXE::MP_ReportStatus failed; 0x80004005
PXE::CPolicyProvider::InitializeMPConnection failed; 0x80004005

After which it does find the images and says that the PXE provider is loaded. Still having the same issues, though.

[mkeehn]

I've now gone through this process detailed below and redistributed my boot images, no change.

 

• untick the enable PXE checkbox on the distribution point. Answer yes that you want to remove the Windows Deployment service.
• remove your boot images from your distribution point
• After 5 minutes. Delete %windir%\temp
• check with server manager if you can add/remove roles on the server. If WDS is done uninstalling there is a pending boot.Reboot!!!
• check if the remoteinstall folder is located on your system. If it is delete it.
• reboot
• Add the PXE point again by checking the box on the distribution point properties. Check the distrmgr.log and see if the remoteinstall folder reappers..
• Send the boot images to the distribution points again.

[Garistotle]

Same exact output from SMSPXE.log. Did you ever manage to find a solution?

 

I'm configuring a new 1606 site and haven't yet successfully PXE-booted my build and capture task sequence. I disabled and re-enabled PXE on my DP, but I really don't want to go through all the steps you had to go through only to find that it didn't work. From looking at the other posts about this issue, it looks like that might fix the issue when the site has been upgraded from R2 to CB. If I find something that works for me, I'll post here.

 

 

This morning I've tried uninstalling the Management Point, running ccmsetup.exe /uninstall and reinstalling the Management Point.

 

Upon reboot, I am seeing this in the SMSPXE.log

RequestMPKeyInformation: Send() failed.	
Failed to get information for MP: http://servername.domain.lan. 80004005.
reply has no message header marker
PXE::MP_LookupDevice failed; 0x80004005
PXE Provider failed to initialize MP connection. 
Unspecified error (Error: 80004005; Source: Windows)
Prioritizing local MP http://servername.domain.lan.
RequestMPKeyInformation: Send() failed.
Failed to get information for MP: http://servername.domain.lan. 80004005.
reply has no message header marker
Failed to send status message (80004005)
Failed to send the status message
PXE::MP_ReportStatus failed; 0x80004005
PXE::CPolicyProvider::InitializeMPConnection failed; 0x80004005

After which it does find the images and says that the PXE provider is loaded. Still having the same issues, though.

[anyweb]

have you tried re-deploying the task sequence ? does it make any difference to the end result ?

[Garistotle]

Hi, thanks.

 

I tried re-deploying the task sequence this morning, no change. I just updated the boot image on the DP and again, no change. The boot error on both my Hyper-V client and a Dell laptop is the same:

 

PXE-E53: No boot filename received

 

On the VM it shows the same error, then shows "Boot failure. Reboot and Select proper Boot device or Insert Boot Media in selected Boot device_

 

SMSPXE.log shows the above, but continues (error-free) with...

 

PXE::CBootImageInfo:::CBootImageInfo: key=

Adding [site]00004.4

Adding [site]00005.5

Adding [site]00019.3

Adding [site]0001A.3

Found new image UCO00004 (goes on error-free) ... To my understanding, this would indicate that the task sequence and boot images are where they're supposed to be.

 

mpcontrol.log is largely error-free with the exception of...

CMPControlManager::PublishDNS: DnsReplaceRecordsSet() failed with status 9017.

 

This is a new site that I'm configuring in preparation to migrate clients to when it's all ready to go. I thought I was getting that mpcontrol error from having added the 2 Application Catalog roles, but not having a DNS redirect yet. This seems unrelated to the problem I'm having, but maybe not? Are there any logs that will show me some more detail about what's happening when the client is requesting the boot image? Any other logs I should look at? Thanks for your help! And, all that you do to help us learn config mgr!

 

 

have you tried re-deploying the task sequence ? does it make any difference to the end result ?

[sandytsang]

Failed to get information from MP, can you check if the MP list can be opened? http://your_sccm_server/sms_mp/.sms_aut?mplist

[boza]

:) :) :) RESOLVED!!!

 

https://support.microsoft.com/pt-pt/kb/2796086

 

steps:

 

1. setting the following registry value to True

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\CcmEval\NotifyOnly

 

2.REMOVE ROLE MANAGMENT POINT

3.REBOOT

4. INSTALL ROLE mp

 

and everything work again...

 

no 500 error,

pxe ok

client status ok, in console!

[Maestro]

Hello everyone.

Got the same error after migrating to 1606 from 2012 SP2. Digging the logs, found that SCCM is getting problems with WDS. WDS needs to be restarted before activating, SCCM isn't ready for this and tries to do everything, not paying attention that service is missing.

What did I do.

1. Unchecked PXE in SCCM console.

2. Uninstalled WDS. Rebooted.

3. Deleted (just in case) %windir%\Temp and RemoteInstall folders.

4. Manually installed WDS. Rebooted.

5. Checked PXE option, waited for procedure to complete (no errors in logs).

6. Redistributed boot images.

7. Redistributed OS images.

8. Deleted and re-created TS.

 

Worked like a charm.

Maybe this will help to somebody.