WDS capture

When booting from a WDS capture image for server 2012 R2, the screen goes blank after the inital stage. It seems to be due to the additonal drivers loaded. It happens with both E1000 and VMNETX3 drivers. The driver is working in Windows PE (during FTP boot  phase). Without additional drivers, there is no issue but there is also no network connection after the initial WindowsPE phase. Ideas?
LVL 3
albatros99Asked:
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.

Nagendra Pratap SinghDesktop Applications SpecialistCommented:
Model of machine being captured?

Also why not use MDT and a VM to capture?
James HaywoodCommented:
Have you injected the VMware network drivers to the capture image?
albatros99Author Commented:
I'm capturing a VM with WDS. The underlying host is ESX5U3. If the 3rd party driver is added to the capture image, the screen goes blank after the initial TFTP boot phase.
Get Blueprints for Increased Customer Retention

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

James HaywoodCommented:
What version of vsphere?
compdigit44Commented:
What hardware version is you VM running on hardware version 7? What video drive are you using? If you are using WDDM try to remove if and replace it with a generic video driver as a test
albatros99Author Commented:
It's hardware version 8 with a generic driver.
compdigit44Commented:
Lets try the following test.
1) Boot the VM into Windows and uninstall VMtools
2) Power down the VM and change the NIC to either vlance or flexible
3) On the VM go into Device manager and make sure the nic is listed.
4) Try to run WDS again.
albatros99Author Commented:
The VM can't be booted into Windows. It's a WDS capture image so it loads WindowsPE and the it's supposed to show the capture GUI. It works well with an E1000 network card but does not work with the VMXNET3 card. The only difference is that with the VMXNET3 driver you have to inject the driver into the WDS capture image.
compdigit44Commented:
I have read a couple of articles on line stating other have had issue using WDS with a VMware Vm and recommend not using VMXNEt3 but using E1000...

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1009104

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
James HaywoodCommented:
Is this working with a boot.wim/capture.wim from another OS? You should be able to capture using a 2k8r2 .wim.
albatros99Author Commented:
It's probably some sort of incompatiblity between VMWARE 5.0 and WDS 2012 R2. I'm using E1000 as a workaround.
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
VMware

From novice to tech pro — start learning today.