gmonks Posted January 15, 2014 Posted January 15, 2014 Hi, We have a problem here with a network card driver when trying to image via WDS. The machine which is a HP Pro 600 G1 won't pick up an IP address which I have assumed is a network driver problem. We have other PCs on our network which are a range of makes and models and they image just fine. WDS is configured correctly and I have added the drivers from the disc HP supplied with the desktop to the WDS console. I have also tried the drivers off the HP website. We had a similar problem to some desktops we brought from HP at Easter, they were HP Pro 6300 desktops. After a lot of communication with their tech support, they sent a capture image just to be used for that model of machine that sorted the problem. At the moment with this case, we're a month in and HP are being very difficult about the situation and was wondering if anybody has come accross anything similar before and if so, what did you do to resolve it? Any suggestions gratefully received. George.
cromertech Posted January 15, 2014 Posted January 15, 2014 Which version of windows are you attempting to deploy with this. I had an enormous amount of trouble with some hp 655 laptops http://www.edugeek.net/forums/o-s-deployment/129863-frustration-lan-driver.html There are some tools that use can use with winpe image to see what drivers are loaded.
gmonks Posted January 15, 2014 Author Posted January 15, 2014 Which version of windows are you attempting to deploy with this. I had an enormous amount of trouble with some hp 655 laptops http://www.edugeek.net/forums/o-s-deployment/129863-frustration-lan-driver.html There are some tools that use can use with winpe image to see what drivers are loaded. Trying to deploy Windows 7 Professional 64 bit. It's not acquiring an IP address but will see if the driver is loading.
Achandler Posted January 15, 2014 Posted January 15, 2014 If your not getting an IP, then you aren't PXE booting yet, sounds like a DHCP error. I know PXE boot can be funny when machines have had fixed IPs set in Windows, I have no diea why but removing them sometimes fixes it. No driver is loaded by WDS at that point, well not that I know, you can only add drivers to the boot.wim or the install (via driver packages).
gmonks Posted January 15, 2014 Author Posted January 15, 2014 If your not getting an IP, then you aren't PXE booting yet, sounds like a DHCP error. I know PXE boot can be funny when machines have had fixed IPs set in Windows, I have no diea why but removing them sometimes fixes it. No driver is loaded by WDS at that point, well not that I know, you can only add drivers to the boot.wim or the install (via driver packages). I boot the machine and go F12 and then choose the capture image. (I want to capture an image.) However once in there I get no IP. I don't understand how it could be a DHCP error. I imaged 16 machines last week no problem. (HPs) Not had any other DHCP errors recently either.
Achandler Posted January 15, 2014 Posted January 15, 2014 Well the machine first gets an IP when you hit F12, and from what you wrote, I thought you meant it was there when you had the problem. The process should be: Choose network boot Machine gets IP from DHCP Machine gets a response from your WDS server You hit F12 You choose what to boot up (usually a boot or a capture wim) The black loading screen shows with the boot.wim loading at the bottom Then Windows boot wim opens You put in your account details You choose the image Partition the drive Install Windows Get a brew. At won't point does it fail?
gmonks Posted January 15, 2014 Author Posted January 15, 2014 Well the machine first gets an IP when you hit F12, and from what you wrote, I thought you meant it was there when you had the problem. The process should be: Choose network boot Machine gets IP from DHCP Machine gets a response from your WDS server You hit F12 You choose what to boot up (usually a boot or a capture wim) The black loading screen shows with the boot.wim loading at the bottom Then Windows boot wim opens You put in your account details You choose the image Partition the drive Install Windows Get a brew. At won't point does it fail? I do all of the following Choose network boot Machine gets IP from DHCP Machine gets a response from your WDS server You hit F12 You choose what to boot up (usually a boot or a capture wim) Select a capture image. Then Windows boot wim opens I select what I want to call the image and then I try and input the server name to save the image to, and it cannot find the server. I hit Shift+F10 and go ipconfig and it just comes back with "Windows IP Configuration" and no IP address. I loaded the setupapi.app.log and get the following: [Device Install Log] OS Version = 6.1.7600 Service Pack = 0.0 Suite = 0x0100 ProductType = 1 Architecture = amd64 [beginLog] [boot Session: 2014/01/15 15:05:33.484] >>> [build Driver List - ACPI\IFX0102\1] >>> Section start 2014/01/15 15:05:46.697 cmd: winpeshl.exe cpy: Policy is set to make all digital signatures equal. <<< Section end 2014/01/15 15:05:46.728 <<< [Exit status: SUCCESS] >>> [build Driver List - PCI\VEN_8086&DEV_8C3A&SUBSYS_18E7103C&REV_04\3&11583659&0&B0] >>> Section start 2014/01/15 15:05:46.728 cmd: winpeshl.exe cpy: Policy is set to make all digital signatures equal. <<< Section end 2014/01/15 15:05:46.760 <<< [Exit status: SUCCESS] >>> [build Driver List - USB\VID_03F0&PID_0B4A\6&3230B2B9&0&5] >>> Section start 2014/01/15 15:05:46.760 cmd: winpeshl.exe cpy: Policy is set to make all digital signatures equal. <<< Section end 2014/01/15 15:05:46.791 <<< [Exit status: SUCCESS] >>> [build Driver List - ACPI\INT0800\4&8E6F043&0] >>> Section start 2014/01/15 15:05:46.791 cmd: winpeshl.exe cpy: Policy is set to make all digital signatures equal. <<< Section end 2014/01/15 15:05:46.884 <<< [Exit status: SUCCESS] >>> [build Driver List - ACPI\INT3F0D\4&8E6F043&0] >>> Section start 2014/01/15 15:05:46.884 cmd: winpeshl.exe cpy: Policy is set to make all digital signatures equal. <<< Section end 2014/01/15 15:05:46.978 <<< [Exit status: SUCCESS] >>> [build Driver List - HDAUDIO\FUNC_01&VEN_10EC&DEV_0221&SUBSYS_103C18E7&REV_1000\4&34761DB2&0&0001] >>> Section start 2014/01/15 15:05:46.978 cmd: winpeshl.exe cpy: Policy is set to make all digital signatures equal. <<< Section end 2014/01/15 15:05:47.009 <<< [Exit status: SUCCESS] >>> [build Driver List - PCI\VEN_8086&DEV_153A&SUBSYS_18E7103C&REV_04\3&11583659&0&C8] >>> Section start 2014/01/15 15:05:47.009 cmd: winpeshl.exe cpy: Policy is set to make all digital signatures equal. <<< Section end 2014/01/15 15:05:47.040 <<< [Exit status: SUCCESS] >>> [build Driver List - PCI\VEN_8086&DEV_8C3D&SUBSYS_18E7103C&REV_04\3&11583659&0&B3] >>> Section start 2014/01/15 15:05:47.040 cmd: winpeshl.exe cpy: Policy is set to make all digital signatures equal. <<< Section end 2014/01/15 15:05:47.072 <<< [Exit status: SUCCESS] >>> [build Driver List - ACPI\PNP0000\4&8E6F043&0] >>> Section start 2014/01/15 15:05:47.072 cmd: winpeshl.exe cpy: Policy is set to make all digital signatures equal. <<< Section end 2014/01/15 15:05:47.150 <<< [Exit status: SUCCESS] >>> [build Driver List - ACPI\PNP0100\4&8E6F043&0] >>> Section start 2014/01/15 15:05:47.150 cmd: winpeshl.exe cpy: Policy is set to make all digital signatures equal. <<< Section end 2014/01/15 15:05:47.228 <<< [Exit status: SUCCESS] >>> [build Driver List - HDAUDIO\FUNC_01&VEN_8086&DEV_2807&SUBSYS_80860101&REV_1000\4&38892E42&0&0001] >>> Section start 2014/01/15 15:05:47.228 cmd: winpeshl.exe cpy: Policy is set to make all digital signatures equal. <<< Section end 2014/01/15 15:05:47.259 <<< [Exit status: SUCCESS] >>> [build Driver List - ACPI\PNP0103\0] >>> Section start 2014/01/15 15:05:47.259 cmd: winpeshl.exe cpy: Policy is set to make all digital signatures equal. <<< Section end 2014/01/15 15:05:47.337 <<< [Exit status: SUCCESS] >>> [build Driver List - ACPI\PNP0200\4&8E6F043&0] >>> Section start 2014/01/15 15:05:47.337 cmd: winpeshl.exe cpy: Policy is set to make all digital signatures equal. <<< Section end 2014/01/15 15:05:47.430 <<< [Exit status: SUCCESS] >>> [build Driver List - ACPI\PNP0303\4&8E6F043&0] >>> Section start 2014/01/15 15:05:47.430 cmd: winpeshl.exe cpy: Policy is set to make all digital signatures equal. <<< Section end 2014/01/15 15:05:47.462 <<< [Exit status: SUCCESS] >>> [build Driver List - PCI\VEN_8086&DEV_8C22&SUBSYS_18E7103C&REV_04\3&11583659&0&FB] >>> Section start 2014/01/15 15:05:47.462 cmd: winpeshl.exe cpy: Policy is set to make all digital signatures equal. <<< Section end 2014/01/15 15:05:47.493 <<< [Exit status: SUCCESS] >>> [build Driver List - ACPI\PNP0C01\1] >>> Section start 2014/01/15 15:05:47.493 cmd: winpeshl.exe cpy: Policy is set to make all digital signatures equal. <<< Section end 2014/01/15 15:05:47.571 <<< [Exit status: SUCCESS] >>> [build Driver List - ACPI\PNP0C02\1] >>> Section start 2014/01/15 15:05:47.571 cmd: winpeshl.exe cpy: Policy is set to make all digital signatures equal. <<< Section end 2014/01/15 15:05:47.664 <<< [Exit status: SUCCESS] >>> [build Driver List - ACPI\PNP0C02\10] >>> Section start 2014/01/15 15:05:47.664 cmd: winpeshl.exe cpy: Policy is set to make all digital signatures equal. <<< Section end 2014/01/15 15:05:47.758 <<< [Exit status: SUCCESS] >>> [build Driver List - ACPI\PNP0C02\111] >>> Section start 2014/01/15 15:05:47.758 cmd: winpeshl.exe cpy: Policy is set to make all digital signatures equal. <<< Section end 2014/01/15 15:05:47.836 <<< [Exit status: SUCCESS] >>> [build Driver List - ACPI\PNP0C02\2] >>> Section start 2014/01/15 15:05:47.836 cmd: winpeshl.exe cpy: Policy is set to make all digital signatures equal. <<< Section end 2014/01/15 15:05:47.930 <<< [Exit status: SUCCESS] >>> [build Driver List - ACPI\PNP0C04\4&8E6F043&0] >>> Section start 2014/01/15 15:05:47.930 cmd: winpeshl.exe cpy: Policy is set to make all digital signatures equal. <<< Section end 2014/01/15 15:05:48.008 <<< [Exit status: SUCCESS] >>> [build Driver List - PCI\VEN_8086&DEV_0412&SUBSYS_18E7103C&REV_06\3&11583659&0&10] >>> Section start 2014/01/15 15:05:48.008 cmd: winpeshl.exe cpy: Policy is set to make all digital signatures equal. <<< Section end 2014/01/15 15:05:48.039 <<< [Exit status: SUCCESS] >>> [build Driver List - PCI\VEN_8086&DEV_8C31&SUBSYS_18E7103C&REV_04\3&11583659&0&A0] >>> Section start 2014/01/15 15:05:48.039 cmd: winpeshl.exe cpy: Policy is set to make all digital signatures equal. <<< Section end 2014/01/15 15:05:48.070 <<< [Exit status: SUCCESS] >>> [build Driver List - ACPI\PNP0F03\4&8E6F043&0] >>> Section start 2014/01/15 15:05:48.070 cmd: winpeshl.exe cpy: Policy is set to make all digital signatures equal. <<< Section end 2014/01/15 15:05:48.101 <<< [Exit status: SUCCESS]
Achandler Posted January 15, 2014 Posted January 15, 2014 Ok, so it fails later on. Quite common actually, I get it with all sorts of drivers not installing. If you download the correct driver for the HP machine's network card, then add it to your WDS server (assuming 2008R2) this is easy, just right-click drivers and add package. Then add it. After that go to Boot Images within the WDS server, then right-click your capture boot image and hit add driver package. Use the search to find the network card driver (I often add all "net") drivers, and let it mount the image and add the driver. Might take about 10-15 minutes, then try again. It is the driver missing from here which is causing the issue probably, even though it PXE booted successfully.
gmonks Posted January 16, 2014 Author Posted January 16, 2014 Ok, so it fails later on. Quite common actually, I get it with all sorts of drivers not installing. If you download the correct driver for the HP machine's network card, then add it to your WDS server (assuming 2008R2) this is easy, just right-click drivers and add package. Then add it. After that go to Boot Images within the WDS server, then right-click your capture boot image and hit add driver package. Use the search to find the network card driver (I often add all "net") drivers, and let it mount the image and add the driver. Might take about 10-15 minutes, then try again. It is the driver missing from here which is causing the issue probably, even though it PXE booted successfully. Hi sorry I didn't get back to you last night, I added the drivers to the boot image and it still didn't work....?
Achandler Posted January 16, 2014 Posted January 16, 2014 So the IP Config /all still shows no network cards? Or does it show you one without an IP?
gmonks Posted January 16, 2014 Author Posted January 16, 2014 So the IP Config /all still shows no network cards? Or does it show you one without an IP? Yep if I go ipconfig it just says "Windows IP Configuration"
Achandler Posted January 16, 2014 Posted January 16, 2014 So the Windows PE still isn't seeing your network card, what make is the actual network card? You could ofcourse just capture local then manually upload after. It is a work around but depends how time crucial this is.
gmonks Posted January 16, 2014 Author Posted January 16, 2014 So the Windows PE still isn't seeing your network card, what make is the actual network card? You could ofcourse just capture local then manually upload after. It is a work around but depends how time crucial this is. Network card is an Intel. Intel I217-LM.
Achandler Posted January 16, 2014 Posted January 16, 2014 https://communities.intel.com/thread/43218 Seems a common problem, people seem to have a solution for it. 1
gmonks Posted January 16, 2014 Author Posted January 16, 2014 https://communities.intel.com/thread/43218 Seems a common problem, people seem to have a solution for it. Still doesn't work! I download the driver from the Intel website, extracted it and uploaded it to WDS and the Capture image. However, 14 of the files wouldn't add and I'm wondering if they are the ones required for it to pick up an IP address. They won't add I can only assume because they're unsigned drivers. I copied one .inf file to my memory stick, one that the a poster said worked on the link you sent and I tried to inject that driver but I got an error code back.
Achandler Posted January 16, 2014 Posted January 16, 2014 It has to eb a driver issue at some stage, after soem further reading there are a few people with the same problem. The issue is only on that other thread did there seem to be an actual answer that might be right, ebcause they mentioned all the driver .infs and adding them to the .wim but making sure you had certain ones because some simply didnt work. They mention driver issues again here Hp ProDesk600 G1 - Integrated Intel® I217LM preboot driver | Symantec Connect Community but the link to the "working" drivers doesn't seem to work for me. Dell Latitude E7440 support for Windows PE4 - Petri IT Knowledgebase Forums it is mentioned in post #5 exactly what .inf the guy uses, so you could check you definitely have that oen in your wim and that it wasn't one of the ones that failed to install. You have definitely both added them to the "Drivers" folder for want of a better word and then added it to your capture .wim How many of these desktops do you have? 1
gmonks Posted January 17, 2014 Author Posted January 17, 2014 It has to eb a driver issue at some stage, after soem further reading there are a few people with the same problem. The issue is only on that other thread did there seem to be an actual answer that might be right, ebcause they mentioned all the driver .infs and adding them to the .wim but making sure you had certain ones because some simply didnt work. They mention driver issues again here Hp ProDesk600 G1 - Integrated Intel® I217LM preboot driver | Symantec Connect Community but the link to the "working" drivers doesn't seem to work for me. Dell Latitude E7440 support for Windows PE4 - Petri IT Knowledgebase Forums it is mentioned in post #5 exactly what .inf the guy uses, so you could check you definitely have that oen in your wim and that it wasn't one of the ones that failed to install. You have definitely both added them to the "Drivers" folder for want of a better word and then added it to your capture .wim How many of these desktops do you have? 3 desktops so not many just don't want to have a different approach (ie. ghost) for one set of machines. I'll see what I can do from reading those links and get back to you next week. Thanks for your help. George.
jessee Posted June 5, 2014 Posted June 5, 2014 (edited) Hello, I have 25 HP 600 G1s and have been struggling to get them to image. I'm trying to deploy an image to them rather than capture one, as the poster was, but my issue seems rather similar: WDS is running on Server 2008 R2 Choose network boot Machine gets IP from DHCP Machine gets a response from your WDS server You hit F12 You choose what to boot up (Deployment Image) The black loading screen shows with the boot.wim loading at the bottom I very briefly see the green progress bar screen, then the blue splash screen with "Setup is Starting" Then the pop-up: "Install Winows - WDSClient: An error occurred while starting networking: a matching network card driver was not found in this image. Please have your Administrator add the network driver for this machine to the Windows PE image on the Windows Deployment Services server." Get 3 brews and die a little inside. I've downloaded all of the drivers from HP's site and from Intel's site. I trying to install Win7 x64 Enterprise. Grabbing new drivers and adding packages is a process with which I'm intimately familiar as I've been through it with a dozen different models of desktops and laptops but this issue is a first for me. My associate suggested trying the x86 drivers and I'm close enough to the end of my rope that I just might. gmonks, did you ever find success or did you go for a different approach? Thanks! Edited June 5, 2014 by jessee
Matty94 Posted June 27, 2014 Posted June 27, 2014 Has anyone had any success with trying to deploy an image with this? We have just got the HP Pro 600 G1, and trying to deploy an image to it but we are getting this error message PCI\VEN_8086&DEV_153A&SUBSYS_18E7103C&REV_04
HTCPCP Posted June 27, 2014 Posted June 27, 2014 One of my colleagues had a huge number of issues finding the right driver for the HP devices. Have you tried all of the drivers on one build? I know it can be a bit of a pain, but eventually it worked for him. @Matty94 that message is just telling you what the device is, Ven_8086 is Intel, and the Dev_153A is the Intel® Ethernet Connection I217-LM
jessee Posted June 27, 2014 Posted June 27, 2014 HTCPCP, I've tried every driver from both the HP and Intel sites. Matty94, still no luck but supposedly our sales rep has HP engineers on the job trying to find a solution for us.
gmonks Posted November 25, 2014 Author Posted November 25, 2014 After *a lot* of persistence with HP, they gave me the correct driver. You just have to be persistent.
Solvig Posted July 2, 2015 Posted July 2, 2015 Hi, please help me about: "Hp Pro 600 G1 Driver Problem - WDS" Our firm bought 20 new desktops "HP ProDesk 600 G1 DM". I prepared one of them (Windows 7 x64 Pro SP1) On one of our servers (WS2008R2) with the WDS-role I added new packets of network card driver in WDS, then injected new packets of the network card driver in boot\capture images x64. Drivers & Software - HP Support Center. [TABLE=width: 100%] [TR] [TD=class: label hpui-padding-right-20]Type:[/TD] [TD=colspan: 2]Network card driver[/TD] [/TR] [TR] [TD=class: label hpui-padding-right-20]Version:[/TD] [TD=colspan: 2]12.12.80.1920 Rev.A(6 January 2015)[/TD] [/TR] [TR=class: oslist] [TD=class: label hpui-padding-right-20, width: 30%]OS:[/TD] [TD=width: 70%, colspan: 2][TABLE=width: 100%] [TR] [TD]Microsoft Windows 7 Professional (64-bit)[/TD] [/TR] [/TABLE] [/TD] [/TR] [/TABLE] Now, when i am trying to capture image, i am getting the same error as you. Can you send me the link to the correct network card driver? "...gmonks, 25th November 2014, 03:03 PM, After *a lot* of persistence with HP, they gave me the correct driver. You just have to be persistent." Andrew Suray, sysadm JSC "Tatenergosbyt", Kazan, Rebublic of Tatarstan, Russia [email protected]
gmonks Posted July 2, 2015 Author Posted July 2, 2015 Hi, I no longer work for the company in which had this problem and as a result, I don't have the driver. If you ring HP though they will give you the correct driver. George
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now