WDS Client : Unable to Obtain IP

[Darylrese]

Morning all,

 

Before I throw this PC out the window, anyone know what's going on here?

 

Got a brand new PC and trying to install a WDS image of Windows 7 onto it but keeps coming up with this error

 

 

I have injected all the drivers into the boot.wim including all NIC drivers for that PC from HP's website. All other PC's and laptops are imaging fine so it's not a problem with the deployment or images themselves.

 

I have checked device manager to see what driver is currently installed and working on the PC's standard Windows 10 build and it matches the drivers i injected into the boot

 

Many thanks

Edited May 23, 2016 by Darylrese

[KibosJ]

Morning all,

 

Before I throw this PC out the window, anyone know what's going on here?

 

Got a brand new PC and trying to install a WDS image of Windows 7 onto it but keeps coming up with this error

 

[ATTACH=CONFIG]36944[/ATTACH]

 

I have injected all the drivers into the boot.wim including all NIC drivers for that PC from HP's website. All other PC's and laptops are imaging fine so it's not a problem with the deployment or images themselves.

 

I have checked device manager to see what driver is currently installed and working on the PC's standard Windows 10 build and it matches the drivers i injected into the boot

 

Many thanks

 

I had this issue with a Toshiba laptop and it was driver related unfortunately. I downloaded the driver from Toshiba's website and injected it and got this error. I tried to find a working driver but never could, however Windows 10 had the driver built-in so I just changed my boot images to Windows 10 ones and loaded windows 7 from there

[sted]

that looks like youre booting a wim from windows vista id try using one from at least 7 prefereably 8.1/10 it might be a chipset thing i had some laptops on friday with win7 i couldnt get the nic working (or the touchpad/usb/pretty much anything). If its a new laptop with an intel skylake chipset you as far as i can tell have to use win10

[Darylrese]

sorry, i found that screenshot on google images as i couldnt be bothered to take a screenshot and upload myself The boot.wim is Windows 7 Enterprise x64

 

Yes its Skylake, HP ProDesk 400 G3 SFF. i5-6500, 4GB Memory, 128GB SSD

Edited May 23, 2016 by Darylrese

[KibosJ]

sorry, i found that screenshot on google images as i couldnt be bothered to take a screenshot and upload myself The boot.wim is Windows 7 Enterprise x64

 

Yes its Skylake, HP ProDesk 400 G3 SFF. i5-6500, 4GB Memory, 128GB SSD

 

I agree with Sted, change your boot.wim to a windows 10 one and then install your 7 Image from that

[FN-GM]

Add the Nic driver to your boot image, should be ok then.

[sted]

sorry, i found that screenshot on google images as i couldnt be bothered to take a screenshot and upload myself The boot.wim is Windows 7 Enterprise x64

 

Yes its Skylake, HP ProDesk 400 G3 SFF. i5-6500, 4GB Memory, 128GB SSD

 

then its time to plan windows 10 systems or send the laptops back unfortunately as far as i can tell intel only support that chipset on windows 10 so even if you get the nic working thats will be about it no vidfeo drivers/usb/ touchpad etc

[Darylrese]

Already done that, no joy.

[sted]

Add the Nic driver to your boot image, should be ok then.

 

with skylake it wont work i had one in windows 7 propper not pe and the driver was instaled but because of preumably the chipset it diddnt work (had ! next to it with the right name etc) about the only driver i managed to install was the card reader

[Darylrese]

Ah man. Can you build a Windows 10 Boot.wim and deploy Windows 7 image within it?

[sted]

Ah man. Can you build a Windows 10 Boot.wim and deploy Windows 7 image within it?

 

yes but it wont help you you will get the image deployed but not be able to install pretty much any drivers once its booted from my experience (i used mdt with a win10 boot image windows 7 installed fine but i couldnt get any drivers to install on 7 and basically nothing worked)

[superaz300]

I agree with these posts, it is most likely a driver issue. However, I would try the following.

1. Have you tried another laptop or computer to get it to reinstall Windows?

2. Have you restarted the DHCP service?

3. Has the DHCP scope used all its available addresses?

4. Can you reauthorize WDS?

 

Depending on the boot image you have chosen, if it is a Windows 7 x32 boot image, you will need to inject a 32bit NIC driver for it to be able to install the OS. However if it is a 64bit boot image, then you will need a 64 bit driver.

 

Hope this helps.

James

[Darylrese]

1) Yes all other devices build fine

2) Yes all up and running

3) Yes and works for all hardware except this new PC

4) I have both x32 and x64 drivers, no luck.

 

I might just buy a PCI-E NIC and build it with that in. Once its up and running remove it and install network driver. Bit of a pain especially if we were to roll these out across the site.

[Darylrese]

I have created a Windows 10 boot.wim, booted from that and its working. Its just installing Windows 7 x64 now but i expect it wont work as above.

[CavLiv]

I get this message with one of our computers in our computer suite. I leave that computer to the end, when I plug in a network cable to one of the other computers. When the image is transferred, I then plug back in the original cable to activate and deploy anti-virus.

[Darylrese]

Still no luck with this. Its making a lovely expensive paperweight in my office at the moment.

 

I have injected all Windows 7 drivers for the PC from Hp's website and the RealTek website. They only work in conjunction with a Windows 10 boot image but we aren't running Windows 7 at the moment.

[dapaulio]

If you have a 64 bit server and 32 bit image then you would need 64 bit and 32 bit drivers for you nic in the WDS drivers and the 64 bit driver injected in to the boot image.

 

Have you tried downloading the driver from the nic vendor eg realtek, rather than from the manufacturer website eg hp

 

Have you tried an older version of the driver?

 

Fail all that get a USB gigabit network adapter that support pxe (or a non pxe usb nic but you would have to create a usb discovery image) and use that for the persistently troublesome computers. In my experience very few are troublesome and have always managed to find a driver that works before resorting to using a USB nic.

[Darylrese]

I don't have a 32bit image, it's a 64bit boot image and a 64 bit Windows 7 image.

 

Yes I've tried downloading drivers from HP, Realtek and other sites.

 

My next idea was a USB or add in card network adaptor and see what happens but that's not practical if we are going to buy them in bulk

[dapaulio]

I have some prodesk 400 g3 myself. I will see what driver I have on my WDS server tomorrow.

[Darylrese]

Excellent thank you very much

[dapaulio]

as promised here is the driver that i have extracted from my WDS. the rar has both x86 and x64 drivers. we run a slightly different configuration. we run a 64 bit server with a 32 bit image but these group of drivers works,

 

https://www.dropbox.com/s/3q5b70m4nulusl1/400g3nic.rar?dl=0

 

Goodluck

[Darylrese]

Thank-you very much, that's very kind of you!

 

This looks like the exact driver i have injected already, however i just added it anyway but unfortunately its still coming up with the same error

 

I'd say its 100% the correct driver too.

 

Basically, i am adding the driver package using the Windows Deployment Services Snap in, then right clicking on the boot image and adding drivers to that. It seems to have done the trick for USB 3.0 drivers, display drivers etc its just the network adaptor thats having the issues. Are your HP ProDesk 400's the i5 6500 model?

 

Many thanks again

[Burconix_Greg]

If you want to prove the network driver hasn’t initialised properly, at the prompt cant get IP, instead of clicking ok, leave the message on screen.

 

Press Shift-F10, this will bring up a command prompt window (sometimes you have to alt tab if the cmd.exe window loads behind the prompt).

 

ipconfig, and it will presumably be blank...

 

At the prompt:

wpeutil InitializeNetwork

 

This take a few moments, but will then force the driver store to reload and search for a driver for the hardware installed.

 

If after that, ipconfig still shows blank, the correct driver defiantly isn’t in the boot.wim...

 

If it comes up with an IP at this stage, there is a timing issue with the machine getting an IP Address from DHCP… that could be something else.

 

From what you have set it most probably is driver related...

 

Note for network drivers, you not only have to add them to WDS Drivers, but you also have to manually then add them to the boot image (right click, add driver on the boot.wim under Boot Images after adding to Drivers) - this is an additional step just for network/sata drivers. I would recommend you take a backup of your boot.wim by right click Export before adding boot drivers, as you can get conflicts.

 

If it is driver related, and the above hasn’t helped, to diagnose further, when you have the driver installed and working in windows, if you go to Device Manager, right click the installed adaptor, properties, details and select Hardware IDs take down the top ID, and then search the content of your driver .inf file you have imported to make sure the ID matches - if it does not match, the driver is not correct for the hardware.

 

Also note you need the x86 driver in the boot.wim (if your boot.wim is x86), if you are using the x86 boot.wim to install an x64 install image. The boot/format/filecopy part is x86 until after the first boot. If your boot.wim is x64 naturally it’s only the x64 driver you will need to add to the boot image.

 

Hope this helps,

Greg

[Darylrese]

Thank-you.

 

It said the command was successful but still has no address or network adaptor listed when performing ipconfig

 

Its a x64 boot image and x64 Windows image. I have added the drivers to the driver packages, thern right clicked on boot.wim and add driver packages to it.

 

Still no luck.

 

Worth mentioning again, it works fine with a Windows 10 boot image and builds but gets stuck in a loop when performing the OOBE stage.

[Burconix_Greg]

In which case, it does sound like the driver, does the HardwareID (gathered in windows device manager) matches the x64 inf file you have imported into the boot.wim?

 

For example in device manager you get:

PCI\VEN_8086&DEV_08B1&SUBSYS_C4708086&REV_6B

 

Then you would expect to see this string in the inf file in the driver folder (if you open the .INF in notepad and search for it).