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

  • Question

  • Hey everyone,

    there's plenty of other threads with this topic but none of it could fix my problem.

    After booting into PxE my Deployment fails and I get the following error:

    The Windows Boot Configuration Data (BCD) file from the PXE Server does not contain a valid operating system entry.

    Error code: 0xc0000098

    What I have already tried is:

    • turned off PxE on the Distribution Point
    • Removed the RemoteInstall Folder
    • Restarted
    • Enabled PxE on the Distribution Point
    • Restarted after the WDS was configured

    This didn't help sadly.

    In the SMSPXE.log after the WDS installation I saw the following.

    InstallBootFilesForImage failed. 0x80004005	SMSPXE	21.08.2018 14:23:15	1684 (0x0694)
    
    Warning: Failed to copy the needed boot binaries from the boot image G:\RemoteInstall\SMSImages\F0100005\boot.F0100005.wim. 
    The operation completed successfully. (Error: 00000000; Source: Windows)	SMSPXE	21.08.2018 14:23:15	1684 (0x0694)
    
    Failed adding image G:\RemoteInstall\SMSImages\F0100005\boot.F0100005.wim. Will Retry.. 
    Unspecified error (Error: 80004005; Source: Windows)	SMSPXE	21.08.2018 14:23:15	1684 (0x0694)
    

    When I try to boot over PxE I see the following entries in the log:

    Prioritizing local MP http://MYSERVER.
    SMSPXE	21.08.2018 14:52:26	1912 (0x0778)
    00:50:56:84:43:68, 65D60442-9352-CB34-372D-7836665AF677: Not serviced.	SMSPXE	21.08.2018 14:52:26	1912 (0x0778)
    Prioritizing local MP http://MYSERVER.
    SMSPXE	21.08.2018 14:52:27	1912 (0x0778)
    00:50:56:84:43:68, 65D60442-9352-CB34-372D-7836665AF677: Not serviced.	SMSPXE	21.08.2018 14:52:27	1912 (0x0778)
    Prioritizing local MP http://MYSERVER.	
    SMSPXE	21.08.2018 14:52:27	1912 (0x0778)
    00:50:56:84:43:68, 65D60442-9352-CB34-372D-7836665AF677: Not serviced.	SMSPXE	21.08.2018 14:52:27	1912 (0x0778)

    My Checklist:

    • TS is deployed to my Collection
    • Under my Collection there's the VM where I want to start the TS.
    • Distributed Successful the Boot Images
    • Enabled PxE on the Distribution Point
    • Configured DHCP Option 066 (my SCCM Server) and 067 (smsboot\x64\wdsnbp.com

    Any help would be appreciated!

    Greetings,

    Flex


    Tuesday, August 21, 2018 1:00 PM

All replies

  • Hi,

    It seems we've re-installed the WDS role by re-enabling the PXE of DP. Have we checked the log files to confirm each step? It is encouraged we try it again and check the log for confirmation.

    1) untick the enable PXE checkbox on the distribution point. Answer yes that you want to remove the Windows Deployment service.
    2) remove boot images from your distribution point, then delete %windir%\temp
    3) check with server manager. If WDS is done uninstalling there is a reboot pending. Reboot.
    4) check if the remoteinstall folder is located on your system.
    5) If it fails to delete due to permission issues with the SMSTempBootFiles path, delete all folders except that one and then rename the remoteinstall folder something else.
    6) reboot
    7) Add the PXE point again by checking the box on the distribution point properties.
    8) Check the distrmgr.log and see if the remoteinstall folder reappears..
    9) Replicate the boot image to the DP again.  After they land you can try running an F12 and it should roll smoothly.


    If the problem persists, we may use the following PowerShell to see if this is the curlpit.
    Get-WMIObject -namespace "root" -query "SELECT * FROM __Namespace where name = 'ccm'"
    
    Get-WMIObject -namespace "root" -query "SELECT * FROM __Namespace where name = 'ccm'" | remove-wmiobject


    For more information, we may refer to:
    SCCM 2012 R2 BCD PXE Boot Fix
    https://timstidstonit.wordpress.com/2016/03/02/sccm-2012-r2-bcd-pxe-boot-fix/

    Hope the above information helps.

    Regards,

    Alex Zhu
    -----------------------------------------------
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
    Wednesday, August 22, 2018 2:44 AM
  • 1) unticked PXE on DP and answered yes to remove WDS
    2) removed boot images from my distribution point, then deleted %windir%\temp
    3) Check in the Server Manager and WDS is still selectable but if I try to remove the Role manually it say it's not installed. When I go into WDS it says "Cannot locate Windows Deployment Services"

    4) removed the RemoteInstall Folder
    5)Successfully removed the RemoteInstall Folder
    6) reboot
    7) Added the PXE point again by checking the box on the distribution point properties.
    8) Checked the distrmgr.log:

    MsiEnumRelatedProducts failed	SMS_DISTRIBUTION_MANAGER	22.08.2018 16:24:52	5384 (0x1508)
    FindProduct failed; 0x80070103	SMS_DISTRIBUTION_MANAGER	22.08.2018 16:24:52	5384 (0x1508)
    
    
    and
    
    
    Failed to open WDS service.	SMS_DISTRIBUTION_MANAGER	22.08.2018 16:24:52	5384 (0x1508)
    Failed (2) to run: ServerManagerCmd.exe -i WDS -a	SMS_DISTRIBUTION_MANAGER	22.08.2018 16:24:52	5384 (0x1508)
    
    

    I recreated the Bootimages as following:

    https://blogs.technet.microsoft.com/brandonlinton/2015/07/30/windows-10-adk-boot-image-updates-for-configuration-manager/

    9) I replicated the boot image to the DP again. I smashed again the F12 still the same error.

    Wednesday, August 22, 2018 3:08 PM
  • Get-WMIObject -namespace "root" -query "SELECT * FROM __Namespace where name = 'ccm'"

    Output:



    __GENUS          : 2
    __CLASS          : __NAMESPACE
    __SUPERCLASS     : __SystemClass
    __DYNASTY        : __SystemClass
    __RELPATH        : __NAMESPACE.Name="ccm"
    __PROPERTY_COUNT : 1
    __DERIVATION     : {__SystemClass}
    __SERVER         : SCCM
    __NAMESPACE      : ROOT
    __PATH           : \\SCCM\ROOT:__NAMESPACE.Name="ccm"
    Name             : ccm
    PSComputerName   : SCCM


    Should I execute the following command?: Get-WMIObject -namespace "root" -query "SELECT * FROM __Namespace where name = 'ccm'" | remove-wmiobject


    • Edited by Flextom Wednesday, August 22, 2018 3:14 PM
    Wednesday, August 22, 2018 3:14 PM
  • Can you please share (on OneDrive) the complete SMSPXE log file?
    Wednesday, August 22, 2018 8:15 PM
  • SMSPXE.log on OneDrive:

    https://1drv.ms/u/s!Ap0DILuxbv1NgYpp23CmrMvJgz-7RQ

    Any help would be appreciated :)


    • Edited by Flextom Thursday, August 23, 2018 6:06 AM
    Thursday, August 23, 2018 6:06 AM
  • Hi,

    At one of the SCCM client computer, open the browser and try to access the following url. Can the correct MP list be returned? If yes, we may onhold to continue executing the PowerShell.

    http://<server FQDN>/sms_mp/.sms_aut?mplist

    In addition, what is our environment? For example, the Server OS version, the SCCM version (something like 5.0.7958, 5.0.8634, etc.) and so on. Does the problem happen with a virtual machine? If yes, if we create a new VM, can it be replicated?

    From the log you posted, the follwing error message is found. Are the PXE client and the PXE server in the same subnet without any hardware/software firewall installed?

    PXE::MP_ReportStatus failed; 0x80070490

    Regards,

    Alex Zhu
    -----------------------------------------------
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
    Thursday, August 23, 2018 6:53 AM
  • Hey Alex,

    I get the following back when I open http://<server FQDN>/sms_mp/.sms_aut?mplist:

    This XML file does not appear to have any style information associated with it. The document tree is shown below.
    <MPList>
    <MP Name="MYSERVER.MYDOMAIN.NET" FQDN="MYSERVER.MYDOMAIN.NET">
    <Version>8577</Version>
    <Capabilities SchemaVersion="1.0">
    <Property Name="SSLState" Value="0"/>
    </Capabilities>
    </MP>
    </MPList>

    Server OS version: Windows Server 2016 Datacenter Version 1607 (OS Build 14393.2312)

    SCCM Version: 5.00.8577.1000

    Client: Virtual Box

    I never imported a device (new vm) in SCCM so I might try that tommorow.

    PXE Client is in the same network as the DHCP Server. The Client receives a IP-adress. The PXE Server is in another subnet. 

    Thursday, August 23, 2018 1:56 PM
  • Hi,

    Please check the permission of network access account which you have set under configure site components -> software distribution 

    Thursday, August 23, 2018 2:32 PM
  • That log file seems to be missing a lot of lines. Did you edit this file?

    Thursday, August 23, 2018 10:07 PM
  • @SCCMhelpme

    Under Configure Site Components, Network Access Account is my service account already added.

    Friday, August 24, 2018 6:34 AM
  • @Kerwin Medina

    No I haven't deleted anything. I literally copy paste it.

    Friday, August 24, 2018 6:34 AM
  • Please try to access G:\RemoteInstall\SMSImages\F0100005\boot.F0100005.wim from some other test user machine using ur Network Access Account and check if it has required permission. 
    Friday, August 24, 2018 7:11 AM
  • Hey SCCMhelpme,

    I was able to open the location G:\RemoteInstall\SMSImages\F0100005\boot.F0100005.wim. It was a shared folder. I could access it with read, write permissions.

    Friday, August 24, 2018 11:42 AM
  • The SCCM PXE provider is getting the client requests, but it thinks it does not need to respond.

    Normally, this is because you don't have a TS deployment that is targeted to the collection where the clients belong to.

    Friday, August 24, 2018 7:51 PM
  • A task sequence called W2k16 is deployed to a collection. In this collection the VM is added. 

    Any other ideas are appreciated.

    Monday, August 27, 2018 9:16 AM
  • When I disable PxE on the distribution and enable it again I see the following in the SMSPxE.log:

    Opening image file G:\RemoteInstall\SMSImages\F0100023\boot.F0100023.wim	SMSPXE	27.08.2018 13:12:50	9128 (0x23A8)
    Found Image file: G:\RemoteInstall\SMSImages\F0100023\boot.F0100023.wim
     PackageID: F0100023
     ProductName: Microsoft® Windows® Operating System
     Architecture: 9
     Description: Microsoft Windows PE (x64)
     Version:  
     Creator: 
     SystemDir: WINDOWS
    	SMSPXE	27.08.2018 13:12:50	9128 (0x23A8)
    Closing image file G:\RemoteInstall\SMSImages\F0100023\boot.F0100023.wim	SMSPXE	27.08.2018 13:12:50	9128 (0x23A8)
    InstallBootFilesForImage failed. 0x80004005	SMSPXE	27.08.2018 13:12:51	9128 (0x23A8)
    Warning: Failed to copy the needed boot binaries from the boot image G:\RemoteInstall\SMSImages\F0100023\boot.F0100023.wim. 
    The operation completed successfully. (Error: 00000000; Source: Windows)	SMSPXE	27.08.2018 13:12:51	9128 (0x23A8)
    Failed adding image G:\RemoteInstall\SMSImages\F0100023\boot.F0100023.wim. Will Retry.. 
    Unspecified error (Error: 80004005; Source: Windows)	SMSPXE	27.08.2018 13:12:51	9128 (0x23A8)
    Monday, August 27, 2018 11:19 AM
  • Hi,

    For this problem, based on the below article. The pxeboot.com downloads the bootmgr.exe and prepares the .bcd file. Our problem occurs from here.

    https://support.microsoft.com/en-us/help/10082/troubleshooting-pxe-boot-issues-in-configuration-manager-2012

    Just to confirm with you, after we disable the PXE (uninstall the WDS role), have we removed the RemoteInstall folder? If not yet, we can try it to see if it helps.

    Hope the above information helps.

    Regards,

    Alex Zhu
    -----------------------------------------------
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
    Tuesday, August 28, 2018 8:27 AM
  • Hey Alex Zhu,

    everytime I disable PxE I let it deinstall WDS and after that I reboot the system. After that I delete the whole RemoteInstall Folder and enable PxE again. RemoteInstall gets newly created.

    Any other ideas are appreciated.

    Kind regards,

    Flex

    Tuesday, August 28, 2018 11:04 AM
  • Hi,

    Thank you very much for the tesing.

    For this problem, if we are familiar with wireshark or network monitor, we can capture to see which .bcd file is downloaded via TFTP. Hope the step can narrow down the problem.



    Normally, it should download a .bcd file that begins with date (file size is about 12k, contains an entry to boot into PE). We can copy the file from corresponding folder of WDS server to verify.



    The default .bcd file that begins x86x64 (file size is about 8k) actually contains no entry at all.



    Hope the above information helps.

    Regards,

    Alex Zhu
    -----------------------------------------------
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
    Wednesday, August 29, 2018 5:44 AM

  • In my RemoteInstall\SMSTemp I have a file named:

    2018.08.27.13.35.10.03.{24FB3E2E-A992-4F50-98D8-E739349A2522}.boot.bcd

    I executed the following command:

    bcdedit /store 'G:\RemoteInstall\SMSTemp\2018.08.27.13.35.10.03.{24FB3E2E-A992-4F50-98D8-E739349A2522}.boot.bcd'

    Wednesday, August 29, 2018 2:00 PM
  • Still the same error appears:

    The Windows Boot Configuration Data (BCD) file from the PXE server does not contain a valid operating system entry. Ensure that the server has boot images installed for this architecture.

    File: \Tmp\x86x64{0667F30C-AD6C-9197-6815B3FD8519}.bcd

    Error code: 0xc0000098

    The server can access the boot file I tried it over the share. The firewall also allows successful TFTP connections.

    Any other ideas?

    Wednesday, August 29, 2018 2:09 PM
  • Look at the network trace and see if the download of the BCD file actually happens. Also, check from the network trace and see if the BCD file is coming from the correct SCCM PXE server.


    Wednesday, August 29, 2018 10:16 PM
  • Hi,

    My fault to not make myself be understood well. The first picture is a working one and the third picture is a failed one as you stated above. The bcdedit command just to verify that the .bcd file does contains an entry to boot into winPE and it will not change anything. As Kerwin suggested, we need to look into the network trace (by using wireshark or network monitor) to check why the correct .bcd file is not transferred. If the default x86x64{...}.bcd is transferred, the error occurs.

    Hope the above information helps.

    Regards,

    Alex Zhu
    -----------------------------------------------
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
    Thursday, August 30, 2018 1:20 AM
  • Hey Alex,

    I ran wireshark on my SCCM and filtered to TFTP protocol. I didn't see a Info where "Read request, File: \SMSTemp......" was written. Instead I noticed the following:

    Error Code, Code: Illegal TFTP Operation, Message: Access violation.

    Any ideas?

    Again thanks for your help and your patience!

    Greetings,

    Flex

    • Edited by Flextom Thursday, August 30, 2018 6:10 AM
    Thursday, August 30, 2018 6:09 AM
  • But who is sending what to where?

    You need to analyze that network capture and follow the interaction.

    Thursday, August 30, 2018 7:11 AM
  • My SCCM Server is sending TFTP packets to my SCCM Client.

    I have the feeling some permissions aren't correct because the following Error appears:

    Error Code, Code: Illegal TFTP Operation, Message: Access violation.

    What exactly you want me to analyze?

    • Edited by Flextom Thursday, August 30, 2018 9:03 AM
    Thursday, August 30, 2018 9:00 AM
  • Can you please share (on OneDrive) the network trace file?

    Thursday, August 30, 2018 8:41 PM
  • Sorry for the late response. Will post it tommorow (in arround 15h)
    Monday, September 3, 2018 3:00 PM
  • I filtered to TFTP:

    https://1drv.ms/u/s!Ap0DILuxbv1NgYpzUKqkQNquLj6aeg


    • Edited by Flextom Tuesday, September 4, 2018 6:34 AM
    Tuesday, September 4, 2018 6:34 AM
  • Can you please share the complete trace?

    This one looks like it is not generated by an interaction with an SCCM PXE server.

    Tuesday, September 4, 2018 8:36 PM
  • Also, it looks like WDS is responding instead of SCCM.

    You should never configure WDS for anything. When you enable the SCCM PXE option, that will install and configure WDS. You should never touch WDS after that.

    I suggest that you start clean. Remove the SCCM PXE option, remove WDS, reboot the machine, and then re-enable the SCCM PXE option. Again, do not touch WDS.

    Tuesday, September 4, 2018 9:08 PM
  • I think thats the wrong approach with checking the network traffic. There are not packets that are being dropped by our firewall. But here's the network trace from my SCCM Server that you asked for:

    https://1drv.ms/u/s!Ap0DILuxbv1NgYp1rxIdQn41roVg6Q

    Wednesday, September 5, 2018 6:14 AM
    • unchecked PXE support for clients.
    • waited a few minutes
    • rebooted
    • deleted the old RemoteInstall folder
    • rebooted
    • enabled PXE support for clients again
    • waited a few minutes 
    • rebooted again

    The following Error appears 4 times in the SMSPXE.log:

    InstallBootFilesForImage failed. 0x80004005	SMSPXE	05.09.2018 08:42:57	9464 (0x24F8)
    Warning: Failed to copy the needed boot binaries from the boot image G:\RemoteInstall\SMSImages\F0100027\boot.F0100027.wim. 
    The operation completed successfully. (Error: 00000000; Source: Windows)	SMSPXE	05.09.2018 08:42:57	9464 (0x24F8)
    Failed adding image G:\RemoteInstall\SMSImages\F0100027\boot.F0100027.wim. Will Retry.. 
    Unspecified error (Error: 80004005; Source: Windows)	SMSPXE	05.09.2018 08:42:57	9464 (0x24F8)

    I did not touch WDS. But still the same error appears when PxE booting a client. Any more ideas, suggestions?

    Wednesday, September 5, 2018 6:48 AM
  • Those are not real errors. It just means that the boot WIM is still being copied to the DP.

    Wednesday, September 5, 2018 6:10 PM
  • That network trace is not useful at all. It only contains the packets from one IP source (10.0.35.206). There is no way anyone can figure out what the interaction is between the client and the server.

    Can you please share the "complete" network trace and the corresponding SMSPXE log file? While you are at it, it would be nice to use Netmon instead. Wireshark is pretty primitive.

    The machine 10.0.35.206 is sending the following PXE continuation, and this is definitely NOT from SCCM. I can't tell why because the trace file is so incomplete.

    875 35.061753 10.0.35.206 10.0.63.248 DHCP 390 DHCP ACK - Transaction ID 0x57844368

    fPV|Ex¬

    ?ø«Ddy;WCh

    #ÎPVChSCCMDIV01.fidesintra.netboot\x86\wdsnbp.comcSc6
    #ÎaBÖeR4Ë7-x6fZöw<    PXEClient5ü6\Tmp\x86x64{BEEF38FA-E169-40B2-9153-C432719CC04A}.bcdú
    ÿÿ

    Wednesday, September 5, 2018 6:32 PM
  • That network trace is not useful at all. It only contains the packets from one IP source (10.0.35.206). There is no way anyone can figure out what the interaction is between the client and the server.

    I though I filtered it to source: 10.0.35.206 (SCCM Server) and 10.0.63.248 (Client).

    Netmon file: https://1drv.ms/u/s!Ap0DILuxbv1NgYp3d8LjBj_wx-83lw

    SMSPXE.log file: https://1drv.ms/u/s!Ap0DILuxbv1NgYp2Z5J47qpeyHQN3g

    I hope those can help you :) Thanks for your patience!

    Thursday, September 6, 2018 6:47 AM
  • Your problems are:

    1. You are using DHCP options for PXE. Do not do this. Use IP helpers.

    2. You don't have any TS deployed to the client, or whatever TS deployment you have is required/mandatory and has already run. You need to deploy a TS to a collection that contains the client.

    3. Your WDS is configured to respond. You should not configure WDS.

    Using DHCP options to PXE boot is really bad for many reasons. In your particular case, it causes the client to always download a boot file even if there is no TS for it. The DHCP options just says "go download this file and run it." The DHCP server is not a PXE server. It does not have any logic to know whether or not a client really has to boot. In addition, it masks problem (2) - it is not obvious to realize that there is no TS deployment for the client.

    Thursday, September 6, 2018 8:40 PM
  • 1. You are using DHCP options for PXE. Do not do this. Use IP helpers.

    So I should remove the DHCP option 66 and 67 that points out to the SCCM ip-address and the path: \smsboot\x64\wdsnbp? So you say I should configure IP helpers? Where can I configure that? Never heard about it. On the DHCP? On the router? Remember my Client is a VM.

    2. You don't have any TS deployed to the client, or whatever TS deployment you have is required/mandatory and has already run. You need to deploy a TS to a collection that contains the client.

    I did deploy a task sequence to the collection where the device is in. 

    3. Your WDS is configured to respond. You should not configure WDS.

    But I just disabled PXE Support from the Distribution Point and enabled PXE again so WDS gets installed again. How can I reset it so nothing is configured?

    Using DHCP options to PXE boot is really bad for many reasons. In your particular case, it causes the client to always download a boot file even if there is no TS for it. The DHCP options just says "go download this file and run it." The DHCP server is not a PXE server. It does not have any logic to know whether or not a client really has to boot. In addition, it masks problem (2) - it is not obvious to realize that there is no TS deployment for the client.

    Thursday, September 6, 2018 9:31 PM
  • Anyone here willing to help me? :) 

    I still have the same issue.

    Thursday, September 13, 2018 9:05 PM
  • Hello, I have exactly the same problem since I have upgrade SCCM to 1902. Did you find a soluce ? 

    Thx,

    Fabrice

    Friday, April 26, 2019 10:32 AM