I just upgraded from SCCM 2012 SP1 to release 1511
When I try to image a machine via PXE boot, it's failing.
I have created two new boot images x86 and x64 -OS version 10.0.10240.16384
Under data source, I have enabled 'Deploy this boot image from the PXE-enabled distribution point' for the new boot images and disabled this option for the old boot images.
When I PXE boot a machine it does not detect the new x64 boot image. See below for message that appears on machines I PXE boot.
"WDSNBP started using DHCP referral
Contacting Server: 10.xxx.xxx.xxx
Architecture: x64
The details below show the information relating to the PXE boot request for this computer. Please provide these details to your Windows Deployment Services Administrator so that this request can be approved
Pending request ID: xx
Message from Administrator: Configuration Manager is looking for policy.
Contacting server: 10.xxx.xxx.xxx
Press F12 for network service boot
PXE-MOF: Exitign Broadcom PXE ROM"
Selected boot device failed. Press any key to reboot the system
From SMSPXE.log
Prioritizing local MP http://xxxxxxxxxx.
SMSPXE24/02/2016 18:59:114448 (0x1160)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE
24/02/2016 18:59:114448 (0x1160)
D4:BE:D9:44:75:53, 4C4C4544-0039-3810-804B-B8C04F465631: device is not in the database.SMSPXE24/02/2016 18:59:114448 (0x1160)
Prioritizing local MP http://xxxxxxx.SMSPXE24/02/2016 18:59:114448 (0x1160)
Getting boot action for unknown machine: item key: 2046820353SMSPXE24/02/2016 18:59:114448 (0x1160)
Prioritizing local MP http://xxxxxxxxxSMSPXE24/02/2016 18:59:114448 (0x1160)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820353" ServerName=""><Machine><ClientID>01b725c4-1ea8-44ce-86fe-5d556d69caca</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="P0120054" OfferIDTime="03/11/2014 14:15:00" PkgID="P01000B2" PackageVersion="" PackagePath="http://FQDN/SMS_DP_SMSPKG$/P01000C4"
BootImageID="P01000C4" Mandatory="0"/></ClientIDReply>
SMSPXE
24/02/2016 18:59:114448 (0x1160)
D4:BE:D9:44:75:53, 4C4C4544-0039-3810-804B-B8C04F465631: found optional advertisement P0120054SMSPXE24/02/2016 18:59:114448 (0x1160)
Looking for bootImage P01000C4SMSPXE24/02/2016 18:59:114448 (0x1160)
D4:BE:D9:44:75:53, 4C4C4544-0039-3810-804B-B8C04F465631: could not find boot image P01000C4SMSPXE24/02/2016 18:59:114448 (0x1160)
D4:BE:D9:44:75:53, 4C4C4544-0039-3810-804B-B8C04F465631: Not serviced.SMSPXE24/02/2016 18:59:114448 (0x1160)
It seems like it's referencing task sequences (in this case P01000B2) and then looking at whichever boot image they reference (in this case P0100C4). I thought it should just look for a x64 boot image that has 'Deploy this boot image from the PXE-enabled distribution point'' enabled (in this case there is only one boot image that has this enabled and that is P010010C
I changed the x64 Task Sequences to they are all set to use the new x64 boot image. (In task sequence properties, advanced tab, 'Use a boot image')
Itt did try to boot with the new x64 boot image but it still failed.
Prioritizing local MP http://xxxxxxxxx.SMSPXE24/02/2016 19:08:374448 (0x1160)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE
24/02/2016 19:08:374448 (0x1160)
D4:BE:D9:44:75:53, 4C4C4544-0039-3810-804B-B8C04F465631: device is not in the database.SMSPXE24/02/2016 19:08:374448 (0x1160)
Prioritizing local MP http://xxxxxx.SMSPXE24/02/2016 19:08:374448 (0x1160)
Getting boot action for unknown machine: item key: 2046820353SMSPXE24/02/2016 19:08:374448 (0x1160)
Prioritizing local MP http://xxxxxxxx.SMSPXE24/02/2016 19:08:374448 (0x1160)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820353" ServerName=""><Machine><ClientID>01b725c4-1ea8-44ce-86fe-5d556d69caca</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="P0120053" OfferIDTime="31/10/2014 13:16:00" PkgID="P01000AE" PackageVersion="" PackagePath="http://FQDN/SMS_DP_SMSPKG$/P010010C"
BootImageID="P010010C" Mandatory="0"/></ClientIDReply>
SMSPXE
24/02/2016 19:08:374448 (0x1160)
D4:BE:D9:44:75:53, 4C4C4544-0039-3810-804B-B8C04F465631: found optional advertisement P0120053SMSPXE24/02/2016 19:08:374448 (0x1160)
Looking for bootImage P010010CSMSPXE24/02/2016 19:08:374448 (0x1160)
BootImage P010010C needs to be updated (new packageID=P010010C) VersionUpdate=trueSMSPXE24/02/2016 19:08:374448 (0x1160)
PXE::CBootImageInfo::CBootImageInfo: key=P010010C
SMSPXE24/02/2016 19:08:374448 (0x1160)
Saving Media Variables to "S:\RemoteInstall\SMSTemp\2016.02.24.19.08.39.0003.{2A2C8156-2118-4F3C-80C2-AAFB6B3C00A5}.boot.var"SMSPXE24/02/2016 19:08:394448 (0x1160)
Prioritizing local MP http://xxxxxxxxxxxxx.
SMSPXE24/02/2016 19:08:394448 (0x1160)
Looking for bootImage P010010CSMSPXE24/02/2016 19:08:574448 (0x1160)
Prioritizing local MP http://xxxxxxxxxxxxx.
SMSPXE24/02/2016 19:08:574448 (0x1160)
Any advice would be very welcome!