• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1556
  • Last Modified:

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?
0
albatros99
Asked:
albatros99
  • 4
  • 3
  • 3
  • +1
1 Solution
 
Nagendra Pratap SinghCommented:
Model of machine being captured?

Also why not use MDT and a VM to capture?
0
 
James HaywoodCommented:
Have you injected the VMware network drivers to the capture image?
0
 
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.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

  • 4
  • 3
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now