+ Post New Thread
Results 1 to 10 of 10
O/S Deployment Thread, WDS wdsclient error in Technical; I've got the familiar error when trying to install an image from our Server 2012 WDS onto a new PC ...
  1. #1
    Sheridan's Avatar
    Join Date
    Oct 2010
    Posts
    1,289
    Thank Post
    112
    Thanked 86 Times in 58 Posts
    Rep Power
    28

    WDS wdsclient error

    I've got the familiar error when trying to install an image from our Server 2012 WDS onto a new PC - wdsclient: an error occured while obtaining an ip address

    Problem is I've rebuilt the boot image with the drivers (realtek) injected into it so I'm now stuck - its definitely the right set of drivers but no joy.

    Is there anything else that causes this or should I give up now and install from dvd instead!

    Edit: I've just realised its probably the uefi bios, even set to legacy I've never ever got a uefi bios to work with wds, even on our newer 2012 version! Either that or zoostorm PCs just don't work with WDS.
    Last edited by Sheridan; 18th March 2014 at 01:43 PM.

  2. #2
    Sam_Brown's Avatar
    Join Date
    Sep 2009
    Location
    Northampton
    Posts
    533
    Thank Post
    89
    Thanked 30 Times in 28 Posts
    Rep Power
    16
    You should be able to do a Shift+F10 to bring up the console. Can you do an IPCONFIG at all to see if it's actually picked up the network card and you've gotten an IP Address or not.

    Then try Notepad.exe x:\Windows\INF\setupapi.app.log and see if it's moaning about drivers etc. Although I appreciate you've said you have the drivers added every time I've seen this issue it's been a drive issue.

  3. Thanks to Sam_Brown from:

    Sheridan (18th March 2014)

  4. #3
    Sheridan's Avatar
    Join Date
    Oct 2010
    Posts
    1,289
    Thank Post
    112
    Thanked 86 Times in 58 Posts
    Rep Power
    28
    I do get an error in there relating to VEN=10EC DEV=8168 which is the Realtek 8168 that is onboard. I've copied over about 5 different versions of those drivers!

    Always the same error though: Loading Module "x:\windows\system32\wwaninst.dll" failed. The specified module could not be found

    Every other PC we try is working fine - whatever zoostorm have put is this doesn't like wds.

  5. #4
    Sam_Brown's Avatar
    Join Date
    Sep 2009
    Location
    Northampton
    Posts
    533
    Thank Post
    89
    Thanked 30 Times in 28 Posts
    Rep Power
    16
    I know it's frustrating. I've had similar issues in the past. Are you using the Vista version of the drivers? I usually have better luck with them than Windows 7 because Windows PE is based on Vista.

    Also how are you added the drivers to the image out of curiosity? That might also be the issue.
    Last edited by Sam_Brown; 18th March 2014 at 02:06 PM.

  6. #5
    Sheridan's Avatar
    Join Date
    Oct 2010
    Posts
    1,289
    Thank Post
    112
    Thanked 86 Times in 58 Posts
    Rep Power
    28
    I've added the drivers using the old dism commands, and also through the WDS gui (from driver packages)

    I've even created a new empty boot.wim and added only the single driver required!

  7. #6
    Sheridan's Avatar
    Join Date
    Oct 2010
    Posts
    1,289
    Thank Post
    112
    Thanked 86 Times in 58 Posts
    Rep Power
    28
    Ha! Created a new blank 64 bit boot image from the DVD, and then added only 1 single driver - the 64bit version (the oldest one!) of the realtek driver and its worked! So adding the later versions kills it so there must be some kind of driver conflict with this set of drivers. Very odd and not UEFI's fault at all this time

  8. #7
    Sam_Brown's Avatar
    Join Date
    Sep 2009
    Location
    Northampton
    Posts
    533
    Thank Post
    89
    Thanked 30 Times in 28 Posts
    Rep Power
    16
    Rings a bell. I've had similar issues in the past. Glad you got it working

  9. #8
    Sheridan's Avatar
    Join Date
    Oct 2010
    Posts
    1,289
    Thank Post
    112
    Thanked 86 Times in 58 Posts
    Rep Power
    28
    Even if I have to have a seperate, single boot image just for these PCs I can suffer that.

  10. Thanks to Sheridan from:

    Sam_Brown (18th March 2014)

  11. #9
    Sam_Brown's Avatar
    Join Date
    Sep 2009
    Location
    Northampton
    Posts
    533
    Thank Post
    89
    Thanked 30 Times in 28 Posts
    Rep Power
    16
    I remember a similar issue with drivers for our older Dell Machines where we had to have a separate boot image because the standard USB Drivers were "too new". We had to force it to use drivers from about 6 years ago for KB+M to work lol.

  12. #10
    Sheridan's Avatar
    Join Date
    Oct 2010
    Posts
    1,289
    Thank Post
    112
    Thanked 86 Times in 58 Posts
    Rep Power
    28
    WDS is great, but frustrating when it goes wrong! Especially when mixed with uefi - I've got this one switched to legacy for everything to make this work!

SHARE:
+ Post New Thread

Similar Threads

  1. SCCM WDS Service Error
    By ptotham in forum O/S Deployment
    Replies: 1
    Last Post: 23rd November 2011, 09:19 PM
  2. [WDS] WDS Deployment Error
    By achesterman in forum O/S Deployment
    Replies: 3
    Last Post: 1st September 2011, 11:34 AM
  3. [WDS] WDS & DHCP Error! Help was working yesterday!
    By jamin100 in forum O/S Deployment
    Replies: 19
    Last Post: 17th June 2011, 11:31 AM
  4. Windows Deployment Services (WDS) Image Error
    By adamchapman in forum How do you do....it?
    Replies: 1
    Last Post: 3rd September 2009, 09:59 AM
  5. Replies: 0
    Last Post: 10th October 2008, 12:10 PM

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
  •