Can't PXE boot a client after upgrade to 1511 and ADK 10

[couillardk]

Here are the smspxe.log results when I F12 a client, and it replies PXE53 - No boot file name available.

The MAC not serviced is the client I am attempting to boot.

 

Prioritizing local MP http://CSD10.csd.local. SMSPXE 6/23/2016 8:33:10 AM 3404 (0x0D4C)

RequestMPKeyInformation: Send() failed. SMSPXE 6/23/2016 8:33:10 AM 3404 (0x0D4C)

Failed to get information for MP: http://CSD10.csd.local. 80004005. SMSPXE 6/23/2016 8:33:10 AM 3404 (0x0D4C)

reply has no message header marker SMSPXE 6/23/2016 8:33:10 AM 3404 (0x0D4C)

PXE::MP_LookupDevice failed; 0x80004005 SMSPXE 6/23/2016 8:33:10 AM 3404 (0x0D4C)

Prioritizing local MP http://CSD10.csd.local. SMSPXE 6/23/2016 8:33:10 AM 3404 (0x0D4C)

RequestMPKeyInformation: Send() failed. SMSPXE 6/23/2016 8:33:10 AM 3404 (0x0D4C)

Failed to get information for MP: http://CSD10.csd.local. 80004005. SMSPXE 6/23/2016 8:33:10 AM 3404 (0x0D4C)

reply has no message header marker SMSPXE 6/23/2016 8:33:10 AM 3404 (0x0D4C)

Failed to send status message (80004005) SMSPXE 6/23/2016 8:33:10 AM 3404 (0x0D4C)

Failed to send the status message SMSPXE 6/23/2016 8:33:10 AM 3404 (0x0D4C)

PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 6/23/2016 8:33:10 AM 3404 (0x0D4C)

PXE Provider failed to process message.

Unspecified error (Error: 80004005; Source: Windows) SMSPXE 6/23/2016 8:33:10 AM 3404 (0x0D4C)

94:57:A5:01:8C:40, B3B369FF-F4C2-11E4-A609-7070990000FF: Not serviced. SMSPXE 6/23/2016 8:33:10 AM 3404 (0x0D4C)

[anyweb]

Prioritizing local MP http://CSD10.csd.local.  SMSPXE 6/23/2016 8:33:10 AM 3404 (0x0D4C)

RequestMPKeyInformation: Send() failed. SMSPXE 6/23/2016 8:33:10 AM 3404 (0x0D4C)

still having issues contacting the Management point, take a look at this post to see does it help you resolve your problem

 

https://www.windows-noob.com/forums/topic/7281-management-point-pxe-boot-error-80004005-after-sp1-upgrade/

[couillardk]

Yes that is the root of the issues for sure. My EP defs are not getting to clients anymore either. This is a great article and I did all these steps yesterday. It made a brand new remoteinstall folder but did not fix anything.

 

• untick the enable PXE checkbox on the distribution point. Answer yes that you want to remove the Windows Deployment service.
• remove boot images from your distribution point
• After 5 minutes delete %windir%\temp
• check with server manager. If WDS is done uninstalling there is a reboot pending. Reboot.
• check if the remoteinstall folder is located on your system. If it is delete it. If it fails to delete due to permission issues with the SMSTempBootFiles path, delete all folders except that one and then rename the remoteinstall folder something else.
• 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 reappears..
• Replicate the boot image to the DP again.

[couillardk]

Still get this error when f12 a client PXE53: No Boot file name available. Here are the latest steps I have done, without success.

• Uncheck PXE and Multicast on the distribution point. Answer yes that you want to remove the Windows Deployment service.
  
• remove all boot images from your distribution point
  
• Wait until WDS is gone, then rename %windir%\temp to ­_old
  
• If WDS is done uninstalling there is a reboot pending. Reboot.
  
• Rename RemoteInstall folder to _old
  

• This time I am going to delete all boot images from OS/Boot Images. I am trying to make the RemoteInstall folder recreate without any boot images. Maybe this is why the “Invalid file version found” errors in smspxe.log. Example: Failed to retrieve the version of file 'C:\RemoteInstall\SMSTempBootFiles\C1000063\WINDOWS\Boot\PXE\pxeboot.com'. Error code: 0x80004005
  

• reboot
  
• Select PXE and Multicast on the distribution point. A new RemoteInstall folder should be created and WDS. Look at the distrmgr.log and smspxe.log. May have to restart WDS service.
  
• Create new boot images
  
• Distribute the boot images to the DP again.
  

• This all sounded good but did not work. Next, I am going to delete the boot images, uninstall ADK10 and install ADK 10 RTM (older version), then recreate the boot images. – No this did not work either.
  
• Next? I think this is the root of the problem:
  

Mpcontrol.log:

Initialization still in progress. SMS_MP_CONTROL_MANAGER 6/24/2016 3:24:19 PM 3784 (0x0EC8)

Beginning periodic tasks. SMS_MP_CONTROL_MANAGER 6/24/2016 3:24:49 PM 3784 (0x0EC8)

RetryWINSOperationIfNecessary: No need to retry. Returning. SMS_MP_CONTROL_MANAGER 6/24/2016 3:24:49 PM 3784 (0x0EC8)

RetryDNSPublishingIfNecessary: No need to retry. Returning. SMS_MP_CONTROL_MANAGER 6/24/2016 3:24:49 PM 3784 (0x0EC8)

Completed periodic tasks. SMS_MP_CONTROL_MANAGER 6/24/2016 3:24:49 PM 3784 (0x0EC8)

SSL is not enabled. SMS_MP_CONTROL_MANAGER 6/24/2016 3:24:49 PM 3784 (0x0EC8)

Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error SMS_MP_CONTROL_MANAGER 6/24/2016 3:24:49 PM 3784 (0x0EC8)

Sent summary record of SMS Management Point on ["Display=\\CSD10.csd.local\"]MSWNET:["SMS_SITE=C10"]\\CSD10.csd.local\ to \\CSD10.csd.local\SMS_C10\inboxes\sitestat.box\b6n3dr1i.SUM, Availability 1, 303725564 KB total disk space , 23328884 KB free disk space, installation state 0. SMS_MP_CONTROL_MANAGER 6/24/2016 3:24:49 PM 3784 (0x0EC8)

Successfully performed Management Point availability check against local computer. SMS_MP_CONTROL_MANAGER 6/24/2016 3:24:49 PM 3784 (0x0EC8)

Initialization unsuccessfully completed within the allowed interval. SMS_MP_CONTROL_MANAGER 6/24/2016 3:24:49 PM 3784 (0x0EC8)

[couillardk]

Microsoft professional support just solved this issue. They removed the MP, rebooted, ran a program called "ccmclean.exe" and then installed the MP. No more errors in the MPcontrol.log and PXE boot works!