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
Monday, July 3, 2017 3:28 PM
Hi,
I have roughly 50 Acer TracelMate p259 laptops (bios version 1.19 up to 1.27) that I need to build using SCCM 2012 1702 running on a windows 2016 server. I have several other desktops and laptops that work fine with PXE. For some reason I am unable to get these laptops to boot in uefi pxe. I have successfully made it boot into legacy pxe boot.
I enabled network boot and boot mode selected UEFI. Here are the smspxe logs:
Prioritizing local MP http://SCCM01.mydomain.com. SMSPXE 03/07/2017 16:13:59 4076 (0x0FEC)
Prioritizing local MP http://SCCM01.mydomain.com. SMSPXE 03/07/2017 16:13:59 4072 (0x0FE8)
Client lookup reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 03/07/2017 16:13:59 4072 (0x0FE8)
A8:1E:84:55:5E:2B, 5C315CCC-7C5B-5841-8CAE-A81E84555E2B: device is not in the database. SMSPXE 03/07/2017 16:13:59 4072 (0x0FE8)
Getting boot action for unknown machine: item key: 2046820353 SMSPXE 03/07/2017 16:13:59 4072 (0x0FE8)
Prioritizing local MP http://SCCM01.mydomain.com. SMSPXE 03/07/2017 16:13:59 4072 (0x0FE8)
Request using architecture 9. SMSPXE 03/07/2017 16:13:59 4072 (0x0FE8)
Client lookup reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 03/07/2017 16:13:59 4076 (0x0FEC)
A8:1E:84:55:5E:2B, 5C315CCC-7C5B-5841-8CAE-A81E84555E2B: device is not in the database. SMSPXE 03/07/2017 16:13:59 4076 (0x0FEC)
Getting boot action for unknown machine: item key: 2046820353 SMSPXE 03/07/2017 16:13:59 4076 (0x0FEC)
Prioritizing local MP http://SCCM01.mydomain.com. SMSPXE 03/07/2017 16:13:59 4076 (0x0FEC)
Client boot action reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="2046820353" ServerName=""><Machine><ClientID>5e473a3b-5693-42e7-9bf2-1899c80bc7cc</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="10020039" OfferIDTime="20/04/2017 15:21:00" PkgID="1000004F" PackageVersion="" PackagePath="http://SCCM01.mydomain.com/SMS_DP_SMSPKG$/10000027" BootImageID="10000027" Mandatory="0"/></ClientIDReply>
SMSPXE 03/07/2017 16:13:59 4072 (0x0FE8)
A8:1E:84:55:5E:2B, 5C315CCC-7C5B-5841-8CAE-A81E84555E2B: found optional advertisement 10020039 SMSPXE 03/07/2017 16:13:59 4072 (0x0FE8)
Getting boot action for unknown machine: item key: 2046820353 SMSPXE 03/07/2017 16:13:59 4072 (0x0FE8)
Prioritizing local MP http://SCCM01.mydomain.com. SMSPXE 03/07/2017 16:13:59 4072 (0x0FE8)
Request using architecture 9. SMSPXE 03/07/2017 16:13:59 4076 (0x0FEC)
Request using architecture 9. SMSPXE 03/07/2017 16:13:59 4072 (0x0FE8)
Client boot action reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="2046820353" ServerName=""><Machine><ClientID>5e473a3b-5693-42e7-9bf2-1899c80bc7cc</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="10020039" OfferIDTime="20/04/2017 15:21:00" PkgID="1000004F" PackageVersion="" PackagePath="http://SCCM01.mydomain.com/SMS_DP_SMSPKG$/10000027" BootImageID="10000027" Mandatory="0"/></ClientIDReply>
SMSPXE 03/07/2017 16:13:59 4076 (0x0FEC)
A8:1E:84:55:5E:2B, 5C315CCC-7C5B-5841-8CAE-A81E84555E2B: found optional advertisement 10020039 SMSPXE 03/07/2017 16:13:59 4076 (0x0FEC)
Client boot action reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="2046820353" ServerName=""><Machine><ClientID>5e473a3b-5693-42e7-9bf2-1899c80bc7cc</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="10020039" OfferIDTime="20/04/2017 15:21:00" PkgID="1000004F" PackageVersion="" PackagePath="http://SCCM01.mydomain.com/SMS_DP_SMSPKG$/10000027" BootImageID="10000027" Mandatory="0"/></ClientIDReply>
SMSPXE 03/07/2017 16:13:59 4072 (0x0FE8)
A8:1E:84:55:5E:2B, 5C315CCC-7C5B-5841-8CAE-A81E84555E2B: found optional advertisement 10020039 SMSPXE 03/07/2017 16:13:59 4072 (0x0FE8)
Getting boot action for unknown machine: item key: 2046820353 SMSPXE 03/07/2017 16:14:03 4072 (0x0FE8)
Prioritizing local MP http://SCCM01.mydomain.com. SMSPXE 03/07/2017 16:14:03 4072 (0x0FE8)
Getting boot action for unknown machine: item key: 2046820353 SMSPXE 03/07/2017 16:14:03 4076 (0x0FEC)
Prioritizing local MP http://SCCM01.mydomain.com. SMSPXE 03/07/2017 16:14:03 4076 (0x0FEC)
Request using architecture 9. SMSPXE 03/07/2017 16:14:03 4072 (0x0FE8)
Request using architecture 9. SMSPXE 03/07/2017 16:14:03 4076 (0x0FEC)
Client boot action reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="2046820353" ServerName=""><Machine><ClientID>5e473a3b-5693-42e7-9bf2-1899c80bc7cc</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="10020039" OfferIDTime="20/04/2017 15:21:00" PkgID="1000004F" PackageVersion="" PackagePath="http://SCCM01.mydomain.com/SMS_DP_SMSPKG$/10000027" BootImageID="10000027" Mandatory="0"/></ClientIDReply>
SMSPXE 03/07/2017 16:14:03 4072 (0x0FE8)
A8:1E:84:55:5E:2B, 5C315CCC-7C5B-5841-8CAE-A81E84555E2B: found optional advertisement 10020039 SMSPXE 03/07/2017 16:14:03 4072 (0x0FE8)
Getting boot action for unknown machine: item key: 2046820353 SMSPXE 03/07/2017 16:14:03 4072 (0x0FE8)
Prioritizing local MP http://SCCM01.mydomain.com. SMSPXE 03/07/2017 16:14:03 4072 (0x0FE8)
Client boot action reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="2046820353" ServerName=""><Machine><ClientID>5e473a3b-5693-42e7-9bf2-1899c80bc7cc</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="10020039" OfferIDTime="20/04/2017 15:21:00" PkgID="1000004F" PackageVersion="" PackagePath="http://SCCM01.mydomain.com/SMS_DP_SMSPKG$/10000027" BootImageID="10000027" Mandatory="0"/></ClientIDReply>
SMSPXE 03/07/2017 16:14:03 4076 (0x0FEC)
A8:1E:84:55:5E:2B, 5C315CCC-7C5B-5841-8CAE-A81E84555E2B: found optional advertisement 10020039 SMSPXE 03/07/2017 16:14:03 4076 (0x0FEC)
Request using architecture 9. SMSPXE 03/07/2017 16:14:03 4072 (0x0FE8)
Client boot action reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="2046820353" ServerName=""><Machine><ClientID>5e473a3b-5693-42e7-9bf2-1899c80bc7cc</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="10020039" OfferIDTime="20/04/2017 15:21:00" PkgID="1000004F" PackageVersion="" PackagePath="http://SCCM01.mydomain.com/SMS_DP_SMSPKG$/10000027" BootImageID="10000027" Mandatory="0"/></ClientIDReply>
SMSPXE 03/07/2017 16:14:03 4072 (0x0FE8)
A8:1E:84:55:5E:2B, 5C315CCC-7C5B-5841-8CAE-A81E84555E2B: found optional advertisement 10020039 SMSPXE 03/07/2017 16:14:03 4072 (0x0FE8)
I then ran wireshark trace and here are the results:
192.168.10.6 is my DHCP Server and 192.168.10.80 is my sccm server.
Ive read some post about option 66/67 in dhcp but which I had changed but that didn't make a difference?
I don't know much about this issue so I hope someone here will be able to point me in the right direction?
Kind regards
Tyrone
All replies (17)
Monday, July 3, 2017 5:25 PM
> "SCCM 2012 1702 "
There's no such thing. 1702 is a version of ConfigMgr/SCCM Current Branch and is not associated with 2012 at all.
Define "unable to get these laptops to boot in uefi pxe"? That's a pretty meaningless and ambiguous statement. Is there an error message or any message at all? What exactly does happen and what exactly does not happen that you are expecting to happen. Where exactly does it stop and what is on the target system's screen when it "stops"?
For your issues, it looks like everything on the ConfigMgr side is working properly. Have you tried updating the UEFI firmware on the devices?
Jason | http://blog.configmgrftw.com | @jasonsandys
Tuesday, July 4, 2017 8:13 AM
Jason,
Thanks for your response. My lack of knowledge is probably part of my issue here. I have updated the post.
To clarify i can get them to boot legacy lan (PXE) but when i enable UEFI (Secure Boot) and boot up it just does nothing. No errors i can see at all. All it states is Start PXE over IPv4, Press [ESC] to Exit... that message does flash up twice after about 5 seconds each (As it flashes i can see activity on Wireshark at that exact moment) then it changes to IPv6 does the same , After about 30 seconds it will boot into the os ( If i remove the os on its hdd it gives me an error stating boot device missing). Screen shots below:
I've upgraded the Bios of the the laptop but i'm not sure how i update the UEFI Firmware? I've done a quick online search but i haven't found anything?
Thanks again for your response.
Regards
Tyrone
Tuesday, July 4, 2017 3:02 PM
So are you using DHCP scope options or IP helpers?
If DHCP scope options, why?
Also if DHCP scope options, what exactly do you have configured?
What architecture is the boot image with ID 10000027?
Jason | http://blog.configmgrftw.com | @jasonsandys
Tuesday, July 4, 2017 4:38 PM
Neither, its my understanding that you only use DHCP Scope options and IP helpers if the client and servers are on different subsets and/or the DHCP server and SCCM is the same box. I have separate servers for each and they all on one flat vlan including my clients.
ID 10000027 is x64 it is however an MDT created boot image if that has any bearing on it? How do i get it to use my other boot image?
Tuesday, July 4, 2017 4:57 PM
I figured out how to get sccm to use an alternate boot image. I disabled all my task sequences. I created a new task using the alternate boot image. After booting up into pxe it used my other boot image
BootImageID="10000017" which is also x64 but it still did not work. I also tried to x86 image but i then get an error: No boot action. Rejected.
This is rather frustrating...
Tuesday, July 4, 2017 6:49 PM
So to verify, your clients are on the same subnet as your PXE enabled DP is?
(DHCP and SCCM server -- whatever that is -- have no bearing on this as PXE is a network-level function).
Boot image selection is based upon the boot image assigned to the task sequence for required deployments or the most recently deployed task sequence for available deployments.
Jason | http://blog.configmgrftw.com | @jasonsandys
Tuesday, July 4, 2017 9:34 PM
I figured out how to get sccm to use an alternate boot image. I disabled all my task sequences. I created a new task using the alternate boot image. After booting up into pxe it used my other boot image
BootImageID="10000017" which is also x64 but it still did not work. I also tried to x86 image but i then get an error: No boot action. Rejected.
This is rather frustrating...
"doesn't work"?? could we have a little more detail please? did the symptom change from the previous issue at all? No progress forward, compared to previous issue? Or has it moved forward a little and you're now getting a different issue?
*you can't PXE-boot an UEFI-x64 machine by using an x86 bootfile. so your attempt with x86 which failed, is correct failure.
>> Request using architecture 9
That's a good sign, it means that the device is presenting/attempting PXE in the form of 'UEFI x86-64', which suggests that your device firmware config for PXE-booting seems ok. (although there can be other firmware config required, it varies by vendor)
I often find it useful to look into the Windows event logs for WDS on the PXE-enabled-DP. The SMSPXE.log by itself can be hard to use, and it doesn't record everything. The WDS log will show you when a client device requests the various files for TFTP download, and what the WDS responded with.
e.g.: Request wdsnbp.com, send wdsnbp.com, request boot.sdi, send boot.sdi, etc.
For an UEFI PXE-boot scenario, the client should *not* be sent wdsnbp.com (because that's only for legacy/BIOS/MBR PXE-boot scenarios). An UEFI client should be sent wdsmgfw.efi instead. You should see that in the WDS logs.
I am guessing that this is your first-time trying to get UEFI-PXE-booting working? Things are a little different in UEFI scenarios, and just because MBR-PXE is/was working fine, doesn't mean that UEFI-PXE is ready to go. (it's a little like learning how PXE works, all over again, the rules of the UEFI game are different. Not hard, just different ;)
Don [doesn't work for MSFT, and they're probably glad about that ;]
Wednesday, July 5, 2017 7:56 AM
@ Jason, Yes they are all on the same subnet.
@ Don, to elaborate on " Doesn't work"- i get the exact same symptoms. Nothing changed. The only change i had was when i used the x86 boot image but as you and Jason mentioned that wont work with UEFI-PXE.
I've enabled those logs and i think you are onto something here: I get several error and warnings but im not sure what they mean? :
Information 05/07/2017 08:09:29 Deployment-Services-Diagnostics 32769 None
Information 05/07/2017 08:09:29 Deployment-Services-Diagnostics 32769 None
Information 05/07/2017 08:09:29 Deployment-Services-Diagnostics 32769 None
Error 05/07/2017 08:09:29 Deployment-Services-Diagnostics 24579 None
Error 05/07/2017 08:09:29 Deployment-Services-Diagnostics 24579 None
Error 05/07/2017 08:09:29 Deployment-Services-Diagnostics 24579 None
Information 05/07/2017 08:09:25 Deployment-Services-Diagnostics 32769 None
Information 05/07/2017 08:09:25 Deployment-Services-Diagnostics 32769 None
Information 05/07/2017 08:09:25 Deployment-Services-Diagnostics 32769 None
Error 05/07/2017 08:09:25 Deployment-Services-Diagnostics 24579 None
Error 05/07/2017 08:09:25 Deployment-Services-Diagnostics 24579 None
Error 05/07/2017 08:09:25 Deployment-Services-Diagnostics 24579 None
Warning 05/07/2017 08:09:20 Deployment-Services-Diagnostics 24578 None
Warning 05/07/2017 08:09:20 Deployment-Services-Diagnostics 24578 None
Warning 05/07/2017 08:09:20 Deployment-Services-Diagnostics 24578 None
Each event level has several events and within each event level the messages are identical please below:
Warning: [WDSServer/WDSPXE] PXEv6 Warning: DUID-LLT unrecognized hardware type 24
Error: [WDSServer/WDSPXE] [base\eco\wds\wdssrv\wdspxe\src\pxeep.cpp:646] Expression: , Win32 Error=0x3e5
Info: [WDSServer/WDSPXE/SMSPXE] A8:1E:84:55:5D:9A, 5E4E0182-3B21-CD48-8FC3-A81E84555D9A: found optional advertisement 1002003A
This is not the first time we using UEFI-PXE, most of our clients are UEFI-PXE deployments and they deployed fine. Thanks for the help!
Wednesday, July 5, 2017 10:36 AM
@ Jason, Yes they are all on the same subnet.
@ Don, to elaborate on " Doesn't work"- i get the exact same symptoms. Nothing changed. The only change i had was when i used the x86 boot image but as you and Jason mentioned that wont work with UEFI-PXE.
I've enabled those logs and i think you are onto something here: I get several error and warnings but im not sure what they mean? :
Information 05/07/2017 08:09:29 Deployment-Services-Diagnostics 32769 None
Information 05/07/2017 08:09:29 Deployment-Services-Diagnostics 32769 None
Information 05/07/2017 08:09:29 Deployment-Services-Diagnostics 32769 None
Error 05/07/2017 08:09:29 Deployment-Services-Diagnostics 24579 None
Error 05/07/2017 08:09:29 Deployment-Services-Diagnostics 24579 None
Error 05/07/2017 08:09:29 Deployment-Services-Diagnostics 24579 None
Information 05/07/2017 08:09:25 Deployment-Services-Diagnostics 32769 None
Information 05/07/2017 08:09:25 Deployment-Services-Diagnostics 32769 None
Information 05/07/2017 08:09:25 Deployment-Services-Diagnostics 32769 None
Error 05/07/2017 08:09:25 Deployment-Services-Diagnostics 24579 None
Error 05/07/2017 08:09:25 Deployment-Services-Diagnostics 24579 None
Error 05/07/2017 08:09:25 Deployment-Services-Diagnostics 24579 None
Warning 05/07/2017 08:09:20 Deployment-Services-Diagnostics 24578 None
Warning 05/07/2017 08:09:20 Deployment-Services-Diagnostics 24578 None
Warning 05/07/2017 08:09:20 Deployment-Services-Diagnostics 24578 NoneEach event level has several events and within each event level the messages are identical please below:
Warning: [WDSServer/WDSPXE] PXEv6 Warning: DUID-LLT unrecognized hardware type 24
Error: [WDSServer/WDSPXE] [base\eco\wds\wdssrv\wdspxe\src\pxeep.cpp:646] Expression: , Win32 Error=0x3e5
Info: [WDSServer/WDSPXE/SMSPXE] A8:1E:84:55:5D:9A, 5E4E0182-3B21-CD48-8FC3-A81E84555D9A: found optional advertisement 1002003A
This is not the first time we using UEFI-PXE, most of our clients are UEFI-PXE deployments and they deployed fine. Thanks for the help!
the PXEv6 Warning: DUID-LLT, is the PXEv6 attempt failing, because your environment or this hardware device, isn't PXEv6 ready/capable/configured.
WS2016/WDS is trying to service that PXEv6 attempt. But I wouldn't worry about that unless you are very keen to use IPv6 for this.
Win32 error 0x3e5, is an overlapped I/O request, again I think this is related to the PXEv6 attempt. I don't think you nee to bother with it.
The next log line seems to be from the actual SMSPXE provider, and that found an advertisement. Which is good.
But, what happened next? Did the service serve the EFI boot program (wdsmgfw.efi) via TFTP?
There's a very deep-logging article here but I wouldn't dive into that just yet (and not sure if it applies to WS2016);
https://support.microsoft.com/en-us/help/936625/how-to-enable-logging-in-windows-deployment-services-wds-in-windows-se
Don [doesn't work for MSFT, and they're probably glad about that ;]
Wednesday, July 5, 2017 1:52 PM
We have no need(yet) to use IPv6 for this.
Im looking in the debug section of the logs and that is the only logs, nothing else shows up?
I saw that article but i just enabled the standard logs for now.
I just tested a desktop with UEFI-PXE and it booted up fine, no problem?
Any other suggestions?
Wednesday, July 5, 2017 3:37 PM
That reinforces the premise that this is a hardware specific issue which means you need to work with the vendor to obtain a firmware update to fix the issue if they have one.
A short term fix is to use media instead of PXE.
Jason | http://blog.configmgrftw.com | @jasonsandys
Wednesday, July 5, 2017 9:16 PM
That reinforces the premise that this is a hardware specific issue which means you need to work with the vendor to obtain a firmware update to fix the issue if they have one.
A short term fix is to use media instead of PXE.
Jason | http://blog.configmgrftw.com | @jasonsandys
I agree with Jason. This looks to be an issue specific to the Acer TravelMate P259, either the configuration settings within the firmware, or, a defect/gap in that firmware implementation. I would contact Acer tech support for assistance. We used to buy Acer, and had a really great technical support manager here in AUS.
Don [doesn't work for MSFT, and they're probably glad about that ;]
Thursday, July 6, 2017 2:22 PM
Thanks Guys for all your help. I have logged this with Acer, ill update you once i have more.
Friday, July 14, 2017 3:20 PM
the response from Acer:
"
Our test server unit was running on windows 8.1 home, firewall disabled and no secure boot
We used the boot files from our uefi usb keys i.e. BCD, boot.sdi, bootx64.efi etc and our boot.wim file
We used another laptop first to test and were able to access the server via IPV4 and were able to boot from the boot.wim file, it did not complete as was not set for this unit and would need to be developed to run correctly
We then tried 2107205N with secure boot disabled and it also booted to IPV4 giving identical results
What we have shown is that the hardware is capable of connecting to a uefi server and booting.
Unit was supplied with bios 1.19, this was used for all tests. We then updated to the latest 1.27 and re-run the test and got the same result "
Any suggestions guys?
Regards
Tyrone
Friday, July 14, 2017 3:59 PM
It may turn into he said, she said, but you need to open a case with Microsoft support at this point; however, I don't see any mention of PXE or TFTP whatsoever in the copied response above so have no idea how that test case is remotely applicable here.
Jason | http://blog.configmgrftw.com | @jasonsandys
Sunday, July 16, 2017 2:28 PM
Hi Jason,
I saw that too and asked a few questions however i only got one question answered which was re server type they used:
We don’t have a uefi wimboot server so have used “tiny pxe” open source server
I have since done a little more digging in this. I built a new Win 2016 STD server, Installed/ Enabled WDS on the server and made sure its fully updated. I then copied the boot image from SCCM to the new WDS server.
On the laptop i made sure legacy was disabled and initiated the PXE boot by pressing F12 and what do you know.... IT worked!!!??? So the laptop booted UEFI-PXE so that makes me believe my SCCM setup is not right? However i can 100% confirm that SCCM works with other devices booted into UEFI-PXE.
Just to confirm that the laptop was actually in UEFI-PXE i ran these commands in WINPE:
wpeutil UpdateBootInfo
reg query HKLM\System\CurrentControlSet\Control /v PEFirmwareType
My result was: 0x2 -which is UEFI.
As Jason mentioned my next step will be to open a case with Microsoft to see what they come back with.
Friday, February 16, 2018 11:05 AM
Hi,
Were you able to solve this problem. As I'm experiencing the same problem at one of my customers.
Best regards,
Bert