Jump to content


  • 0
glen8

HP Pro 4000 (Intel 82567V-4 NIC) WinPE Driver Issue

Question

Hi all,

 

Started a new job a month ago and have been working with a contractor on SCCM 2007. Never used it before then but I am picking it up quite quickly. The contractor has gone now but we still have an ongoing issue with a new model of HP desktop. It's a HP PRO 4000 SFF and looks to have an Intel 82567V-4 NIC installed.

 

Last week we had to deploy seven systems that day so I ended up manually building the system from CDs, then I created a USB boot disk to run SCCM to capture the image locally. Then I copied the .wim to the network. That all worked great but the issue we have is now deploying the .wim via the network on PXE boot.

 

The other machines PXE boot into Windows PE but do not get an IP address. I have the console enabled in the boot image so can F8 into DOS. When I run an ipconfig all I get is:

 

Windows IP Configuration

 

Now looking on the internet it seems the boot image does not have the correct driver. I have downloaded the driver from HPs website, intels website and as a last resort toshibas website (older version) and injecting one by one the drivers into the boot image. Unfortunately none of them seem to be working ARGH! The image we are deploying is Windows XP 32bit. Just as a test I have even tried booting a Windows Vista and 7 32bit and 64bit images with the Vista/7 drivers. Even that didn't work. The boot image only has one driver at a time as to avoid any potential driver conflicts.

 

To make matters worse we have 50 coming today we need to be built from this .wim image

 

Please help!!!!!! Thanks, Glen.

Share this post


Link to post
Share on other sites

Recommended Posts

  • 0

Did you add the boot image to the PXE Service Point?

 

The log should be in x:\windows if memory serves

 

PXE Service Point? take that as a no lol I'm actually sat here at home going through a full server 2008 VMware build so I can get a SCCM lab setup. Might help me out a bit.

 

:edit: quick google tells me the PXE service point is a role? if that's so then yes the server does indeed have a PXE role as PXE works fine on all the other boot images apart from my new one

 

:edit: ahhhhh, think I added my boot image to the wrong location, I added it to the general DP share where all the software packages go

 

http://technet.microsoft.com/en-us/library/bb932177.aspx

 

Thanks again Chris, I owe you one. Just downloaded the latest win7 driver from intel again. There's ndis5, ndis61 and ndis62. Not sure if I have to add them all in or should I pick a paticular one. Damn, why is everything so complicated :-)

Share this post


Link to post
Share on other sites

  • 0

Hurrah!!

 

Downloaded an older intel driver (proset64 v16.0) which works fine. I can now boot into WinPE and do an IPCONFIG.

 

after fixing other issues such as corrupt packages after a VM crash and for some reason having to select in the advertisement 'run from a network DP if the task can't run locally' or something to that effect it's now working :-)

 

Thanks to everyones help, especially Chris!

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
Answer this question...

×   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...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.