How to Find MAC Addresse of NIC in Windows Team This article describes how to get the MAC addresses of all member Network Interface Cards (NICs)

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.

Script:

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:

MAC_Addresses_NIC_Team_2012
MAC_Addresses_NIC_Team_2012

Related Article: Technet Microsoft

How to Find a Lost, Missing, Hidden or Removed Network Card In a scenario where you have physically removed hardware from a machine you can no longer see it in device manager.

In a scenario where you have physically removed hardware from a machine you can no longer see it in device manager.  This does not mean that it is gone.  Evidence of that is, if for example you had a network card that had a Static IP address set and you remove the card and add a new one then try to set the IP address to the same as the old NIC you will get an error message. The error might look something like “The IP address 192.168.30.100 you have entered for this network adapter is already assigned to another adapter (Microsoft Virtual machine Bus Network Adapter #3) which is no longer present in the computer.  If the same address is assigned to both adapters and they both become active, only one of them will use this address.  This may result in incorrect system configuration”.  In Windows Server 2008 R2 and Windows 7 it actually gives you an opportunity to “remove the static IP configuration for the absent adapter”. If you say Yes, this will eliminate the IP conflict problem but does not solve the problem of the adapter still being present in the machine.  In older versions of the OS, it was even worse because every time you go into network properties it gives you an error message.  Another way this comes up is if you move a virtual machine from one host to another.  Like in the case of moving from Virtual Server 2005 R2 to Hyper-V or perhaps you are moving from one Hyper-V machine to another but you did not do an export, you just moved the VHD’s and created a new machine.

The IP address XXX.XXX.XXX.XXX you have entered for this network adapter is already assigned to another
The IP address XXX.XXX.XXX.XXX you have entered for this network adapter is already assigned to another

Getting rid of these old devices is actually very simple. Well, it is simple if you know how

Before you proceed, I recommend that you confirm that you have a good backup. I have never had a problem with this but hey, it is your server not mine.

Description

  • You need to run a command prompt so you can set an environment variable prior to opening the Device Manager This will bring up a command windowClick Start – Type the following command and then press ENTER

    cmd
  • Step 2: We have the command window open.  We now need to set the variable (that is the “set” line and then with the variable set, we need to run Device Manager.
    The file name for the Device Manager snap-in is devmgmt.msc.  The first line will not appear to do anything but it is setting the environment for next step.  The second command will actually open the Device Manager but it will be in a “special” mode which allows you to show devices that no longer exists.Type the following commands pressing ENTER after each line

    set devmgr_show_nonpresent_devices=1

    devmgmt.msc

  • Step 3: Now all we have to do is show hidden devices and you will be able to access the devices that are not present in the machine.  This will also turn a checkbox on in front of the Show Hidden Devices menu option.In this Special Device Manager Window; on the menu, click View then Show Hidden Devices
  • Step 4: Now you can just go find the adapter or device that is missing and delete it!  Expand the network adapter (or whatever category of device) and look for the device that needs to be removed.  The error message that you got should tell you the “name” of the device so you just have to go find that named device.  You may also notice while you are there that the icon for the “non-present” or missing device is slightly subdued so that will make it easier to find it if you have many devices in a category.See screen shot belowExpand the network adapter (or whatever category of device) and look for the device that needs to be removed.
    Right-Click the Device and select Uninstall
devmgr_show_nonpresent_devices
devmgr_show_nonpresent_devices

Related Article: VMware KB  | Microsoft Blog Technet

AWS named as a leader in the Infrastructure as a Service (IaaS) Magic Quadrant report for the 7th consecutive year The 2017 Magic Quadrant for Cloud Infrastructure as a Service, Worldwide. Difference with 2016

At AWS, we invest in customer success through an accelerating pace of innovation with a focus on operating efficiently at massive scale, and growing a partner ecosystem already tens of thousands strong. We have worked closely with industry leaders from Salesforce to McDonald’s, Comcast to Capital One, to help them transform their businesses by migrating and rethinking existing applications, as well as pursuing new solutions in areas like artificial intelligence, IoT, and big data.

In the image the last year quadrant (2016) vs the 2017 quadrand.

IAAS GARTNER 2016 vs 2017
IAAS GARTNER 2016 vs 2017