PXE Boot Error "0xc000000f" while Installing SCCM 2012 Task-Sequence

PXE Boot Error "0xc000000f" while Installing SCCM 2012 Task-Sequence

Error-Code: 0xc000000f
Error-Description: An error occurred while attempting to read the boot configuration data.
File: \Boot\BCD



Resolution steps:
  1. Check if all components like Bootimages, OS-Images, Task-Sequences and Announcements are published to all distribution-points
  2. Check if there is a processing-failure during the distribution
  3. Check permissions on file-System (insert "system"-account and SCCM PXE-Point FQDN with Full-Acces (share and security permissions))
  4. Add the network-access acount with Domain-Administration Status
  5. Update the Network Driver to the Bootimages
  6. Add the client computer to SCCM "Computers"-Section (Import with MAC-Address) and create Task-Sequence Announcement to this Selection
  7. Try to clear Client-PCs PXE-Announcements
  8. Check if there are both boot Images deployed (x64 and x86) and distributed to DPs (If you have to re-create boot files check out: http://social.technet.microsoft.com/wiki/contents/articles/16233.how-to-create-or-re-create-a-default-sccm-boot-image-windows-pe-4-0-for-sccm-2012-sp1-en-us.aspx)
Leave a Comment
  • Please add 6 and 5 and type the answer here:
  • Post
Wiki - Revision Comment List(Revision Comment)
Sort by: Published Date | Most Recent | Most Useful
Comments
Page 1 of 1 (4 items)
Wikis - Comment List
Sort by: Published Date | Most Recent | Most Useful
Posting comments is temporarily disabled until 10:00am PST on Saturday, December 14th. Thank you for your patience.
Comments
  • What fixed it for me:

    I only had x64 boot image distributed, which I wanted to use, but it only worked after I also distributed x86.

  • Hi Aurimas,

    it is only necessary if you want to distibute Images on x86 Hardware. But if it fixed your issue i will integrate your solution into the article. Thanks for your comment.

  • Hi Aurimas,

    it is only necessary if you want to publish Images on x86 hardware but you have to distribute both boot images to all of your sccm servers. Thanks for your suggestion. I will add your solution as Step 8 to my article.

  • Hi Aurimas,

    it is only necessary if you want to publish Images on x86 hardware but you have to distribute both boot images to all of your sccm servers. Thanks for your suggestion. I will add your solution as Step 8 to my article.

  • Hi Aurimas,

    it is only necessary if you want to publish Images on x86 hardware but you have to distribute both boot images to all of your sccm servers. Thanks for your suggestion. I will add your solution as Step 8 to my article.

  • Jochen.Reinecke edited Revision 2. Comment: additional tipps added

  • Carsten Siemens edited Revision 3. Comment: typo

  • Carsten Siemens edited Revision 6. Comment: fixed typo

  • Fernando Lugão Veltem edited Revision 7. Comment: remove en-us from title

  • This error could also result in the following message being written in SMSPXE.log: <![LOG]: device is not in the database. + <![LOG]: Not serviced.]LOG]!> I have seen this twice so far. The fix was just to delete the computer from SCCM and import it again.

  • In my case, it was very important to use boot\x86\wdsnbp.com, nothing else.

Page 1 of 1 (11 items)