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
Tuesday, May 10, 2016 2:24 PM
Hi all,
I'm tyring to get PXE to work. The setup is like this now;
- IP Helpers to dhcp, DP and terminal server in the client VLAN.
When booting into PXE, the client gets an IP but then gives PXE-E32: TFTP open timeout. This is the smspxe.log:
Prioritizing local MP http://DP.
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16830119" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
D0:BF:9C:**:**:**, D730017F-38AE-11E4-*: device is in the database. SMSPXE 10/05/2016 16:17:00 6012 (0x177C)
Prioritizing local MP http://DP.
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16830119" ServerName=""><Machine><ClientID>GUID:73C35A63-7A0F-4844-*</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="P0120FEA" OfferIDTime="28/04/2016 14:38:00" PkgID="P010039A" PackageVersion="" PackagePath="http://DP/SMS_DP_SMSPKG$/P010039B" BootImageID="P010039B" Mandatory="1"/></ClientIDReply>
D0:BF:9C:**:**:**, D730017F-38AE-11E4-*: using advertisement P0120FEA
Prioritizing local MP http://DP.
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16830119" ServerName=""><Machine><ClientID>GUID:73C35A63-7A0F-4844*</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="P0120FEA" OfferIDTime="28/04/2016 14:38:00" PkgID="P010039A" PackageVersion="" PackagePath="http://DP/SMS_DP_SMSPKG$/P010039B" BootImageID="P010039B" Mandatory="1"/></ClientIDReply>
D0:BF:9C:**:**:**, D730017F-38AE-11E4-*: using advertisement P0120FEA
--> I don't know if it matters but the PkgID in the line "Client boot action reply" seems very weird, since we don't have a pkg with an ID P010039A.
Kind regards,
Sander.
All replies (9)
Thursday, May 19, 2016 10:42 AM âś…Answered
Just have a look at my blogpost too. The prerequisites for UEFI boot are:
1) DHCP Option 67: smsboot\x64\wdsmgfw.efi (or IP-helpers pointing to both DHCP and WDS)
2) DHCP Option 60: PXEClient (also needed sometimes when DHCP and WDS are not on the same server!)
3) Task Sequence: Select x64 boot image (mandatory)
Source: http://henkhoogendoorn.blogspot.nl/2014/03/pxe-boot-files-in-remoteinstall-folder.html
My blogs: Henk's blog | Follow Me on: Twitter | View My Profile on: LinkedIn
Tuesday, May 10, 2016 2:28 PM
Any chance that this is the task sequence ID?
I've seen multiple "Client boot action" replies lines in the log only when packages are lost / blocked from PXE-enabled to client or vice versa.
Torsten Meringer | http://www.mssccmfaq.de
Tuesday, May 10, 2016 2:33 PM
Torsten, it is indeed the task sequence ID. However the clients doesn't download the boot image connected to the task sequence. Could this be because the IP helpers to the DP are only on the vlan the client is in? And not on the other vlans.
Wednesday, May 11, 2016 8:59 AM
Allright. It was a problem in the ACL. Got it working now, for BIOS machines.
UEFI machines are acting weird. They boot up in PXE, then the following comes on the screen:
Downloading NBP file...
Succeed to download NBP file.
No options to boot to.
-> So it seems like the uefi machine can't reach the DP?
Someone got some tips? Thanks.
Wednesday, May 11, 2016 9:01 AM
Dear Sir,
No, if you configure the IP helpers correctly, the clients on other VLAN will also find the PXE server by using the server address in IP helpers. Have you tried to re-distribute the boot images to your DP? Also make sure the WDS service is running as expected on your PXE enabled DP server.
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].
Wednesday, May 11, 2016 9:45 AM
Hi Jimmy,
There shouldn't be anything wrong with the IP helpers and the boot images as our BIOS computers work perfectly over PXE. Our UEFI machines are also working but over USB. And they're using the same boot image & task sequence.
The only problem is when PXE'ing a computer that has UEFI, then it doesn't work.
In short the case is like this;
- PXE a BIOS machine: OK
- USB a BIOS machine: OK
- PXE an UEFI machine: NOK
- USB an UEFI machine: OK
-> They're on the same VLAN. They use the same boot images, they use the same task sequence. Hell, they're even in the same collection in SCCM.
Kind regards,
Sander.
Thursday, May 12, 2016 2:56 PM
Also tried adding DHCP scope option 60 to "PXEClient", this did not fix the problem.
However, the server version of the DP (where WDS is running) is 2008. Could this be the problem? Someone got any more advice?
Kind regards,
Sander.
Thursday, May 12, 2016 6:36 PM
Can you please share the complete SMSPXE.log file? These snippets are not helpful.
Tuesday, May 17, 2016 4:17 AM
Dear Sir,
Just a confirm, did you configure DHCP option 66&67? Because you have configured IP helper correctly, there's no need to configure DHCP options (option 60 only needed in the scenario the DHCP and WDS are running on the same server).
Also note that in UEFI mode, the boot image version must match PC architecture, you can only boot a 64-bit UEFI PC from a 64-bit boot image.
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].