none
SCCM 2012 fails at PXE boot: The Windows Boot Configuration Data file does not contain a valid OS entry

    Question

  • Hi there,

    I have the fantastic opportunity to play with SCCM 2012, I managed to deploy OS without any problems, create bootable media and capture images and then deploy those images and everything worked perfectly fine until this morning. I was testing an image that I captured the previous day, I deployed it on two machines and I was pleased with the result. Later on I was messing with multicasting as this will need to be implemented within our system. I made sure it is enabled on the distribution point (which it was), then i changed the settings on the image. Then I installed Admin Studio, because it was part of my task. Also I messed a little bit with the network discovery as it was not discovering computers which are not part of the domain(still no luck with that but this is another topic). After making the changes to the multicasting I thought alright lets see if it works. I used the same task sequence i used to deploy the captured image(which worked before!!!) and when i restarted the computers it would give me an error, something like TFTP Server: Access violation. I knew what the problem was as i had similar issue before, so i checked the DHCP and saw that "Magically" the path to the boot image had an additional "\" in the beginning. Deleted that "\", restarted the computers again. Now it would get an ip address as usual, then it would download the wdsnbp and then it would say something about Architecture: x64 (the machine is x86). Then it gave me the F12 option to boot, once pressed it would say again something about Architecture: 64, and then I will get a blue screen saying that  "The Windows Boot Configuration Data file does not contain a valid OS entry" and give me an error code of: 0x0000098. I read some topics about it and people were suggesting that the boot images are not distributed on the DP or the PXE is not enabled, which is weird as it used to work before, so I deleted the boot images from the DP and redistributed them to the DP making sure that PXE is enabled everywhere but still no luck. From what I understand is that it cannot locate boot images on the DP and I can confirm they are there. I restarted both the dc and the SCCM server but still no joy.

    Any suggestions would be much appreciated.

    On another topic, we are planning to change the domain (have entirely different domain controller). What changes have to be done in SCCM in order to work alongside with the new domain. Is it just a case of creating again a new container, giving permissions, setting up bounderies, creating new security accounts?

    Thanks,

    LP

    Tuesday, July 09, 2013 1:17 PM

Answers

All replies

  • Are you going to "change" the domain or add another one? You can't move a configmgr server from one domain to another. You can however support clients across domains.


    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    • Marked as answer by lpopov Tuesday, July 09, 2013 3:00 PM
    Tuesday, July 09, 2013 1:29 PM
    • Marked as answer by lpopov Tuesday, July 09, 2013 3:00 PM
    Tuesday, July 09, 2013 1:31 PM
  • Are you going to "change" the domain or add another one? You can't move a configmgr server from one domain to another. You can however support clients across domains.


    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    We will entirely change the domain. So you suggest just reinstalling SCCM ? It wouldn't be a problem as we are still in testing phase.
    Tuesday, July 09, 2013 1:33 PM
  • Re-install for sure


    Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson

    • Marked as answer by lpopov Tuesday, July 09, 2013 3:00 PM
    Tuesday, July 09, 2013 1:38 PM
  • Thank you very much for your quick response guys. All the information was very helpful.
    Tuesday, July 09, 2013 3:01 PM
  • Yep...as Gerry said, installed a fresh CM in the new domain and let the clients join that CM as they are migrated over.


    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    Tuesday, July 09, 2013 8:50 PM
  • How about the licensing, can i use the same license ?
    Wednesday, July 10, 2013 1:08 PM
  • Had this problem before and solved it as shown here


    This didn't fix the problem btw. I noticed thatt it is trying to boot from TFTP Download: boot\x86\wdsnbp.com instead of SMSboot\x86\wdsnbp.com (eventho this is set in the dhcp). I uninstalled WDS and installed it again but still no joy. Any other suggestions?
    Wednesday, July 10, 2013 1:49 PM
  • Try using SMSboot\x64\wdsnbp.com as your DHCP option (are you using UEFI?). I'm assuming both boot images have been distributed to DP

    As for licensing, use the same key - as the first environment will be decommissioned



    Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson


    Wednesday, July 10, 2013 2:07 PM
  • I'd suggest not using any DHCP options. they are unreliable. Use IP Helpers.


    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    Wednesday, July 10, 2013 2:14 PM
  • Try using SMSboot\x64\wdsnbp.com as your DHCP option (are you using UEFI?). I'm assuming both boot images have been distributed to DP

    As for licensing, use the same key - as the first environment will be decommissioned


    Thanks again for the quick response, at the moment we are installing the new domain so soon i will have to uninstall sccm 2012, so I believe i ll leave this problem behind. Is there a setting within WDS or SCCM 2012 where you specify the tftp server location ? Because from what i understand SCCM 2012 sits on top of WDS, and at the moment it is trying to boot from WDS and not from SCCM 2012 SMSBoot location(if that makes any sense?).
    • Edited by lpopov Wednesday, July 10, 2013 2:20 PM Awesome
    Wednesday, July 10, 2013 2:18 PM
  • No, the server is located as follows:

    1. automatically if on the same subnet

    2. via IP Helper (as John said - recommended)

    3. DHCP scope option



    Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson

    Wednesday, July 10, 2013 2:20 PM
  • Hello again guys,

    We got the new domain up and running, I uninstalled SCCM 2012, done everything as it should be and we still have the same problem as described above. When we boot it grabs an IP address then it points to the correct TFTP server, but then I noticed that it tries to boot from a different file than what we specified, it tries to boot from:

    Boot\x86\wdsnbp.com instead of SMSBoot\x86\wdsnbp.com

    and again it would say something about x64 architecture.

    I have checked more than 10 times the configuration on the DHCP options and it is correct.

    I have validated and revalidated the content on the DP, send and resend the Boot images on the distribution point.

    Now I followed Gerry's guide but no joy, I did a delayed service start of WDS and still nothing.

    Any more suggestions would be much appreciated.

    Lach

    Friday, July 12, 2013 12:10 PM
  • The easiest way to fix this is to NOT use DHCP options. I've never seen them work reliably. Get rid of them and configure IP helpers on the routers.


    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    Friday, July 12, 2013 12:45 PM
  • Thanks for your answer John. Correct me if I am wrong but don't IP healpers relay broadcast traffic to a DHCP server? In our case everything resides in 1 subnet so we don't really need to forward the traffic.
    Friday, July 12, 2013 2:21 PM
  • If everything in on one subnet you don't need to do anything, it should just work.


    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    Friday, July 12, 2013 3:13 PM
  • Hello again guys,

    Thank you very much for your help on the previous problem. We ended up rebuilding the server and the re-installing system center. We deployed  OS images and software applications/packages/scripts to over 1000 computers and everything went successful !!!!!!!!!!!! 

    However, this morning we tried to rebuild one of the machine, and we ended up with the same problem. Where it wouldn't boot from teh correct boot image, and it would just show that blue screen with the message. Do you guys have any suggestion how after nearly 2 months of fully functional system it would suddenly come up with this error?

    So far we have tried:

    - restarting the services

    - restarting the server

    -reinstalling wds (by disabling/enabling PXE from teh distribution point)

    - Recreating the boot images and distributing them to the distribution point

    Any other suggestion would be much appreciated.


    Kind Regards,

    L

    Tuesday, September 03, 2013 4:38 PM
  • Oh and by the way, when we login into the server after a reboot it stays:

    There is a file or folder on your computer called "C:\Program" which could cause certain applications to not function correctly. Renaming it to "C:\Program5" would solve this problem. Would you like to rename it now?


    I had this message appearing before as well when we initially had this probelm.

    L

    Wednesday, September 04, 2013 8:30 AM