How to Find MAC Addresse of NIC in Windows Team

There are lot of instances where the network communications fail when we are teaming up the incorrect network interfaces. Especially when the team members are the partitions of a virtual partition capable Converged Network Adapter (CNA), we need to make sure that we are teaming up correct partitions from different physical ports for redundancy and proper VLAN traffic. In such situations, the primary troubleshooting step related to network team’s connectivity issue is to validate the network team members.

The easiest way to ensure this is to compare the unique attributes of the partitioned interfaces with the data in the network card BIOS or out-of-band management tools (like iDRAC, ILO etc) or other baseboard management controllers. Media Access Control (MAC) addresses of the partitioned interfaces seen by the Operating System are the easiest and reliable unique identifiers in this scenario as the names for the interfaces will be different for different network cards.

The default available option to get the member NIC’s MAC address is to use the PowerShell command Get-NetAdapter <member NIC name>. For that we have to manually find the native teams in the server, their member NICs and then the MAC addresses of the member NICs.

The following short PowerShell script will automate this process and will list down the MAC addresses of the member NICs of all the native windows teams available in the server. The advantage with the below script is that it can be used on any Windows 2012 or Windows 2012 R2 servers without any modifications/inputs.


foreach ($i in ((Get-NetLbfoTeam).name))
Write-Host “`nTeam Name – “$i`n”Team Members: ”
Get-NetAdapter (Get-NetLbfoTeamMember -Team $i).Name | Format-Table

The best way is to open notepad, copy and paste this script, then save the file as ‘Save As’ > Select ‘All files’ > then name the file ‘nic.ps1’ > destination > where you want

Open Powershell, and run the file .ps1 from it:


Related Article: Technet Microsoft

How To Run Windows Server 2012 and 2012 R2 on ESXi 4.1

If you  are running an ESXi 4.x O.S. you should know that, according with Guest OS Customization Support Matrix (PDF Guest OS Customization Support Matrix VMware ESXi), most recent Windows Server Operating Systems are not Compatibile (2012, 2012R2 and 2016).

VMware Guest OS Customization Support Matrix
VMware Guest OS Customization Support Matrix

With this How-to we will show you how to run Windows Server 2012 and 2012 R2 on ESXi 4.x

I found these set of instructions from VMware communities (VMware communities)

>>Don’t do this for a production environment<<

      1. Create a new VM over the vSphere Client;
      2. As “Guest Operating System” use “Microsoft Windows Server 2008 R2 (64-bit)”;
      3. After VM has been created but before first power on, download the following  bios file and upload it to your ESXi datastore into the folder of the VM;
      4. Now open the .vmx file of the new VM and add the following lines (or edit on the VM advanced option from UI)
    bios440.filename = bios.440.rom
    mce.enable = TRUE
    cpuid.hypervisor.v0 = FALSE
    vmGenCounter.enable = FALSE

    5. Power on VM and Server 2012 will install and run