question

Ben-3882 avatar image
1 Vote"
Ben-3882 asked SunnyQi-MSFT answered

NIC teaming and DHCP

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-dhcp-dnswindows-server-infrastructure
5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

SunnyQi-MSFT avatar image
0 Votes"
SunnyQi-MSFT answered

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.


5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.