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



37 comments:

  1. Hey Gerry this didnt work for me. any further advise

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

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

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

      Delete
  3. 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. THANK YOU!!!!!!!!!!!!!!!!!!!!!! That worked! So many hours wasted...

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

    ReplyDelete
  6. 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
  7. 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
  8. 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. 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
  9. Worked for me. Thanks

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

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

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

      Delete
  12. 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
  13. Thanks for the write-up, Gerry. It helped me resolve the same errors.

    ReplyDelete
  14. Thanks a lot Gerry. That worked! - Sreejith Menon

    ReplyDelete
  15. 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
  16. It worked, thanks ;-)

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

    ReplyDelete
  18. Thanks buddy...

    ReplyDelete
  19. Worked for me after my upgrade to SP1. Thanks!

    ReplyDelete
  20. 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. 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
  21. 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
  22. Gerry,

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

    ReplyDelete
    Replies
    1. You're welcome Steven. Glad to help.

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

    ReplyDelete