locked
ConfigMgr 2012 SP1 - Looking for bootimage + BooImage needs to be updated RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello, 

    We're trying to deploy a TS to several clients. The client successfully connects to the SCCM server but when hitting F12 to download the boot image we are just getting the message: sms looking for policy and PXE aborted. 

    Here is the log from SMSPXE.log: 

    Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777452" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
    SMSPXE 09.07.2013 09:35:39 7960 (0x1F18)
    XX:XX:XX:XX:XX:XX, 4C4C4544-004C-3110-8037-B8C04F585731: device is in the database. SMSPXE 09.07.2013 09:35:39 7960 (0x1F18)
    Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777452" ServerName="" ServerRemoteName=""><Machine><ClientID>GUID:30A83EBA-80E1-4E81-993B-009FFD2779CB</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="XXX20009" OfferIDTime="08.07.2013 14:15:00" PkgID="XXX0002D" PackageVersion="" PackagePath="http://SERVER-SC-001.DOMAIN.local/SMS_DP_SMSPKG$/XXX00022" BootImageID="PRI00022" Mandatory="0"/></ClientIDReply>
    SMSPXE 09.07.2013 09:35:39 7960 (0x1F18)
    XX:XX:XX:XX:XX:XX, 4C4C4544-004C-3110-8037-B8C04F585731: found optional advertisement XXX20009 SMSPXE 09.07.2013 09:35:39 7960 (0x1F18)
    Looking for bootImage XXX00022 SMSPXE 09.07.2013 09:35:39 7960 (0x1F18)
    BootImage PRI00022 needs to be updated (new packageID=PRI00022) VersionUpdate=true SMSPXE 09.07.2013 09:35:39 7960 (0x1F18)
    PXE::CBootImageInfo::CBootImageInfo: key=PRI00022 SMSPXE 09.07.2013 09:35:39 7960 (0x1F18)

    Anyone have any idea how to troubleshoot this?

    Best regards,

    kenny


    • Edited by KennyBree Tuesday, July 9, 2013 7:47 AM
    Tuesday, July 9, 2013 7:47 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Have you distributed both boot images (x86 / x64) to the PXE-enabled DP? Have you already tried updating the boot image PRI00022?

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

    Tuesday, July 9, 2013 8:51 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Yes, I discovered some errors in the SMSPXE.log after updating DP: 

    ================= PXE Provider loaded. ===================== SMSPXE 09.07.2013 11:46:52 6428 (0x191C)
    Machine is running Windows Longhorn. (NTVersion=0X601, ServicePack=1) SMSPXE 09.07.2013 11:46:52 6428 (0x191C)
    Cannot read the registry value of MACIgnoreListFile (00000000) SMSPXE 09.07.2013 11:46:52 6428 (0x191C)
    MAC Ignore List Filename in registry is empty SMSPXE 09.07.2013 11:46:52 6428 (0x191C)
    Begin validation of Certificate [Thumbprint 2B848A1FCA0858262EA26068ABF670A827910599] issued to '0927151f-6b92-4186-a037-148dd161f3f0' SMSPXE 09.07.2013 11:46:52 6428 (0x191C)
    Completed validation of Certificate [Thumbprint 2B848A1FCA0858262EA26068ABF670A827910599] issued to '0927151f-6b92-4186-a037-148dd161f3f0' SMSPXE 09.07.2013 11:46:52 6428 (0x191C)
    Initializing PXEPerfObject. SMSPXE 09.07.2013 11:46:52 6428 (0x191C)
    Could not load logging configuration for component ccmperf. Using default values. SMSPXE 09.07.2013 11:46:52 6428 (0x191C)
    Client is set to use HTTPS when available. The current state is 224. SMSPXE 09.07.2013 11:46:52 6428 (0x191C)
    Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
    SMSPXE 09.07.2013 11:46:53 6428 (0x191C)
    PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 09.07.2013 11:46:53 6428 (0x191C)
    PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 09.07.2013 11:46:53 6428 (0x191C)
    Adding PRI00021.3 SMSPXE 09.07.2013 11:46:53 6428 (0x191C)
    Adding PRI00022.8 SMSPXE 09.07.2013 11:46:54 6428 (0x191C)
    CContentDefinition::GetFileProperties failed; 0x80070003 SMSPXE 09.07.2013 11:46:54 6428 (0x191C)
    CContentDefinition::CopyFileW failed; 0x80070003 SMSPXE 09.07.2013 11:46:54 6428 (0x191C)
    CContentDefinition::ExpandContentDefinitionItems failed; 0x80070003 SMSPXE 09.07.2013 11:46:54 6428 (0x191C)
    Found new image PRI00021 SMSPXE 09.07.2013 11:46:54 6428 (0x191C)
    Opening image file D:\RemoteInstall\SMSImages\PRI00021\winpe.PRI00021.wim SMSPXE 09.07.2013 11:46:54 6428 (0x191C)
    Found Image file: D:\RemoteInstall\SMSImages\PRI00021\winpe.PRI00021.wim
     PackageID: PRI00021
     ProductName: Microsoft® Windows® Operating System
     Architecture: 9
     Description: Microsoft Windows PE (x64)
     Version:  
     Creator: 
     SystemDir: WINDOWS
    SMSPXE 09.07.2013 11:46:54 6428 (0x191C)
    Closing image file D:\RemoteInstall\SMSImages\PRI00021\winpe.PRI00021.wim SMSPXE 09.07.2013 11:46:54 6428 (0x191C)
    Found new image PRI00022 SMSPXE 09.07.2013 11:46:55 6428 (0x191C)
    Opening image file D:\RemoteInstall\SMSImages\PRI00022\winpe.PRI00022.wim SMSPXE 09.07.2013 11:46:55 6428 (0x191C)
    Found Image file: D:\RemoteInstall\SMSImages\PRI00022\winpe.PRI00022.wim
     PackageID: PRI00022
     ProductName: Microsoft® Windows® Operating System
     Architecture: 0
     Description: Microsoft Windows PE (x86)
     Version:  
     Creator: 
     SystemDir: WINDOWS
    SMSPXE 09.07.2013 11:46:55 6428 (0x191C)
    Closing image file D:\RemoteInstall\SMSImages\PRI00022\winpe.PRI00022.wim SMSPXE 09.07.2013 11:46:55 6428 (0x191C)
    Begin validation of Certificate [Thumbprint 2B848A1FCA0858262EA26068ABF670A827910599] issued to '0927151f-6b92-4186-a037-148dd161f3f0' SMSPXE 09.07.2013 11:46:55 6428 (0x191C)
    Completed validation of Certificate [Thumbprint 2B848A1FCA0858262EA26068ABF670A827910599] issued to '0927151f-6b92-4186-a037-148dd161f3f0' SMSPXE 09.07.2013 11:46:55 6428 (0x191C)
    PXE Provider finished loading. SMSPXE 09.07.2013 11:46:55 6428 (0x191C)

    I've tried to uninstall/reinstall PXE role and WDS, but I still get the same error on the PRI00022 bootimage.

    Best regards,

    Kenneth


    • Edited by KennyBree Tuesday, July 9, 2013 9:51 AM wrong spell
    Tuesday, July 9, 2013 9:49 AM