Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About couillardk

  • Rank
  1. 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!
  2. 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
  3. 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
  4. 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 34
  5. both x86 and x64 winpe boot images contain two net drivers (an Intel and a Realtek), distributed and enabled PXE. Only one is attached to the task sequence. In this case I have a win10 OS, so I attached the x64 boot image.
  6. I removed, and reinstalled the MP. I also added DHCP scope options even though the client and server are on the same subnet. The good news: a. the MP is healthy online again b. the smspxe.log is populating again c. the client gets an IP and downloads the wdsnbp, then errors. The bad news: a. errors in the smspxe.log (see below) b. the client error: The BCD from the PXE server does not contain a valid operating system. Ensure the server has boot images installed for this architecture. File:\\Tmp x86x64(<numbers>).bcd Error code: 0x0000098 Severity Type Site code Date / Time S
  7. Also, sorry typo in my first post. I applied this patch to both boot images https://support.microsoft.com/en-in/kb/3143760
  8. Steps I tried with No success: Disable PXE support on all (old and new) boot images Disable PXE support on DP Remove WDS role Reboot server Enable PXE support on two new boot images (x64 and x86 winpe ADK Win10) Enable PXE support on DP Wait for WDS role to be installed Redistribute two new boot images to DP Verify RemoteInstall folder has been populated F12 a client – no, same error PXE-E53 No boot file name available
  9. I just fixed the MP issue (ERROR SMS_MP_CONTROL_MANAGER) by changing the Management Point Connection Account from use the computer account to domain service account. Still unable to PXE boot. On a client I am trying to PXE boot, F4 to get a command prompt. ipconfig /all results: Host Name: (blank) Primary Dns Suffix: (blank) Node type: Hybrid IP Routing Enabled: No WINS Proxy Enabled: No
  10. I just found this in Monitoring Componet Status: Critical SMS_MP_CONTROL_MANAGER ERROR SMS_MP_CONTROL_MANAGER MP Control Manager detected management point is not responding to HTTP requests. The HTTP status code and text is 500, Internal Server Error. Possible cause: Management point encountered an error when connecting to SQL Server. Solution: Verify that the SQL Server is properly configured to allow Management Point access. Verify that management point computer account or the Management Point Database Connection Account is a member of Management Point Role (msdbrole_MP) in the SQL Ser
  11. After upgrading to 1511 and ADK win10 and running the patch kb314370, F12 a client and get "No boot file name available". Cannot get F8 to open a cmd prompt for support logs either, yes it is enabled. Both the new (x86 and x64 from ADK) boot images are distributed and have WinPE 10 drivers. PXE is enable and advertised by the DT. SMSPXE.log on the server is not even being populated. Previous to this upgrade, we could PXE boot, now we can't. Thank you for any help! KACouillard
  12. We have the fix! Thanks to this site. https://social.technet.microsoft.com/Forums/en-US/3b21e55a-65e5-4193-b82b-6634a0e3af42/capturing-an-image-from-newly-built-reference-computer-fails-with-error-code-0x00004005-windows-10?forum=configmanagerosd The failure each time is in the SysPrep. SysPrep is choking on the Universal Apps. See the SysPrep setupact.log. The fix: Run gpedit.msc for local Group Policy and turn off the Customer Experience “Computer Configuration –> Administrative Templates –> Windows Components –> Cloud Content” called “Turn off Microsoft consumer
  13. Hello, we have the exact same issue! SCCM v5.00.8239.1000, Capture media works on Windows 7 but not Windows 10. Same error during sysprep code 0x00004005. Does anyone know what is causing this? thank you! KAC
  14. This was resolved by moving the tasks, Apply Windows Settings and Apply Network Settings above the task Setup Windows and Configuration and then came the Install Apps task.
  • Create New...