none
Fixing the default boot image problem in SP1 RRS feed

  • Question

  • We are having issues with our default boot images after an upgrade from RTM to SP1. I get this error in the SMsPXE.log:

    <![LOG[Warning: Failed to copy the needed boot binaries from the boot image D:\RemoteInstall\SMSImages\VSM00001\boot.XXX00001.wim. 

    I found this article about the issue. It gives a step by step solution to this problem. But I am having issues with this step: 

    "Update default boot image. Click “Execute Method” -> input object path as SMS_BootImagePackage.PackageID=”” -> UpdateDefaultImage"

    Where exactly am I supposed to click execute method? Can someone please explain how this step is done?

    Monday, January 21, 2013 9:59 AM

Answers


  • <![LOG[failed to copy D:\RemoteInstall\SMSTempBootFiles\VSM00001\WINDOWS\Boot\PXE\wdsmgfw.efi to D:\RemoteInstall\SMSBoot\x86\wdsmgfw.efi]LOG]!><time="12:16:25.789-60" date="01-21-2013" component="SMSPXE" context="" type="3" thread="3364" file="bootimagemgr.cpp:1485">


    That usually indicates that you are using a non-SP1 boot image (based on Win7 instead of Win8). Those are no longer supported with CM12 SP1.
    Remove all old boot images and make sure that you are using the new ones. Distribute both x86 and x64 to the DP(s).

    Torsten Meringer | http://www.mssccmfaq.de

    • Proposed as answer by TorstenMMVP Tuesday, January 22, 2013 8:59 AM
    • Marked as answer by Nico_ Tuesday, January 22, 2013 9:09 AM
    Monday, January 21, 2013 12:04 PM
  • This is solved. The problem was related to old boot images. After deleting them all and only using the boot images that SP1 upgraded I was able to get it to work.
    • Marked as answer by Nico_ Tuesday, January 22, 2013 8:52 AM
    Tuesday, January 22, 2013 8:52 AM

All replies

    • Proposed as answer by Jörgen NilssonMVP Monday, January 21, 2013 10:09 AM
    • Marked as answer by Nico_ Monday, January 21, 2013 10:48 AM
    • Unmarked as answer by Nico_ Monday, January 21, 2013 11:28 AM
    Monday, January 21, 2013 10:02 AM
  • Actually that did not solve my problem.. After following the instructions in the post I still get the same issue. This is what shows up in my SMSPXE.log:

    <![LOG[Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
    ]LOG]!><time="12:16:08.085-60" date="01-21-2013" component="SMSPXE" context="" type="1" thread="2024" file="libsmsmessaging.cpp:6363">
    <![LOG[D4:BE:D9:07:34:73, 4C4C4544-0036-5610-8030-B7C04F335131: device is not in the database.]LOG]!><time="12:16:08.085-60" date="01-21-2013" component="SMSPXE" context="" type="1" thread="2024" file="database.cpp:479">
    <![LOG[Warning: Matching Processor Architecture Boot Image (0) not found]LOG]!><time="12:16:08.085-60" date="01-21-2013" component="SMSPXE" context="" type="2" thread="2024" file="pxehandler.cpp:2022">
    <![LOG[D4:BE:D9:07:34:73, 4C4C4544-0036-5610-8030-B7C04F335131: Not serviced.]LOG]!><time="12:16:08.163-60" date="01-21-2013" component="SMSPXE" context="" type="1" thread="2024" file="database.cpp:479">
    <![LOG[Warning: Matching Processor Architecture Boot Image (0) not found]LOG]!><time="12:16:14.945-60" date="01-21-2013" component="SMSPXE" context="" type="2" thread="2024" file="pxehandler.cpp:2022">
    <![LOG[D4:BE:D9:07:34:73, 4C4C4544-0036-5610-8030-B7C04F335131: Not serviced.]LOG]!><time="12:16:15.008-60" date="01-21-2013" component="SMSPXE" context="" type="1" thread="2024" file="database.cpp:479">
    <![LOG[Failed to find ADK installation root registry key]LOG]!><time="12:16:24.774-60" date="01-21-2013" component="SMSPXE" context="" type="1" thread="3364" file="wimfile.cpp:226">
    <![LOG[Opening image file D:\RemoteInstall\SMSImages\VSM00001\boot.VSM00001.wim]LOG]!><time="12:16:24.774-60" date="01-21-2013" component="SMSPXE" context="" type="1" thread="3364" file="wimfile.cpp:416">
    <![LOG[Found Image file: D:\RemoteInstall\SMSImages\VSM00001\boot.VSM00001.wim
     PackageID: VSM00001
     ProductName: Microsoft® Windows® Operating System
     Architecture: 0
     Description: Microsoft Windows PE (x86)
     Version:  
     Creator: 
     SystemDir: WINDOWS
    ]LOG]!><time="12:16:24.774-60" date="01-21-2013" component="SMSPXE" context="" type="1" thread="3364" file="bootimagemgr.cpp:925">
    <![LOG[Closing image file D:\RemoteInstall\SMSImages\VSM00001\boot.VSM00001.wim]LOG]!><time="12:16:24.774-60" date="01-21-2013" component="SMSPXE" context="" type="1" thread="3364" file="wimfile.cpp:452">
    <![LOG[failed to copy D:\RemoteInstall\SMSTempBootFiles\VSM00001\WINDOWS\Boot\PXE\wdsmgfw.efi to D:\RemoteInstall\SMSBoot\x86\wdsmgfw.efi]LOG]!><time="12:16:25.789-60" date="01-21-2013" component="SMSPXE" context="" type="3" thread="3364" file="bootimagemgr.cpp:1485">
    <![LOG[InstallBootFilesForImage failed. 0x80070002]LOG]!><time="12:16:25.789-60" date="01-21-2013" component="SMSPXE" context="" type="3" thread="3364" file="bootimagemgr.cpp:1594">
    <![LOG[Warning: Failed to copy the needed boot binaries from the boot image D:\RemoteInstall\SMSImages\VSM00001\boot.VSM00001.wim. 
    The operation completed successfully. (Error: 00000000; Source: Windows)]LOG]!><time="12:16:25.789-60" date="01-21-2013" component="SMSPXE" context="" type="3" thread="3364" file="bootimagemgr.cpp:1275">
    <![LOG[Failed adding image D:\RemoteInstall\SMSImages\VSM00001\boot.VSM00001.wim. Will Retry.. 
    The system cannot find the file specified. (Error: 80070002; Source: Windows)]LOG]!><time="12:16:25.789-60" date="01-21-2013" component="SMSPXE" context="" type="3" thread="3364" file="bootimagemgr.cpp:1920">
    <![LOG[File D:\RemoteInstall\SMSTemp\2013.01.21.12.16.24.137.{A62FE68E-1886-430F-A4E7-CA66891C7CB3}.boot.bcd deleted.]LOG]!><time="12:16:25.789-60" date="01-21-2013" component="SMSPXE" context="" type="1" thread="3364" file="bootimagecache.cpp:267">
    <![LOG[File D:\RemoteInstall\SMSTemp\2013.01.21.12.16.24.137.{A62FE68E-1886-430F-A4E7-CA66891C7CB3}.boot.bcd.log deleted.]LOG]!><time="12:16:25.789-60" date="01-21-2013" component="SMSPXE" context="" type="1" thread="3364" file="bootimagecache.cpp:282">
    <![LOG[Failed to find ADK installation root registry key]LOG]!><time="12:18:25.796-60" date="01-21-2013" component="SMSPXE" context="" type="1" thread="3364" file="wimfile.cpp:226">


    • Edited by Nico_ Monday, January 21, 2013 11:28 AM
    Monday, January 21, 2013 11:27 AM
  •  A couple of things I noticed about my boot image before I did the steps above. 

    1. The version number was correct: 6.2.9200.16384
    2. Under optional components all the components are listed.
    Monday, January 21, 2013 11:33 AM

  • <![LOG[failed to copy D:\RemoteInstall\SMSTempBootFiles\VSM00001\WINDOWS\Boot\PXE\wdsmgfw.efi to D:\RemoteInstall\SMSBoot\x86\wdsmgfw.efi]LOG]!><time="12:16:25.789-60" date="01-21-2013" component="SMSPXE" context="" type="3" thread="3364" file="bootimagemgr.cpp:1485">


    That usually indicates that you are using a non-SP1 boot image (based on Win7 instead of Win8). Those are no longer supported with CM12 SP1.
    Remove all old boot images and make sure that you are using the new ones. Distribute both x86 and x64 to the DP(s).

    Torsten Meringer | http://www.mssccmfaq.de

    • Proposed as answer by TorstenMMVP Tuesday, January 22, 2013 8:59 AM
    • Marked as answer by Nico_ Tuesday, January 22, 2013 9:09 AM
    Monday, January 21, 2013 12:04 PM
  • Ok here is what has been done so far:

    1. All images that are not version 6.2.9200.16384 have been deleted. I now have 4 boot images. 2 of them have been migrated from 2007 but they do show the correct version number so it looks like they have been upgraded. None of the boot images show any of the symptoms of being corrupted. For exmaple, they show the correct version number and they have all the option available under properties -> Optional components.
    2. I have followed all the steps in the article above. I have copied the .wim files in: C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us and C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us and copied them to E:\SCCM\OSD\boot\i386 and x64. Further I renamed all the old boot images to bootimagename.wim.bak and renamed the new .wim files to boot.wim and boot.packageID.wim. Then I reuploaded all the boot images to the DPs and I have booted the pxe server.

    Still get the errors when I try to pxe boot. 

    The screen on the machine I try to boot shows:

    File: \Boot\BCD

    Status:0xc000000f

    Info: An error occured while attempting to read the boot configuration data.

    The SMSPXE.log shows this when I try to PXE boot:

    <![LOG[Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>

    ]LOG]!><time="14:11:22.302-60" date="01-21-2013" component="SMSPXE" context="" type="1" thread="2012" file="libsmsmessaging.cpp:6363">

    <![LOG[D4:BE:D9:07:34:73, 4C4C4544-0036-5610-8030-B7C04F335131: device is not in the database.]LOG]!><time="14:11:22.302-60" date="01-21-2013" component="SMSPXE" context="" type="1" thread="2012" file="database.cpp:479">

    <![LOG[Warning: Matching Processor Architecture Boot Image (0) not found]LOG]!><time="14:11:22.365-60" date="01-21-2013" component="SMSPXE" context="" type="2" thread="2012" file="pxehandler.cpp:2022">

    <![LOG[D4:BE:D9:07:34:73, 4C4C4544-0036-5610-8030-B7C04F335131: Not serviced.]LOG]!><time="14:11:29.177-60" date="01-21-2013" component="SMSPXE" context="" type="1" thread="2012" file="database.cpp:479">

    <![LOG[Failed to find ADK installation root registry key]LOG]!><time="14:11:54.663-60" date="01-21-2013" component="SMSPXE" context="" type="1" thread="3652" file="wimfile.cpp:226">


    • Edited by Nico_ Monday, January 21, 2013 1:14 PM
    Monday, January 21, 2013 1:13 PM
  • This is solved. The problem was related to old boot images. After deleting them all and only using the boot images that SP1 upgraded I was able to get it to work.
    • Marked as answer by Nico_ Tuesday, January 22, 2013 8:52 AM
    Tuesday, January 22, 2013 8:52 AM