VMware Communities
N74jrw
Enthusiast
Enthusiast
Jump to solution

Configure vNIC to use vmxnet3 driver

Guest: Windows 10 Enterprise 1803 x64

Host: Windows 10 Enterprise 1607 x64 & VMware Workstation 14.

I cannot execute a sysprep and capture task sequence for MDT because sysprep strips out the NIC driver during its process. Brilliant, BTW... Online suggestions advise to convert the e1000 vNIC to vmxnet3. How does one do this? I can find nothing that actually says how to do so in VMware Workstation. Sure, for vSphere, or VA, but not Workstation. I did try editing the VMX file with the line:

ethernet0.virtualDev = "e1000e"

to read

ethernet0.virtualDev = "vmxnet3"

...but this did nothing. I've tried both with VMware Tools installed and uninstalled. I did not have these problems capturing 1607. Anything else I can try?

Thank you

Reply
0 Kudos
1 Solution

Accepted Solutions
yanw
VMware Employee
VMware Employee
Jump to solution

1) Power off your VM

2) Make sure there is not any .lck file in your VM's file folder

3) Open .vmx file and chang ethernet0.virtualDev = "vmxnet3", save it

4) Power on the VM

Note that vmtools is required for vmxnet3 driver.

View solution in original post

Reply
0 Kudos
2 Replies
yanw
VMware Employee
VMware Employee
Jump to solution

1) Power off your VM

2) Make sure there is not any .lck file in your VM's file folder

3) Open .vmx file and chang ethernet0.virtualDev = "vmxnet3", save it

4) Power on the VM

Note that vmtools is required for vmxnet3 driver.

Reply
0 Kudos
N74jrw
Enthusiast
Enthusiast
Jump to solution

Thanks!

Sysprep still removed the NIC driver during the capture process. Brilliant!

Reply
0 Kudos