Windows Deployment Services

Hi Guys,

I have the following issues.

Created a VMware machine with sufficient specs for Server 2012 R2.  Loaded server 2012 R2, joined it to the domain and installed WDS role.  (DHCP, DNS etc all running on a separate server on the domain.

I then configured my WDS server role server and loaded my default Win7Pro install.wim image under install images.  Then added a default win7 boot.wim image under boot images.  Created a second default win7 boot2.wim image under boot images.  Then proceeded to create a capture image from boot2.wim

Then on a fully configured machine I ran sysprep and shut it down once completed.  Then booted it back up and did a PXE boot.  When boot images appeared I used the capture image I created under boot images.  Select volume to be captured and wait for capturing to complete, automatically uploading the captured .wim image to install images.  Part One done.... successfully captured an image from a preconfigured machine.

Part two:  Installing the captured image on a clean machine.
Enable PXE boot on unconfigured machine and select boot image to boot from.  Client machine complains about network drivers.  Go back to boot images and inject required network drivers into boot2.wim.  On client I again do a PXE boot this time selecting boot2.wim that contains the network drivers.  Now client boots further but again gets an error.  This time different and complaining about not finding the DHCP server.  From here I have followed all the suggestions that are currently on the net but with no luck at all.  I thought that it might have something to do with the fact that it was a virtual machine and then replicated the entire server build on a physical server.  Here I experienced the exact same issues and error.  I then separated the server from my current network and setup my own test domain with AD, DNS DHCP and WDS roles.  My client machines do get ip addresses from my server as tested when plugging in a preinstalled windows machine and by checking the leases in the DHCP console.  But for the life of me no machine I try to deploy an image on can I get to successfully install.  All just complain about DHCP issues but DHCP is definitely working.

Can anyone please assist me in regards to getting this issues sorted out, I have been busy with this for four days with no luck.

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.

Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization ConsultantCommented:
at which stage does it not obtain a DHCP IP Address?

and if you create a standard Windows install, and set to DHCP, do you get an IP Address ?
iamdieterAuthor Commented:
Hi there friend,

Not sure I understand what you are asking.  So what I said was that I know the DHCP server is working as any machine I connect to this isolated network gets an IP and the lease is visible in the DHCP console.  However, when I do a PXE boot for a blank machine and after I have selected which boot image to use it then just stops and complains about not finding a DHCP server.  When I then open a cmd prompt with shift+f10 and do a ipconfig there is nothing.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization ConsultantCommented:
and it has the network interface driver installed ?

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
Ensure Business Longevity with As-A-Service

Using the as-a-service approach for your business model allows you to grow your revenue stream with new practice areas, without forcing you to part ways with existing clients just because they don’t fit the mold of your new service offerings.

aravind ancheWindows/Vmware Commented:

Try adding network drivers in out of box drivers and create selection profile.
We do that in MDT.
Can you try with USB, check that
if you can image the PC with USB then it might be with  DNS DHCP.
If not it is something with the image.
iamdieterAuthor Commented:
I ended up having to install 3rd party LAN drivers directly from Realtek and the issue went away and it successfully booted from my boot image.  However I now have another issue as per my new post.
iamdieterAuthor Commented:
Thanks for the assistance.
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

From novice to tech pro — start learning today.