+ Post New Thread
Page 1 of 2 12 LastLast
Results 1 to 15 of 22
Hardware Thread, Hp Pro 600 G1 Driver Problem - WDS in Technical; Hi, We have a problem here with a network card driver when trying to image via WDS . The machine ...
  1. #1
    gmonks's Avatar
    Join Date
    Oct 2012
    Location
    Bedfordshire
    Posts
    200
    Thank Post
    111
    Thanked 24 Times in 17 Posts
    Rep Power
    11

    Hp Pro 600 G1 Driver Problem - WDS

    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.

  2. #2
    cromertech's Avatar
    Join Date
    Dec 2007
    Location
    Cromer by the coast
    Posts
    731
    Thank Post
    177
    Thanked 109 Times in 97 Posts
    Rep Power
    54
    Which version of windows are you attempting to deploy with this. I had an enormous amount of trouble with some hp 655 laptops Frustration with LAN driver

    There are some tools that use can use with winpe image to see what drivers are loaded.

  3. #3
    gmonks's Avatar
    Join Date
    Oct 2012
    Location
    Bedfordshire
    Posts
    200
    Thank Post
    111
    Thanked 24 Times in 17 Posts
    Rep Power
    11
    Quote Originally Posted by cromertech View Post
    Which version of windows are you attempting to deploy with this. I had an enormous amount of trouble with some hp 655 laptops Frustration with LAN driver

    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.

  4. #4

    Join Date
    Nov 2009
    Location
    Manchester
    Posts
    1,069
    Thank Post
    6
    Thanked 208 Times in 188 Posts
    Rep Power
    53
    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).

  5. #5
    gmonks's Avatar
    Join Date
    Oct 2012
    Location
    Bedfordshire
    Posts
    200
    Thank Post
    111
    Thanked 24 Times in 17 Posts
    Rep Power
    11
    Quote Originally Posted by Achandler View Post
    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.

  6. #6

    Join Date
    Nov 2009
    Location
    Manchester
    Posts
    1,069
    Thank Post
    6
    Thanked 208 Times in 188 Posts
    Rep Power
    53
    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?

  7. #7
    gmonks's Avatar
    Join Date
    Oct 2012
    Location
    Bedfordshire
    Posts
    200
    Thank Post
    111
    Thanked 24 Times in 17 Posts
    Rep Power
    11
    Quote Originally Posted by Achandler View Post
    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&115 83659&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&115 83659&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&115 83659&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&115 83659&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&115 83659&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&115 83659&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]




  8. #8

    Join Date
    Nov 2009
    Location
    Manchester
    Posts
    1,069
    Thank Post
    6
    Thanked 208 Times in 188 Posts
    Rep Power
    53
    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.

  9. #9
    gmonks's Avatar
    Join Date
    Oct 2012
    Location
    Bedfordshire
    Posts
    200
    Thank Post
    111
    Thanked 24 Times in 17 Posts
    Rep Power
    11
    Quote Originally Posted by Achandler View Post
    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....?

  10. #10

    Join Date
    Nov 2009
    Location
    Manchester
    Posts
    1,069
    Thank Post
    6
    Thanked 208 Times in 188 Posts
    Rep Power
    53
    So the IP Config /all still shows no network cards? Or does it show you one without an IP?

  11. #11
    gmonks's Avatar
    Join Date
    Oct 2012
    Location
    Bedfordshire
    Posts
    200
    Thank Post
    111
    Thanked 24 Times in 17 Posts
    Rep Power
    11
    Quote Originally Posted by Achandler View Post
    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"

  12. #12

    Join Date
    Nov 2009
    Location
    Manchester
    Posts
    1,069
    Thank Post
    6
    Thanked 208 Times in 188 Posts
    Rep Power
    53
    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.

  13. #13
    gmonks's Avatar
    Join Date
    Oct 2012
    Location
    Bedfordshire
    Posts
    200
    Thank Post
    111
    Thanked 24 Times in 17 Posts
    Rep Power
    11
    Quote Originally Posted by Achandler View Post
    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.

  14. #14

    Join Date
    Nov 2009
    Location
    Manchester
    Posts
    1,069
    Thank Post
    6
    Thanked 208 Times in 188 Posts
    Rep Power
    53
    https://communities.intel.com/thread/43218

    Seems a common problem, people seem to have a solution for it.

  15. #15
    gmonks's Avatar
    Join Date
    Oct 2012
    Location
    Bedfordshire
    Posts
    200
    Thank Post
    111
    Thanked 24 Times in 17 Posts
    Rep Power
    11
    Quote Originally Posted by Achandler View Post
    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.

SHARE:
+ Post New Thread
Page 1 of 2 12 LastLast

Similar Threads

  1. OfficeJet Pro K5400 32bit drivers installation problem
    By localzuk in forum Windows Server 2008 R2
    Replies: 2
    Last Post: 27th November 2012, 12:57 PM
  2. Replies: 0
    Last Post: 9th March 2012, 03:07 PM
  3. [Fog] Problem with HP Pro 3015MT
    By freaky_seb in forum O/S Deployment
    Replies: 10
    Last Post: 8th June 2010, 04:27 PM
  4. Driver problems on a HP 530 Laptop
    By Neville in forum Windows
    Replies: 1
    Last Post: 13th May 2008, 05:28 PM
  5. HP inkjet/deskjet network printing problems
    By ajbritton in forum Windows
    Replies: 1
    Last Post: 16th December 2005, 08:28 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •