NIC teaming and DHCP

Ben 6 Reputation points
2020-11-11T16:39:52.983+00:00

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.

Ben

Windows for business | Windows Client for IT Pros | Networking | Network connectivity and file sharing
Windows for business | Windows Server | Devices and deployment | Set up, install, or upgrade
0 comments No comments
{count} vote

1 answer

Sort by: Most helpful
  1. Anonymous
    2020-11-12T07:30:28.447+00:00

    Hi,

    Thank you very much for posting here and sharing your resolution in our forum as it would be helpful to anyone who encounters similar issues.

    If there is anything else we can do for you, please feel free to post in the forum.

    Best Regards,
    Sunny

    ----------

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.