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, February 9, 2016 9:21 PM
Hello. I have Win 10 OSD working perfectly on computers using Legacy BIOS mode. Recently I have had to migrate all devices to UEFI BIOS mode.
OSD using UEFI mode works perfectly (exactly like in Legacy BIOS mode) when the computer being imaged has a blank disk (i.e. I run Diskpart > Select Disk 0 > Clean).
However if I want to reimage the same computer it will fail to PXE boot with Error "PXE-E18: PXE server response timeout".
If I wipe the disk, then UEFI PXE works just as it did before, and OSD works as expected.
I do not understand why it is doing this in this specific scenario.
My environment:
1. SCCM 2012 R2 SP1 standalone site on 10.10.100.112. DP with PXE is installed on this server
2. DHCP installed on DC with IP 10.10.100.10. DHCP Scope does not have Options 60, 66 or 67 which is correct since SCCM DP and DHCP server are on the same subnet.
3. OS Deployment is using ask Task Sequence based on MDT 2013 Update 1, with WDK 10. The OS Image being deployed is a Windows 10 Build 1511 Enterprise x64. The boot images are working fine and distributed to the DP's etc.
4. The computer being imaged is an HP Probook 650 G1 (very recent model) and has full UEFI BIOS enabled with all CSM modules disabled
5. The OSD Task Sequence enables Bitlocker. However I have tried this with no Bitlocker enabled with the same result.
I am stumped! Can anyone suggest something I am missing? Thanks in advance!
All replies (8)
Wednesday, February 10, 2016 1:33 PM
are you working with known or unknown computers?
Wednesday, February 10, 2016 7:04 PM
Please look at the SMSPXE.log file. That should tell you why your client is not booting from PXE.
Thursday, February 11, 2016 2:53 AM
I am using Unknown Computer Support - however I do not think this is related to Known/Unknown Computer support.
As soon as the hard drive is cleaned, the PXE boot works and the computer runs the OSD Task Sequence to completion successfully.
I am not making chnages to the computer objects in SCCM.
Thursday, February 11, 2016 2:55 AM
Thanks - I should have mentioned about SMSPXE.log before.
Nothing appears in SMSPXE.log when the the computer fails to PXE boot (no entries at all!).
After the disk is cleaned, PXE boot works fine and the SMSPXE.log shows the PXE boot initiating and succeeding.
Friday, February 12, 2016 7:44 AM
I am using Unknown Computer Support
Dear Sir,
The client is known after deploying the OS, not unknown. So you'd better create a device collection which included the client and then deploy the TS to this collection.
Best regards,
Jimmy
Saturday, February 13, 2016 2:17 AM
It's doesn't matter whether the computer is known or unknown. The deployment Task Sequence is deployed to All Systems (which includes unknown computers) except servers.
This problem does not exist for computers with Legacy mode BIOS. You can image and reimage without any problems. This is a issue with PXE booting.
The UEFI computer I am trying to reimage site on "Booting from NEtwork IP v4" for about a minute and then times out.
I have confirmed that this is not just for the HP Probook 650 G1, it is happening for the HP Elitedesk 800 G1 which is an even more common hardware model.
Tuesday, May 17, 2016 1:13 PM | 1 vote
Hi,
this is a little bit older, but I stumbled over this post while trying to image a HP ProBook 650 G1 with UEFI and SecureBoot and was experiencing something similar. But apparently in my case this was connected to DHCP. When there already is an DHCP lease for the device I am trying to PXE Boot via UEFI it is running into a timeout. Deleting the DHCP lease solves the problem. This happened only on HP ProBooks 650 G1 until now. Not on EliteBooks 820 G1&G3 and not on ProBook 650G2.
Monday, August 15, 2016 1:08 PM
Thanks Cohen0815!....took two days to figure this one out. The Probook 640 was the culprit in our case but the DHCP lease remove fixed the issue.