Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, October 27, 2016 6:02 PM
Attempting to have two "unknown" collections. One for x86 and one for x64. We are unable to PXE boot our UEFI machines, due to the boot wim being x86. This is what we have done:
Removed all deployments from All Unknown Computers Collection.
Created two collections: All Unknown x64 Computers and All Unknown x86 Computers
For each collection the membership rules are using Direct Rule to use the appropriate resource (x64 Unknown Computer or x86 Unknown Computer)
The Task Sequences are using the appropriate boot image, depending on x86 or x64. The Task Sequences have also been deployed to the proper unknown collection.
Unknown Computer support is enabled, and the DP's are PXE-enabled.
Now when attempting a PXE Boot, it fails. In the SMSPXE log we receive messages:
no advertisements found, no boot action. rejected., and Not serviced.
If anyone could provide assistance, that would be great!
All replies (13)
Friday, October 28, 2016 4:49 PM âś…Answered
Was that log snippet above for a UEFI machine boot attempt? If so, it was identified as an unknown x86 machine as you confirmed from the itemkey which is odd since most UEFI firmware are 64-bit implementations. The PXE boot attempt is maybe being rejected due to the architecture mismatch between UEFI 64-bit and the 32-bit WinPE.
Can you do a small test? Manually create a new device record in SCCM, give it any name and assign to it the MAC and SMBIOS GUID that are noted in the log: 00:21:9B:49:5A:E0, 4C4C4544-0054-5710-805A-B3C04F574731
Add that record to the x64 collection that you created and try to PXE boot it again.
Thursday, October 27, 2016 6:52 PM
You should also see in the log a value for "ItemKey=", search for that in Devices by looking for Resource ID with that value. Check the deployments that are targeted to the device record that shows up when searching.
Did you also check to make sure that the relevant boot images have been distributed to the PXE DP you are using?
Thursday, October 27, 2016 6:54 PM | 2 votes
Hello
To fix the problem you need to associate a boot image with the task sequence by following the steps below.
Right click on the Task Sequence and choose Properties.
Click on the Advanced Tab.
Make sure that the option "Use a boot image:" is checked and that a Boot Image is selected
Regards, Regin Ravi
Thursday, October 27, 2016 7:21 PM
Hi,
Thank you for the reply. I searched the "ItemKey" (resource ID). 6 task sequences show up under the deployments tab (our 6 different images). It also shows that it is in the All Unknown x86 Computers collection. I also made sure that all relevant boot images have been distributed to all DP's.
Just seems like something isn't talking to each other, not sure what it is though.
Thursday, October 27, 2016 7:22 PM
Hello ReginRavi,
Yes, that step has already been completed.
Thank you.
Thursday, October 27, 2016 7:23 PM
Please post the entire relevant snippet from the smspxe.log -- a single out of context line is insufficient in providing enough information to help.
Jason | http://blog.configmgrftw.com | @jasonsandys
Thursday, October 27, 2016 8:31 PM
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 10/27/2016 11:39:23 AM 1404 (0x057C)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 10/27/2016 11:39:23 AM 17536 (0x4480)
Prioritizing local MP ************ SMSPXE 10/27/2016 11:39:23 AM 17536 (0x4480)
Prioritizing local MP ************. SMSPXE 10/27/2016 11:39:23 AM 1404 (0x057C)
CLibSMSMessageWinHttpTransport::Send: URL: ************ GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 10/27/2016 11:39:23 AM 17536 (0x4480)
CLibSMSMessageWinHttpTransport::Send: URL: ************ GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 10/27/2016 11:39:23 AM 1404 (0x057C)
CLibSMSMessageWinHttpTransport::Send: URL: ************ CCM_POST /ccm_system/request SMSPXE 10/27/2016 11:39:23 AM 17536 (0x4480)
CLibSMSMessageWinHttpTransport::Send: URL: ************ CCM_POST /ccm_system/request SMSPXE 10/27/2016 11:39:23 AM 1404 (0x057C)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
SMSPXE 10/27/2016 11:39:23 AM 1404 (0x057C)
00:21:9B:49:5A:E0, 4C4C4544-0054-5710-805A-B3C04F574731: no advertisements found SMSPXE 10/27/2016 11:39:23 AM 1404 (0x057C)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
SMSPXE 10/27/2016 11:39:23 AM 17536 (0x4480)
00:21:9B:49:5A:E0, 4C4C4544-0054-5710-805A-B3C04F574731: no advertisements found SMSPXE 10/27/2016 11:39:23 AM 17536 (0x4480)
Prioritizing local MP ************. SMSPXE 10/27/2016 11:39:23 AM 1404 (0x057C)
Prioritizing local MP ************ SMSPXE 10/27/2016 11:39:23 AM 17536 (0x4480)
CLibSMSMessageWinHttpTransport::Send: URL: ************ GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 10/27/2016 11:39:23 AM 1404 (0x057C)
CLibSMSMessageWinHttpTransport::Send: URL: ************ GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 10/27/2016 11:39:23 AM 17536 (0x4480)
Sending StatusMessage SMSPXE 10/27/2016 11:39:23 AM 1404 (0x057C)
Sending StatusMessage SMSPXE 10/27/2016 11:39:23 AM 17536 (0x4480)
CLibSMSMessageWinHttpTransport::Send: URL: ************ CCM_POST /ccm_system/request SMSPXE 10/27/2016 11:39:23 AM 1404 (0x057C)
CLibSMSMessageWinHttpTransport::Send: URL: ************ CCM_POST /ccm_system/request SMSPXE 10/27/2016 11:39:23 AM 17536 (0x4480)
00:21:9B:49:5A:E0, 4C4C4544-0054-5710-805A-B3C04F574731: No boot action. Rejected. SMSPXE 10/27/2016 11:39:23 AM 1404 (0x057C)
00:21:9B:49:5A:E0, 4C4C4544-0054-5710-805A-B3C04F574731: Not serviced. SMSPXE 10/27/2016 11:39:23 AM 1404 (0x057C)
00:21:9B:49:5A:E0, 4C4C4544-0054-5710-805A-B3C04F574731: No boot action. Rejected. SMSPXE 10/27/2016 11:39:23 AM 17536 (0x4480)
00:21:9B:49:5A:E0, 4C4C4544-0054-5710-805A-B3C04F574731: Not serviced. SMSPXE 10/27/2016 11:39:23 AM 17536 (0x4480)
Thursday, October 27, 2016 9:12 PM
So the system with the MAC Address/SMBIOS GUID of 00:21:9B:49:5A:E0, 4C4C4544-0054-5710-805A-B3C04F574731 is a known system which has no applicable task sequence deployments.
Jason | http://blog.configmgrftw.com | @jasonsandys
Friday, October 28, 2016 12:00 AM
I have a suspicion that when you deployed the task sequence, you did not select the option to deploy it to media/PXE.
Friday, October 28, 2016 11:10 AM
Hello,
The log states that it is an unknown machine, our task sequences have been deployed to the proper unknown machine collections. For example, Windows 10 64-bit task sequence is deployed to unknown x64 computers.
I've just checked the properties of the task sequences and they all show they are set to "Configuration Manager clients, media, and PXE" as well.
Friday, October 28, 2016 1:42 PM
Hi,
You mentioned that only UEFI devices have this issue, is it? If so, have you tried to re-install the WDS role (doing this by un-check & check the Enable PXE Support option on DP properties) which will re-populate files in the RemoteInstall folder?
Best regards,
Jimmy
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Friday, October 28, 2016 1:45 PM
Hi Jimmy,
That is correct, only UEFI devices. We have not tried that, thank you for the suggestion. We are going to have another session of "testing" on Tuesday, we will see if that helps.
Thanks!
Thursday, May 10, 2018 5:29 PM
Old thread. I had to go into the DP servicing PXE and change something benign, such as its description and it forces an update to it which somehow makes the new unknown computers become available for use. I just had to do it just now since an imaged machine didn't release the unknown machine's GUID, which made any subsequent imaging tasks say there were no available task sequences for a brand new, out of the box machine.