• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1624
  • 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 SinghDesktop Applications SpecialistCommented:
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
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
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
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

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