When booting into the WinPE-based boot environment and starting the virtual machine virtualized on the ESXi target host, the NIC is not recognized

Summary

When virtualizing a virtual machine with AIP2018 or another Actiphy product, a NIC device is created for VMXNET3. Consequently, when booting the virtualized machine in the (WinPE-based) boot environment, the NIC is not recognized. This issue arises when the driver for VMXNET3 is not embedded in WinPE.  

Workaround

Please try one of the following workarounds:

1) Ensure the VMXNET3 driver is included in the boot environment. Build the WinPE boot environment in Windows on the ESXi virtual machine, and add VMXNET3 during the boot environment creation.
http://webhelp.netjapan.com/AIP/Windows/2018/en/help/Utility_tools/BE_Builder_WinPE.htm

2) In VM Settings, switch the network adapter's adapter type to "E1000(e)." The NIC can be recognized in WinPE by changing the NIC device to "E1000(e)" with Plug and Play. 

3) Boot the CentOS-based boot environment. The NIC can be recognized because the driver for VMXNET3 is embedded in the CentOS-based boot environment. 

Target Product

– ActiveImage Protector 2018

(13451131539481)