After capturing the virtual disk of Virtual Machines (VMs) installed with Windows 2008 R2 or Windows 7 that is configured with the VMXNET3 virtual network device, the following issues might occur: • The guest operating system of the resulting VM shows the Ethernet network interface as: VMXNET Device #2 in Device Manager Local Area connection #2 in Network Properties • The old Ethernet network interface remains in Device Manager when Show Hidden Devices is enabled. • The old Ethernet network interface retains it's network configuration, preventing the new interfaces from reusing the previous static IP addresses. These changes in the network interface entries in the Device Manager and network configuration modify the network stack of the virtual disk. This causes a Blue Screen Stop Error 7B when booting any Target Device, other than the Master Target Device. Rather than just add the driver separately, it might help to just install the VMWARE Tools. It will install the driver and a few other useful drivers for you. I am preparing a Windows 10 image for our company and ran into this problem. Installing VMWare Tools fixed it for me. ![]() Vmxnet3 Driver Windows 10Uninstall the Provisioning Services software from the Target Device before installing the Microsoft hotfix. After installing the Microsoft hotfix and reinstalling the Target Device client software, complete the following: • For Windows 2008 R2 or Windows 7 versions prior to Service Pack 1, install the hotfix described in the Microsoft Knowledge Base article before deploying the virtual disk. • For Windows 2008 R2 or Windows 7 versions post Service Pack 1, install the hotfix described in the Microsoft Knowledge Base article before deploying the virtual disk. • For Windows Vista and Windows 2008, install the hotfix described in the Microsoft Knowledge Base article before deploying the virtual disk. Install Vmxnet3 Driver Windows 7Workaround 1 Before converting a VM to a template, remove references to the Peripheral Component Interconnect (PCI) Express virtual network interfaces in the source VM: • Edit the VM configuration to remove the virtual network interface. • Start the VM. • Use Device Manager to remove network interface devices named similar to VMXNET Device. For more information, refer the Microsoft Knowledge Base article. • Shut down the guest operating system. • Edit the VM configuration to add a new virtual network interface. • Install Provisioning Server Target Device Software. • Restart the VM. • Capture the VM to a virtual disk. If a new VM is created by deploying this template, then the network interface has a new serial number and Machine Address (MAC). Windows detects the network interface as a new device, and the settings of the previous network device are not present. Workaround 2 After deploying a VM from a template or performing a clone, remove references to the previous PCI Express virtual network interfaces in the destination VM. Use Device Manager to remove network interface devices named similar to the VMXNET Device. For more information, refer the Microsoft Knowledge Base article. During template deployment or cloning, a new virtual hardware is created for the destination VM. It helps accelerate time to value by simplifying your underlying infrastructure and allowing you to reduce cost by taking advantage of the industry-standard hardware. Windows server 2012 r2 enterprise iso.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2019
Categories |