Thursday, 28 February 2013

ConfigMgr 2012 / SCCM 2012 Task Sequence fails with BCD error

Issue: OSD Task Sequence fails to be deployed via network booting. Issue occurs on all devices (different makes and models)

This error appears on screen

 Your PC needs to be repaired

File: \Boot\BCD
Status : 0xc0000098
Info : The Windows Boot configuration data file does not contain a valid OS Entry.

 OR


I resolved this by disabling and then re-enabling PXE support on the Distribution Point



Go to the Properties of the DP and uncheck the box "Enable PXE support for clients"

Wait for a short time while Windows Deployment Services uninstalls

Reboot the DP

Re-enable PXE support and wait while WDS re-installs

WDS usually requires a reboot so you should reboot again



Verify that the RemoteInstall folders have been populated

This is a safe process and has no effect on Config Mgr system files or packages

Posted by at
Labels: , ,

51 comments:

  1. Unknown7 June 2013 at 17:20

    Hey Gerry this didnt work for me. any further advise

    ReplyDelete
  2. Gerry Hampson8 June 2013 at 10:43

    Have you an isolated or a general issue? Try redistributing your boot images.

    ReplyDelete
    Replies
    1. Unknown3 February 2016 at 09:27

      Thank you! All i need was to "Update distribution points" for my x86 boot image...

      Delete
    2. Anonymous19 April 2017 at 22:09

      This worked for us after P to V'ing a DP. We also redistributed the BootImage. Thanks!!!

      Delete
    3. Tim Lee7 January 2019 at 05:53

      Much appreciated for the information. I encountered the same issue and the problem was solved by following those steps. Thank you.

      Delete
  3. Anonymous12 July 2013 at 10:48

    Had the same BCD problem. It appears to have been caused by the "Enable unknown computer support" option on the DP being unchecked. You also need to deploy at least one OSD Task Sequence to the "All Unknown Computers" device collection for PXE to work.

    ReplyDelete
  4. Anonymous9 August 2013 at 07:42

    THANK YOU!!!!!!!!!!!!!!!!!!!!!! That worked! So many hours wasted...

    ReplyDelete
  5. Gerry Hampson9 August 2013 at 13:17

    You're very welcome. Thanks for letting me know.

    ReplyDelete
  6. Unknown3 October 2013 at 20:31

    For anyone else who stumbles on this, another possible issue where you will see this is if you are in HTTPS mode and the DP is configured with a self-signed cert. You must use a PKI cert for the DP in order for PXE to work.

    ReplyDelete
    Replies
    1. Anonymous7 February 2018 at 03:28

      Encountered this in SCCM 1710. Been messing around with boot images, task sequences and DHCP options in order to find it. Requested a 'ConfigMgr Client Distribution Point Certificate', exported it with a password, imported it in SCCM, worked like a charm! Thanks!

      Delete
    2. Justin9 April 2018 at 21:38

      Where did you go to request the DP cert?

      Delete
    3. Anonymous16 August 2018 at 13:02

      @Anonymous, thanks, this solved my issue aswell.

      Delete
  7. Gerry Hampson3 October 2013 at 21:00

    Thanks Chris

    ReplyDelete
  8. Pablo Mendoza13 November 2013 at 18:01

    Hi Gerry, I've done the steps that you mentioned but the issue is till there. Could you tell me what else can I do to resolve this issue?

    ReplyDelete
  9. McRae24 January 2014 at 10:29

    For others: this error might pop up also in case you've done a wrong computer association - wrong MAC! I know the error doesn't sound like this, but checking de sms_pxe log will lead you to "device not found in database"... just be 100% sure you exclude that first!
    This was my case.

    ReplyDelete
    Replies
    1. Anonymous26 March 2015 at 19:50

      Thanks buddy, you just saved my bacon. This was my problem. I've had plenty of incorrect MACs loaded but never seen this error before. Good lesson... always check the SMSPXE log!

      Delete
    2. Unknown21 November 2017 at 09:59

      Thanks this was my problem. Lesson learned....

      Delete
  10. Anonymous18 March 2014 at 17:00

    Worked for me. Thanks

    ReplyDelete
  11. Jurgen De Vlieger3 April 2014 at 10:41

    Thanks Gerry, you saved my day (again!) :)

    ReplyDelete
  12. Gerry Hampson3 April 2014 at 14:56

    You're welcome Jurgen

    ReplyDelete
  13. Anonymous3 July 2014 at 01:58

    Is WDS supposed to uninstall itself after disabling the PXE boot option? Anyway it didn't work for me.

    ReplyDelete
    Replies
    1. Gerry Hampson3 July 2014 at 08:23

      It's supposed to. However I've often seen it not happen that way. In that case you must uninstall manually.

      Delete
  14. Unknown1 August 2014 at 01:06

    I've tried everything and I'm still getting this same error. It was working perfectly fine until I upgraded from SCCM 2012 to 2012 R2. I've installed the hotfix that is supposed to fix the PXE issue, but it didn't work. I don't know what else to try.

    ReplyDelete
  15. Chad Simmons14 October 2014 at 16:48

    Thanks for the write-up, Gerry. It helped me resolve the same errors.

    ReplyDelete
  16. Anonymous18 December 2014 at 13:36

    Thanks a lot Gerry. That worked! - Sreejith Menon

    ReplyDelete
  17. Anonymous6 March 2015 at 16:03

    This worked for me. WDS failed to start after disk space was added to the server and then restarted. Uninstalling WDS and adding it directly on the server caused the error above. Following the directions in this blog fixed the issue by letting SCCM install the role. Thanks Gerry!

    ReplyDelete
  18. Anonymous21 August 2015 at 19:36

    It worked, thanks ;-)

    ReplyDelete
  19. Anonymous3 October 2015 at 20:02

    What an idiotic system, where one has to do uninstall to fix something as small of wrong/missing etc .bcd file. Pathetic!

    ReplyDelete
  20. Anonymous10 November 2015 at 01:46

    Thanks buddy...

    ReplyDelete
  21. Unknown29 November 2015 at 20:05

    Worked for me after my upgrade to SP1. Thanks!

    ReplyDelete
  22. Jeff30 December 2015 at 23:16

    Hi Gerry,

    I've never said thanks for all the SCCM help I have gotten from your site in the past, so thanks. But this didn't resolve my issue. I have the following setup:
    SCCM 2012 R2 SP1 CU2, I do have WDS 8.1 and 10 installed. I an getting a File:\boot\bcd Error Code: 0xc000000f. The last two lines in my SMSPXE.log file after trying to do a boot is:
    File D:\RemoteInstall\SMSTemp\2015.12.30.15.49.53.04.{8B3C7110-947C-47E1-9FEC-28711A02D44A}.boot.bcd deleted.
    File D:\RemoteInstall\SMSTemp\2015.12.30.15.49.53.04.{8B3C7110-947C-47E1-9FEC-28711A02D44A}.boot.bcd.log deleted.

    I have DHCP (installed on another Server) set to:
    OptionId 66 -Value 'SCCM'
    OptionId 67 -Value '\smsboot\x86\wdsnbp.com'

    I do get an IP address and everything and do the F12 to PXE boot and then get the Blue screen with the above error.

    Any Ideas would be a great help. Thanks.

    ReplyDelete
    Replies
    1. Gerry Hampson11 January 2016 at 11:27

      No worries Jeff. I don't quite understand what you mean by WDS 8.1 and 10. Are you referring to ADK 8.1 and 10?

      Delete
  23. Unknown8 February 2016 at 13:13

    Hi Gerry,

    I think this issue is due to upgrades that we do when we on the ADK and delete old images and add new ones with different names (file boot.wim now)... Your solution is the best approach as far I'm concern. After the new settings are written again in the DP, you can check the directories from the RemoteInstall that the new boot image is present.

    ReplyDelete
  24. Steven J.11 April 2016 at 16:11

    Gerry,

    this really helped me out I really appreciate you providing this information to us

    ReplyDelete
  25. DBassett20 July 2016 at 09:00

    Thanks Gerry like Steven I appreciate you publishing your expertise, got me back up and running.

    ReplyDelete
  26. Unknown26 November 2017 at 10:04

    All i did was that i changed the computer name. It worked like Vow..
    The computer was in workgroup and i wanted to re-image it and add to domain.

    ReplyDelete
  27. Ermin19 December 2017 at 20:24

    https://timstidstonit.wordpress.com/2016/03/02/sccm-2012-r2-bcd-pxe-boot-fix/

    ReplyDelete
  28. Anonymous21 December 2017 at 12:16

    Hi, I followed the suggestions on this thread, but unfortunately still no fix. Everytime when i try to boot in to PXE. This is what comes up on the Trace tool. Any ideas would be greatly appreciated.

    RequestMPKeyInformation: Send() failed. SMSPXE 21/12/2017 12:06:34 6908 (0x1AFC)
    Failed to get information for MP: http://server. 80004005. SMSPXE 21/12/2017 12:06:34 6908 (0x1AFC)
    PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 21/12/2017 12:06:34 6908 (0x1AFC)
    PXE::MP_LookupDevice failed; 0x80004005 SMSPXE 21/12/2017 12:06:34 6908 (0x1AFC)
    RequestMPKeyInformation: Send() failed. SMSPXE 21/12/2017 12:06:35 6908 (0x1AFC)
    Failed to get information for MP: http://server. 80004005. SMSPXE 21/12/2017 12:06:35 6908 (0x1AFC)
    PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 21/12/2017 12:06:35 6908 (0x1AFC)
    PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 21/12/2017 12:06:35 6908 (0x1AFC)
    PXE Provider failed to process message.
    Unspecified error (Error: 80004005; Source: Windows) SMSPXE 21/12/2017 12:06:35 6908 (0x1AFC)
    D4:3D:7E:BE:C4:D5, 6E1FA92C-FEAA-11E2-A9E4-F0675B7C3100: Not serviced. SMSPXE 21/12/2017 12:06:35 6908 (0x1AFC)
    RequestMPKeyInformation: Send() failed. SMSPXE 21/12/2017 12:06:35 6908 (0x1AFC)
    Failed to get information for MP: http://Server. 80004005. SMSPXE 21/12/2017 12:06:35 6908 (0x1AFC)
    PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 21/12/2017 12:06:35 6908 (0x1AFC)
    PXE::MP_LookupDevice failed; 0x80004005 SMSPXE 21/12/2017 12:06:35 6908 (0x1AFC)
    RequestMPKeyInformation: Send() failed. SMSPXE 21/12/2017 12:06:35 6908 (0x1AFC)
    Failed to get information for MP: http://server. 80004005. SMSPXE 21/12/2017 12:06:35 6908 (0x1AFC)
    PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 21/12/2017 12:06:35 6908 (0x1AFC)
    PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 21/12/2017 12:06:35 6908 (0x1AFC)
    PXE Provider failed to process message.
    Unspecified error (Error: 80004005; Source: Windows) SMSPXE 21/12/2017 12:06:35 6908 (0x1AFC)
    D4:3D:7E:BE:C4:D5, 6E1FA92C-FEAA-11E2-A9E4-F0675B7C3100: Not serviced. SMSPXE 21/12/2017 12:06:35 6908 (0x1AFC)
    RequestMPKeyInformation: Send() failed. SMSPXE 21/12/2017 12:06:35 6908 (0x1AFC)
    Failed to get information for MP: http://server. 80004005. SMSPXE 21/12/2017 12:06:35 6908 (0x1AFC)
    PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 21/12/2017 12:06:35 6908 (0x1AFC)
    PXE::MP_LookupDevice failed; 0x80004005 SMSPXE 21/12/2017 12:06:35 6908 (0x1AFC)
    RequestMPKeyInformation: Send() failed. SMSPXE 21/12/2017 12:06:35 6908 (0x1AFC)
    Failed to get information for MP: http://server. 80004005. SMSPXE 21/12/2017 12:06:35 6908 (0x1AFC)
    PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 21/12/2017 12:06:35 6908 (0x1AFC)
    PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 21/12/2017 12:06:35 6908 (0x1AFC)
    PXE Provider failed to process message.
    Unspecified error (Error: 80004005; Source: Windows) SMSPXE 21/12/2017 12:06:35 6908 (0x1AFC)
    A4:3D:7G:BE:E4:D5, 6E1FB95C-FEAA-11E2-A9D4-F0675F4C3100: Not serviced. SMSPXE 21/12/2017 12:06:35 6908 (0x1AFC)

    Thank you,
    Atheek

    ReplyDelete
  29. Jamie7 February 2018 at 11:06

    Just used this fix on a new deployment of SCCM which was upgraded to current branch. Still seems to be a working fix. Many thanks.

    ReplyDelete
  30. Ivo Hofstede10 September 2018 at 14:02

    In addition to you're problem i would like to mention the following.

    DHCP 67 option should redirect to smsboot\x64\wdsmgfw.efi instead of boot\x64\wdsmgfw.efi this is a stupid typo wich makes me troubleshoot UEFI boot for 4 hours.

    There are many guides out there redirecting you to the boot folder instead of the SMS.

    ReplyDelete
    Replies
    1. Gerry Hampson10 September 2018 at 22:30

      I don't recommend DHCP options at all for this service Ivo. In my opinion IP Helpers are the only way to do this properly.

      Delete
  31. Unknown27 September 2018 at 20:20

    I had the same problem in my environment.
    I restarted the server and the problem was gone. I couldn't to identify the root cause.

    Best Regards

    ReplyDelete
  32. Anonymous11 March 2019 at 17:42

    Funcionó, muchas gracias!

    ReplyDelete
  33. Unknown25 April 2019 at 16:20

    Can anyone help please...

    Getting this error after disabling one of our DHCP servers and can't for the life of me figure out how to get PXE boot working again.

    I have changed the DHCP Scope options to reflect the new DHCP server (option 44) and have both old and new servers configured as helper-addresses on all switches but when I unauthorise the old DHCP server PXE boot fails with the 'The Windows Boot configuration data file from the PXE server does not contain a valid OS Entry' error.

    It's nothing to do with SCCM as when I turn my old DHCP server back on, PXE boot succeeds (even so, I've tried the steps above but to no avail). New DHCP server has been running perfectly for ages - it's just I'm now at the point of decommissioning the old one.

    Thanks in advance.

    ReplyDelete
  34. Brian27 August 2019 at 14:52

    The drive where "RemoteInstall" folder is located was full. I deleted some file someone copied there and it started working.

    ReplyDelete

Subscribe to: Post Comments (Atom)