Jump to content


rbisset

PXE Booting Problem With UEFI HP 430 G4

Recommended Posts

Hi Guys,

 

I'm unable to PXE boot a HP 430 G4 in UEFI mode here.

All other laptops here work on UEFI mode and legacy.

The HP 430 G4 will boot in legacy mode.

 

I have injected the network drivers into the boot image which were missing initially and can confirm they work as I have booted in legacy mode and also from a USB bootable media and both pick up the network fine.

 

When pressing F12 I get Starting PXE over IPv4 for about 5-10 seconds and then back to bios menu.

 

It happens for known and unknown computers of this model as I tried adding it in manually to make it known.

I've tried creating a new boot image with the drivers. Same results.

Using ip-helpers.

Everything definitely distributed.

 

I'm stuck here.

We have 385 of these to image and I don't want to have to change BIOS settings on each one.

Any help would be appreciated.

 

SMSPXE Log only shows this:

 

 

Prioritizing local MP http://<server>. SMSPXE 5/12/2016 12:30:14 PM 3612 (0x0E1C)

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16778518" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 5/12/2016 12:30:14 PM 3612 (0x0E1C)
98:E7:F4:6C:CF:7A, 8ECE579E-EE8A-912F-103D-FE346FCA0DA4: device is in the database. SMSPXE 5/12/2016 12:30:14 PM 3612 (0x0E1C)
Prioritizing local MP http://<server>. SMSPXE 5/12/2016 12:30:14 PM 3612 (0x0E1C)
Request using architecture 9. SMSPXE 5/12/2016 12:30:14 PM 3612 (0x0E1C)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16778518" ServerName=""><Machine><ClientID>GUID:49270912-1C6E-4B3C-AE30-978B0A13960B</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="P032000B" OfferIDTime="5/12/2016 1:25:00 AM" PkgID="P0300073" PackageVersion="" PackagePath="http://<server>/SMS_DP_SMSPKG$/P0300072" BootImageID="P0300072" Mandatory="0"/></ClientIDReply>
SMSPXE 5/12/2016 12:30:14 PM 3612 (0x0E1C)
98:E7:F4:6C:CF:7A, 8ECE579E-EE8A-912F-103D-FE346FCA0DA4: found optional advertisement P032000B SMSPXE 5/12/2016 12:30:14 PM 3612 (0x0E1C)
Prioritizing local MP http://<server>. SMSPXE 5/12/2016 12:34:15 PM 3612 (0x0E1C)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16778428" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 5/12/2016 12:34:15 PM 3612 (0x0E1C)

 

Share this post


Link to post
Share on other sites


have you distributed both architecture boot images ?

Share this post


Link to post
Share on other sites

have you distributed both architecture boot images ?

Sorry. Didn't even see your reply.

 

Yes both are distributed. Every machine except the HP 430 G4 has worked here in both modes.

I've had a case open with HP for 2 months now trying to figure this out.

I really don't think it's a problem with our ConfigMgr setup.

I'll try keep this updated in case anyone else has this problem.

Share this post


Link to post
Share on other sites

so what exactly do you see on the client when you are pxe booting ?

Share this post


Link to post
Share on other sites

I'm having the same problem with these HP 430 G4 laptops. Thankfully we only have 17 of them. We have mostly the G2 and G3 models which have been fine but with our last order from our supplier there were some of these G4 models. To answer your question anyweb it just sits on the ">>Start PXE over IPv4" screen for about 10 seconds then goes back to the BIOS Startup Menu. It's like it can't see the network at all, but they work fine in legacy and also I created a bootable USB and it runs the task sequence fine. I'll be interested to know if you hear back from HP with a solution rbisset because we won't be getting any more of this model if they can't PXE boot with UEFI. I did try updating the BIOS to the latest vesion which was 01.03 but it didn't make any difference. Since I saw you already had a case open I didn't bother contacting HP myself because in the past I've found dealing with HP technicians a bit difficult.

Share this post


Link to post
Share on other sites

I thought it may be worth a try :wacko:

- maybe this can shed some more light on it as it seems to be a known issue with HP (not sure how related this is to your issue - last comment on the link)

https://h30434.www3.hp.com/t5/Notebook-Hardware-and-Upgrade-Questions/PXE-UEFI-and-Secure-Boot/td-p/5080930

Share this post


Link to post
Share on other sites

I have the same problem, when uefi is enabled i cant get them to pxe, when other laptops are able to boot uefi pxe

But when i enable legacy and disable secure boot (this is 1 option) then it wil PXE boot over legacy and i am able to install windows through sccm, but everytime we restart the pc the bitlockerkey is asked.

 

Share this post


Link to post
Share on other sites

We have the same issue with HP EliteDesk 800 G3 SFF.  It will image up in legacy BIOS but not when you select UEFI/SecureBoot.   

Curious to see what you hear from HP.

Share this post


Link to post
Share on other sites

We are having the exact same issue with the HP Probook 450 G4 as @wingzero and @rbisset: UEFI PXE boot does not work, legacy PXE boot does work and we are also asked to enter the Bitlocker key every time.

We also have a HP Elitebook 850 G3, which works fine with UEFI PXE boot and with Legacy PXE.

@rbisset did you get any further with HP support?

Share this post


Link to post
Share on other sites

I've read that your WDS needs to be stup as standalone and not ad integrated.

I uninstalled WDS - reboot - reinstaled WDS and configured it as standalone.

I havn't tested the pxe uefi boot, because i ran into another problem when i changed form ad integrated to standalone.

Now even on my other pc's where everything worked, system center is loaded - Preparing Network Connections and then it reboots.

So there is a difference between wds integrated and standalone, but why my system center reboots i have no idea, as i am using the same boot image, so it shouldn't be a network driver problem.

Share this post


Link to post
Share on other sites

It is a known issue and at least a preview firmware is available from HP that solves the problem, I have multiple customers seeing the same issue.. Hopefully the updateed BIOS Firmware is made available soon. You should be able to get the preview from HP Support.

Regards,
Jörgen

  • Like 1

Share this post


Link to post
Share on other sites
21 hours ago, wingzero said:

I've read that your WDS needs to be stup as standalone and not ad integrated.

I uninstalled WDS - reboot - reinstaled WDS and configured it as standalone.

I havn't tested the pxe uefi boot, because i ran into another problem when i changed form ad integrated to standalone.

Now even on my other pc's where everything worked, system center is loaded - Preparing Network Connections and then it reboots.

So there is a difference between wds integrated and standalone, but why my system center reboots i have no idea, as i am using the same boot image, so it shouldn't be a network driver problem.

Shouldn't you let SCCM control the installation and configuration of WDS? Maybe now that you reconfigured it outside of SCCM, some things broke and that causes the problems you are currently experiencing?

Edited by Erik Nettekoven

Share this post


Link to post
Share on other sites
On 3/28/2017 at 2:47 AM, Jorgen Nilsson said:

It is a known issue and at least a preview firmware is available from HP that solves the problem, I have multiple customers seeing the same issue.. Hopefully the updateed BIOS Firmware is made available soon. You should be able to get the preview from HP Support.

Regards,
Jörgen

To piggy back off this, talked to HP about this earlier today as well.  Pre-release BIOS are available but they need to have it approved/signed off before providing it for testing purposes.  I was told mid-April is their tentative release date for this.  
 

Anything with a kaby lake processor is having the UEFI PXE boot issues according to them or have had reports.  They pointed to the G4 model laptops and the G3+ model desktop machines.

Edited by bbalz
grammar nazi
  • Like 3

Share this post


Link to post
Share on other sites

Today I received a preview bios from HP. Unfortunately it did not fix the problem. They are investigating the issue further.

Update: The BETA BIOS did solve the UEFI PXE boot problem. It didn't work with the BETA BIOS, because I linked the deployment to the wrong collection :blink:

HP told me they hope to make the BIOS publicly available in May

Share this post


Link to post
Share on other sites

hi all,

Did anyone manage to resolve this issue? I'm trying to PXE boot my HP ProBook 430 G4 and it just gets stuck on Starting PXE over IPv4 

Share this post


Link to post
Share on other sites
On 10/31/2017 at 1:48 PM, Cez said:

hi all,

Did anyone manage to resolve this issue? I'm trying to PXE boot my HP ProBook 430 G4 and it just gets stuck on Starting PXE over IPv4 

Have you found the reason? We have the same issue with all new computers UEFI boot, old PCs working in both modes without any issue...

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...