locked
NIC teaming and DHCP RRS feed

  • Question

  • When using NIC teaming in Windows Server 2016/2019 there is no way of determining which member interface becomes primary at boot.

    Because we cannot determine this, we do not know which member's MAC address will be used by the team.  This makes DHCP troublesome.

    I have created a PowerShell script (that may require some modification dependent on your environment) that takes the lowest MAC address of the members and assigns it as the team's MAC address.  This will ensure that any DHCP reservations you may have will work as expected.

    $lowest = Get-NetAdapter | where Name -ne "NIC Team #1" | measure -Property MacAddress -Minimum | select Minimum
    $mac = $lowest.minimum -replace '-',''
    Set-NetAdapterAdvancedProperty -Name "NIC Team #1" -DisplayName "MAC Address" -DisplayValue $mac
    

    Hope this helps.

    _-_ B e n -_-

    • Changed type Dave PatrickMVP Wednesday, November 11, 2020 4:12 PM question
    • Moved by Dave PatrickMVP Wednesday, November 11, 2020 4:12 PM looking for forum
    Wednesday, November 11, 2020 3:58 PM

Answers

All replies