WdsClient: There was a problem initializing WDS Mode

Hi I am in need of any suggestions to fix an issue with WDS. Config: Server 2012R2 HyperV host, Server 2012R2 VM with AD, DNS, WSUS, WDS, DHCP installed. The server and the client are on an internal virtual switch (testing network). Generation 1 and Generation 2 VM's set up to test imaging. Boot wims created from a windows 8.1 DVD. Option 60 and 67 are configured in DHCP (67: set to boot\x64\wdsnbp.com). When I try and image a VM I get the following error after it loads the discovery wim WdsClient: There was a problem initializing WDS Mode. Any suggestions welcome as I am stumped. Thanks in advance
Dead_EyesAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
As I recall, when WDS and DHCP are hosted on the same server, you *don't* want to set options 60 or 67 in DHCP, or it causes conflicts. That'll cause WDS to not behave properly.
0
Dead_EyesAuthor Commented:
thanks for the reply but Its the other way round, it restates this in the WDS options
0
Cliff GaliherCommented:
Try not setting the options, and make sire both cheekbones are checked in the PXE response tab. If that doesn't work, go ahead and set option 60. Setting option 67 though will almost definitely make WDS misbehave. You'd only want to do that in special circumstances.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Dead_EyesAuthor Commented:
I have tried option 60 and it behaves as expected and cannot find the PXE boot. 67 just specifies PXE boot file so is very useful for switching between CSM & UEFI boot loaders.
0
Cliff GaliherCommented:
Regarding option 67, it is supposed to be WDS server that sends that information based on settings you choose in the WDS tabs.  If you set it via DHCP instead of letting WDS then WDS can't manage its response and you get errors.
0
Dead_EyesAuthor Commented:
True but I get the same response with option 67 on or off
0
vivigattCommented:
Regarding DHCP options 60 and 66, 67, these are explained in my article (and its comments):
http://www.experts-exchange.com/Networking/Misc/A_2978-PXEClient-what-is-it-for-Can-I-use-PXE-without-it.html

Basically, DHCP Opt60 is to be set ONLY if your PXE server and DHCP server runs on the same host.
DHCP Opt66 and 67 should NEVER be set if you have a real PXE Server in place. This would prevent the PXE Server (WDS embeds one, of course) to send different PXE-Bootstraps for different architectures, for instance (x86 vs x64 etc.)

However, you do not seem to have a PXE problem, since the PXE portion of the boot process works and you are having your error when under the WinPE environment.
Unless you are getting a PXE-Boot and then a WinPE/WIM boot from a wrong WDS server... Better  check that before making any other assumptions.
0
Dead_EyesAuthor Commented:
I agree its got nothing to do with PXE and I have redone the boot wims and re-installed and still getting the same error
0
vivigattCommented:
I did not say that it had nothing to do with PXE for sure.
It COULD be a PXE6based problem if you got the wrong PXE bootstrap because you specified DHCP opt 66 and 67 and that would prevent the PXE server to send the correct bootstrap.
You should make sure that it is not the case.
You can use a packet analyzer (Network Monitor, Wireshark) to examine what is happening on the wire, check logs etc.
In any case, you must remove DHCP option 66 and 67, they are useless and dangerous when there is a real PXE server in charge of sending PXE details.
0
Dead_EyesAuthor Commented:
I found the problem, for anyone else experiencing similar it occurs when you install WDS on a fully updated VM running Server 2012R2. The solution is to install the WDS component before updating the server. Wish I could say why but after several rebuild tests it holds true every time (I think the culprit update is the big 600-800MB one you usually find on the second round of updates). Oh and as a bonus fail if you are installing WSUS on the same server update the server before installing WSUS or that can encounter issues. I will leave this open for the next few days if anyone can shed any further light on the issue and serve to assist those that really don't want to rebuild the server but in my tests it was only way and held true in 3 separate tests on different host machines, different install disks and different domains.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Dead_EyesAuthor Commented:
Possible fault in Server 2012R2, No other solutions posted
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.