大网数据广告活动
服务器运维问答

Changing NIC Interface Descriptions in Windows

· 52CE 我爱测

I'm creating a new Virtual Switch under Hyper-V on a Windows 2016 Server. When I go to create a Virtual Switch under Hyper-V on Windows Server 2016, I have to select the NIC port that it will be using. Unfortunately, Hyper-V show…

问题原文

原帖链接 · cpuguru · CC BY-SA 3.0

I'm creating a new Virtual Switch under Hyper-V on a Windows 2016 Server.

When I go to create a Virtual Switch under Hyper-V on Windows Server 2016, I have to select the NIC port that it will be using. Unfortunately, Hyper-V shows you the "Interface Description" in the drop-down for which NIC to use rather than the "Name". As you can see below, it's rather confusing as the NIC "Name" numbers (which match the port numbers on the back of the server) do not match the number that's auto-assigned in the "Interface Description" field.

I'd like to change the InterfaceDescription setting so that it aligns with the NIC port # so that the NIC I'm selecting in the drop-down for Virtual Switch creation matches up with the NIC number.

Looking at the registry settings, the description for all (4) of the NICs is just "Broadcom NetXtreme Gigabit Ethernet". It looks like Windows is nonsensically attaching a #2, #3 & #4 to the end of the Description names.

Any way to rename the InterfaceDescription for each NIC so that NIC1 matches up with "Broadcom #1", NIC2 matches up with "Broadcom #2" etc?

Below are the results of a PowerShell get-NetAdapter command.

PS C:\Users\Me> get-netadapter

Name -- InterfaceDescription

---- --------------------

NIC4 --- Broadcom NetXtreme Gigabit Ethernet #3

NIC3 --- Broadcom NetXtreme Gigabit Ethernet #4

NIC2 --- Broadcom NetXtreme Gigabit Ethernet

NIC1 --- Broadcom NetXtreme Gigabit Ethernet #2

社区高分解答

原帖链接 · Filip Matijević · CC BY-SA 4.0

Had similar problem on Hyper-V Server 2016. Apparently it's enough to change registry key FriendlyName for affected NICs/ports. The exact path depends on particular HW but it should be somewhere under HKLM\SYSTEM\CurrentControlSet\Enum... (to be on the safe side I've renamed the same key under HKLM\SYSTEM\ControlSet001\Enum... and HKLM\SYSTEM\ControlSet002\Enum...). Use RegEdit search to find path or you can use DevManView, right click on NIC and then click Open in RegEdit


Reboot was required for changes to be applied

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2017-07-13)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0 / CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。