Monday, July 15, 2013

WdsClient: There was a problem initializing WDS Mode

Tonight I wanted to deploy a bunch of Windows Servers from a customised WIM file for my home lab environment running on VMware Workstation - need to test something for a customer tomorrow :).  In minutes I had built a new WDS server with DHCP and PXE boot services, however when I went to boot my first VMware machine from my WDS server, the PXE boot went through fine however I ran into the following error.

WdsClient: There was a problem initializing WDS Mode


After a good 10 minutes trying to figure out what was going on I ran services.msc on my host physical Laptop.  The darn VMware DHCP Service was running!


The virtual machine was booting of the WDS DHCP Server after booting it went to obtain a second IP address which was the VMware DHCP Service!  Ahg!
Posted by at
Labels: ,

18 comments:

  1. AnonymousAugust 30, 2013 at 1:43 AM

    Thank you :)
    Just ran into the same problem.

    ReplyDelete
  2. AnonymousOctober 1, 2013 at 9:06 AM

    I got the same problem using VMware. I have it working after disabling the VMware DHCP Service. Thanks Clint, it really helps.....

    ReplyDelete
  3. AndyDecember 2, 2013 at 12:39 AM

    Very clever! Your finding in this article was a lifesaver.

    I never would have considered checking or known that the "VMware Workstation" host (for me I use "VMware Fusion" as I have a Mac) has its own VMware DHCP Service running in the background thus changing the IP address info a second time for the guest VM (or the WDS client). Thank you so much Clint! :)

    ReplyDelete
  4. UnknownFebruary 20, 2014 at 8:21 PM

    This comment has been removed by the author.

    ReplyDelete
  5. AaronMarch 8, 2014 at 1:43 PM

    thanx man

    ReplyDelete
  6. AnonymousSeptember 2, 2014 at 7:12 AM

    Wow! It is resolved in my case too. Thanks a ton :)

    ReplyDelete
  7. UnknownSeptember 30, 2014 at 7:34 PM

    Wow! It is resolved in my case too. Thanks a ton :)

    ReplyDelete
  8. AnonymousOctober 10, 2014 at 9:48 AM

    Just want to add one more thanks to the list. It was driving me batty!

    ReplyDelete
  9. JatinOctober 26, 2014 at 11:29 AM

    thanks a LOT. got same error and best first shot answer.

    ReplyDelete
  10. AnonymousDecember 23, 2014 at 10:15 PM

    Thanks Dear, Thank You very much. God Bless you.

    ReplyDelete
  11. AnonymousMarch 17, 2015 at 7:09 AM

    Thanks !

    ReplyDelete
  12. AnonymousMarch 23, 2015 at 1:45 AM

    Thanks for the tip Clint

    ReplyDelete
  13. Gul nawazApril 21, 2015 at 12:59 AM

    thanks dear its working....after stop my VMWare DHCP service......Good Bless you...

    ReplyDelete
  14. UnknownMay 2, 2015 at 2:02 PM

    Thank you. Save me a lot of time !!.

    ReplyDelete
  15. UnknownSeptember 15, 2015 at 1:51 PM

    Thanks a lot... It resolved my query .. thumbs up for you

    ReplyDelete
  16. UnknownSeptember 17, 2015 at 11:13 PM

    Thank you so much for posting this. Solved an issue that I have had for quite some time now.

    ReplyDelete
  17. AnonymousFebruary 10, 2016 at 12:06 AM

    Good to help us ,,,but i want to know why this error happen while i have choose that my vm pxe client use hosted only network so is this doesn't mean that there is an internal network??

    ReplyDelete
  18. ShiblyJune 27, 2016 at 7:04 AM

    That's great help

    ReplyDelete

Subscribe to: Post Comments (Atom)