Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Deploying Windows 2008 R2, Windows 2012, and Windows 7 templates with vmxnet3 renames the NIC as #2 (1020078)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 211166Language:
Chinese (Simplified)JapaneseEnglish

5 like this article

Subscribe to get an email
newsletter with new updates

5 people found this helpful Please provide article feedback:

Symptoms

When deploying or cloning virtual machines from a Windows 2008 R2, Windows 2012, or Windows 7 template configured with the VMXNET3 virtual network device:

The resulting virtual machine's guest operating system 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 present in Device Manager when Show Hidden Devices is enabled.

The old Ethernet network interface retains its network configuration, preventing the new interfaces from reusing the previous static IP addresses. For more information see Networking Error: IP address already assigned to another adapter (1179).

Note: Upgrading the virtual hardware from version 4 to 7, or upgrading the VMware Tools, may automatically convert Flexible or VMXNET2 virtual network interfaces to VMXNET3. This issue may be observed after such an upgrade.

Resolution

During template deployment or cloning, new virtual hardware is created for the destination virtual machine. Network interfaces are assigned new MAC addresses. PCI Express devices, including the VMXNET3 virtual ethernet adapter, a new serial number is generated as well.

Windows 2008 R2, Windows 2012, and Windows 7 track PCI devices by which slot the device is connected to. Moving a PCI network interface between slots will allocate a new set of settings for the NIC as it is considered a new device. Replacing a PCI network interface with the same make and model will retain use of the previous settings. However, PCI Express devices are tracked by their serial number, which is derived from the MAC address.

When a virtual machine is created by cloning or template deployment, the new virtual machine's PCI Express virtual network interfaces have different MAC addresses and serial numbers, and are detected as new devices.

The same behavior can be observed by deploying clones of Windows 2008 R2, Windows 2012, or Windows 7 on new physical hardware with PCI Express network interfaces in the same slots.

Solution:

Install any new Windows Updates on the parent virtual machine.

For Windows 7, go to Control Panel -> System and Security -> Windows Update -> Check for Updates.

For Windows 10, go to Settings -> Updated & Security.  Ensure "You're up to date" is seen.  There is no need to click the "Check for updates" button.

Workaround 1:

Before converting a virtual machine to a template, remove references to the PCI Express virtual network interfaces in the source virtual machine:

Edit the virtual machine configuration to remove the virtual network interface.

Power the virtual machine on.

Use Device Manager to remove network interface devices named similar to "VMXNET Device".

Shut down the guest operating system.

Edit the virtual machine configuration to add a new virtual network interface.

Convert the virtual machine to a template.

When the new virtual machine is created by deploying this template, the network interface will have a new serial number and MAC address. Windows will detect this network interface as a new device, but there will be no previous network device retaining old settings.

Workaround 2:

After deploying a virtual machine from a template or performing a clone, remove references to the previous PCI Express virtual network interfaces in the destination virtual machine. Use Device Manager to remove network interface devices named similar to "VMXNET Device".

Workaround 3:

Reconfigure the affected virtual machines to use the E1000 or other PCI network interface. For more information, see Choosing a network adapter for your virtual machine (1001805) and Manually configuring a virtual machine to use the e1000 network adapter driver (1003020).

Workaround 4:

When looking at the hidden devices within the Microsoft Guest operating systems, make sure you remove the Microsoft ISATAP adapter prior to configuring the new vNIC with a Static IP address inside a virtual machine.

Related Information

vmxnet3 を使用した Windows 2008 R2 テンプレートおよび Windows 7 テンプレートをデプロイすると NIC の名前が #2 に変わる
部署具有 vmxnet3 的 Windows 2008 R2 和 Windows 7 模板会将网卡重命名为 #2

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
vSphere Web Client に VDP プラグインが表示されない (2122684)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware ESX Server

Related Versions:

VMware vSphere ESXi 5.1

VMware vSphere ESXi 5.0

VMware ESXi 4.1.x Installable

VMware ESXi 4.1.x Embedded

VMware ESXi 4.0.x Installable

VMware ESXi 4.0.x Embedded

VMware ESX 4.1.x

VMware ESX 4.0.x

Take Our Survey

Support Assistant