WDS WinPE Boot

Hello - I am trying to get started with WDS in deploying Windows 7. This is a pilot project, that if it works, will go live. I can get the client to PXE boot to the WDS server, but cannot connect to the WDS server. The WinPE environment being used does not have the drivers for the client's NIC. Despite using DRVLOAD to add the exact drivers to the WinPE session, I still can't get a working network stack on my WinPE session. Is there a way to inject the drivers into WinPE before starting a capture session? This way, I can add all of the drivers and not have to try each one, sequentially, during the WinPE session. WDS is running on Windows Server 2012 R2.

Thanks
LVL 27
Jason WatkinsIT Project LeaderAsked:
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.

footechCommented:
Have you tried adding the driver package on the WDS, then add the driver package to the boot image (all done through the WDS console)?
0
Jason WatkinsIT Project LeaderAuthor Commented:
I would like to do that, but am unsure of exactly how to do so. My text, the Windows 7 Resource Kit, doesn't cover this...
0
footechCommented:
The built-in help for WDS has good information on Managing Driver Packages (more than I can include here), so I suggest to read that.  The process really can be as simple as extracting the driver files, adding the driver package on the WDS, and then adding the driver package to the boot image - all with a few button clicks.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Jason WatkinsIT Project LeaderAuthor Commented:
I added the drivers, all of them, for the target PC and now I cannot even boot into the PXE environment. Another, separate, driver error occurs and the process halts. My guess is that one of the added driver overwrote a system drive for Windows PE. Though, I cannot determine which one that is, exactly...
0
footechCommented:
Hard to say what might have broken.  Sounds like you might have incompatible drivers.  You mentioned that the NIC wasn't working so I would have started by just adding that.  This link discusses the scenarios for deploying packages
http://technet.microsoft.com/en-us/library/dd348456%28v=ws.10%29.aspx


What drivers did you add?
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
Jason WatkinsIT Project LeaderAuthor Commented:
It was driver-related. Sorry for the delay on my part for awarding points.
0
footechCommented:
Not a problem.  Glad you got it sorted.
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.